Skip to content
regensbot
DEV-REN-05Avoid5 of 10 in REN

Do not add, change or remove robots meta tags with JavaScript

Level
Avoid

Must not: the site is not ready to launch while it does this.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Automatic

Decided automatically once Regensbot renders your pages.

Why it matters

Robots rules added with JavaScript take longer to be seen, and removing a noindex with JavaScript does not work: Google may skip rendering a page that arrives with noindex, so it stays out of the index. Google's documentation recommends avoiding JavaScript to inject or change meta tags.

How to meet it

Decide indexability on the server and send the final robots meta tag or X-Robots-Tag header in the first response. Never ship noindex in the HTML shell and remove it after hydration, and never toggle data-nosnippet with JavaScript. The one documented exception is adding noindex with JavaScript to an error view in a client-rendered app (DEV-ERR-02).

How to test it

The robots meta tag in curl output and in URL Inspection's rendered HTML is identical on every indexable template. A search of the client bundle finds no code that writes meta[name="robots"] except error views.

How Regensbot covers it

AutomaticNeedsRendering in headless Chromium

Decided automatically once Regensbot renders your pages.

Headless Chromium renders the page on an isolated render service, and the raw and the rendered HTML run through the same parsers.

How verdicts workWhat you connect

Sources

Google documents03

  1. 01meta tags and attributes that Google supportsGoogle Search Central (opens in a new tab)
  2. 02Understand the JavaScript SEO basicsGoogle Search Central (opens in a new tab)
  3. 03Robots meta tag, data-nosnippet, and X-Robots-Tag specificationsGoogle Search Central (opens in a new tab)

Claims in the knowledge base09

  1. D2-C108ConsistentControlling indexingShown on screen
  2. D2-C106ConsistentControlling indexingShown on screen
  3. D2-C107SourceControlling indexingGoogle's documentation
  4. D2-C257SourceWhat is Google friendly JavaScriptGoogle's documentation
  5. D2-C109n/aControlling indexingThe author's interpretation
  6. D2-C079SourceControlling indexingGoogle's documentation
  7. D2-C852ConsistentControlling indexingSaid on stage
  8. D2-C853ConfirmedControlling indexingSaid on stage
  9. D2-C854SourceControlling indexingGoogle's documentation

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Confirmed
Google's documentation states the same thing.
Consistent
Google's documentation supports it without stating it.
Source
The claim is the cited document itself.
n/a
Nothing to verify: a quotation, framing, opinion or analysis.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.