Noindex added or removed by JavaScript
Short answer
Noindex added or removed by JavaScript means: the raw page and the page after JavaScript disagree about noindex. Google reads the raw noindex first and may never render the page. To fix it: set robots tags in the server HTML only.
By the SmooxSEO team. Updated on 16 November 2026.
What it means and why it matters
The raw page and the page after JavaScript disagree about noindex. Google reads the raw noindex first and may never render the page.
How to fix it
Set robots tags in the server HTML only.
Common causes
- The HTML contains noindex, and JavaScript removes it after loading (Google may never index the page).
- A JavaScript framework adds noindex on some pages, by error or while data loads.
How to spot it
Compare the page source (Ctrl+U, before JavaScript) with the rendered page (Inspect, after JavaScript): look for the robots meta tag in both. Google's URL Inspection tool shows the rendered version. SmooxSEO reads both versions and flags any difference.
Example
HTML: <meta name="robots" content="noindex">
Rendered: (removed by JavaScript)HTML and rendered: no robots noindex on pages you want in GoogleMistakes to avoid
- Relying on JavaScript to remove a noindex: if Google reads noindex in the HTML, it may skip rendering the page at all.
How serious is it?
A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.
About indexability checks
Whether search engines are allowed to put a page in their index: noindex tags, robots rules and HTTP headers that keep pages out of search results.
Find this problem on your site
SmooxSEO checks every page of your site for this problem and 311 others, lists the pages concerned, and tells you what to fix first.