JavaScript Console Errors found on /blog and blog post

[amauch-adobe]

I went to the business.adobe.com/blog and checked the console and found one JS error shown on the blog homepage from the content-script.js on line 7, as shown on the following image:

I also went to the /blog/the-latest/announcing-the-2021-adobe-experience-maker-awards-finalists blog post and other blog posts and found some errors that always showed up regardless of the post namely:

1. the same error as the blog homepage listed above.
2. interlinks.js line 36 for the /blog/keywords.json file, ended up in a 404
3. various 404s from other scripts (this was dependent on the blog post you went to, but generally on every post I went to there were 3 or 4 listed errors)

See the following image for reference:

[davidnuescheler]

i don't think that i see that same error.
the 404 are from references that are on the page that don't exist in articles that were migrated, and possibly should be removed or adjusted. the keywords.json will be there as soon as some interlinking is configured.

i don't think there is a reasonable way to disable the 404, i think they should just be fixed by adding/removing content.

[amauch-adobe]

Sounds like a the right approach to me and all your discussion points make sense for the other 404s. Thanks for clarifying.

[amauch-adobe]

I can make mention of this to the authoring team to look into adding/removing the content.

[stereoke]

@aaronmauchley-adobe - should we close this issue here then? And we can log a DOTCOM in Jira for Porter/Rikio?

[amauch-adobe]

@stereoke - that would be the best did you want me to handle that or you?

[amauch-adobe]

So I will be clear though the first issue on the business.adobe.com/blog with the content-script.js issue is not an issue on Helix, I looked into it more and it has to do with a chrome extension running on my browser. What will need to be moved to Jira in a ticket will be about the 404 errors coming from assets that weren't migrated over and just need to be removed/added to fix the 404's as stated by Nuescheler.

[amauch-adobe]

That being said the issue with the 404's showing up affects more than just the blog post URL I mentioned in the ticket. What will need to be done is an audit of some sort that can go through and fix the 404's on any blogs that have them.

[stereoke]

@aaronmauchley-adobe I'll open a ticket and it sounds like something our SEO team can automate (the list of 404s) and then we can address action from there. Thanks!
Tracking MWPW-101548