Complicated Title Tag Issues. Experts, Please Help!

[Leowa]

Hi, I noticed that the images I added don't show. So to clarify:

The 'navigation bar' on google = the tabs-bar on the top of chrome

[RossKernez]

Hi there,

I had a similar problem at one of the client's websites. You must remove the second title from the page because Google is confused about which title is correct. It is possible that the first titles are dynamically generated by the script and they are being overwritten by the second titles or vice versa. By the way, this "%20" means space in a programming language.

Ross

[Leowa]

Hi Ross!

Thank you so much for your answer! I will try this immediately and let you know how it goes

Leo

[RossKernez]

Sounds good!

[seoelevated]

I also suggest to double check that the actual title tag (the first one you included in your post) is in the section of the page, and not the . And preferably high up in the section before any scripts or other elements which could take significant time to load. Check this in "view page source" and not just using the "inspect" function of the browser's dev tools, to ensure that some scripts on the page aren't altering the title tag after the document is loaded, since the search engines may instead use whatever is initially set in the actual of the document before scripts execute.

[Leowa]

Hi Seoelevated, thanks! It is in the section, but below google analytics and google tag manager scripts. Is that good enough? Although as it is right now the wrong title tag shows in the page source but we're implementing fixes according to the feedback from Ross (which will hopefully help!!)

[Everett]

Hi Leowa,

As long as it comes before you're fine.

[seoelevated]

Primarily, the requirement is to be in the section. However, I have seen cases where a long-load-time resource in the above meta tags can cause meta tags to be ignored. These were fairly extreme cases, where the resource took multiple seconds to load, synchronously. But moving the meta tags (and Title) above those resources fixed the issue. Also, in another case, we had a snippet from a CDN provider which included an iframe, and in that iframe there was a section and a closing . It turned out that Google was ignoring all of our tags after the which was injected in that iframe, even though it was only supposedly closing the section opened within the iframe. Once we moved that iframe to the end of our own section, below all our meta data, the issues resolved. So, with all that, I do recommend putting meta data at the top of the section, but depending on what else is in there, it might not be an issue for you.

[Leowa]

This could definitely be relevant to us as the pagespeed is slow when first entering the site (like 6-7 seconds...) and a lot of resources are loaded (primarily unnecesary JavaScript and render-blocking resources according to Lighthouse). We're working on the pagespeed but I'll pass on this info to the development team in the meantime. If the Ross fix doesn't work we'll put the tags as high up as possible in the .

Thanks a lot, seoelevated! You are an absolute champion!

P.S. We're also changing to nextJS  which, as I've understood, should solve a lot of JavaScript SEO issues.

[Leowa]

UPDATE: It worked!!!!!! I'm so freaking happy! Love you guys!