I recently discovered that Google has made some updates to their JavaScript SEO basics documentation. This change has brought clarity to how Google’s crawler deals with noindex tags on pages utilizing JavaScript. The main takeaway? If you’re aiming to have your page indexed, definitely avoid including a noindex tag in the original page code.
What’s New: Google has adjusted this section to specify that when Google encounters a noindex tag, it may bypass rendering and executing JavaScript. Consequently, efforts to modify or remove the robots meta tag using JavaScript might not yield the desired results. So, if indexing is a goal, keep the noindex tag out of the original code.
Previously, the guidelines indicated a certain certainty: if a noindex tag was detected, Google skipped rendering and executing any JavaScript. This meant any attempts to counter this with JavaScript adjustments would simply not work. The advice stood firm—keep noindex tags out of the original code if there’s any chance you need the page indexed.
Reason for Change: Google clarified that while it can render pages employing JavaScript, this behavior is not consistently defined and is subject to change. If there’s any chance you want your page to show up in search, play it safe and leave out the noindex tag from the original code.
Why This Matters: It’s often safer to steer clear of JavaScript when setting crucial protocols, especially concerning the blocking of Googlebot or other crawlers. If you need a search engine not to rank a particular page, avoid using JavaScript to execute those directives.
Inspired by this post on Search Engine Land.
Leave a Reply