stillindexedStart monitoringOpen the app

Search Console Page indexing: Why pages aren't indexed

Excluded by 'noindex' tag in Search Console: the fix

Google found a noindex in the robots meta tag or the X-Robots-Tag header. Where it usually comes from, how to find it, and how to get the page back.

Google fetched the page and found a noindex rule, in a robots meta tag or an X-Robots-Tag response header, so it left the page out of Search. If you meant it, nothing needs doing. If not, find which of the two carries it, remove it at the source, and request indexing.

What "Excluded by 'noindex' tag" means

Google: "When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it." Google's help page names this status "URL marked 'noindex'"; the report shows "Excluded by 'noindex' tag". The rule can come from <meta name="robots" content="noindex"> in the HTML or from an X-Robots-Tag: noindex response header. Google says the two have the same effect, and the header never appears in view-source.

The report shows "Excluded by 'noindex' tag". Google's help page for the report calls the same status "URL marked 'noindex'".

Is it a problem?

Depends on the URL

Only if you want the page in Search. A noindex on a page you do not want indexed is the system working, and Google says so. It becomes an incident when the count rises after a deploy, or when the list contains pages that earn traffic.

Causes, most likely first

  1. A "discourage search engines" or "hide from search" setting switched on in the CMS, often left over from building the site before launch.
  2. A staging environment's noindex shipped to production with a deploy, in a template or in an environment variable that controls the robots tag.
  3. An SEO plugin rule that noindexes a whole content type, taxonomy or paginated archive.
  4. An X-Robots-Tag header added at the server, CDN or hosting layer, which nobody sees in the page source.
  5. JavaScript meant to remove a noindex the server sent. Google says that when it sees noindex it may skip rendering, so the script may never run for Googlebot.

How to confirm it

  1. In URL Inspection, read "Indexing allowed?" on the indexed result. Google says it should show that noindex is preventing indexing.
  2. Click Test live URL and read "Indexing allowed?" again. If noindex is gone from the live page, the report is describing an older crawl.
  3. Search view-source for "noindex", then check the response headers in DevTools. The indexability checker reads the meta tag and the X-Robots-Tag header in one request.

Indexability checkerX-Robots-Tag checker

How to fix it

  1. Find the source: the CMS visibility setting, the SEO plugin rule for that content type, the template, or the server or CDN config that adds the header.
  2. Remove noindex at that source rather than overriding it with JavaScript.
  3. Make sure robots.txt does not block the page, or Google cannot see that the noindex has gone.
  4. Re-run the indexability checker until neither the meta tag nor the header carries noindex, request indexing for the important URLs, then click Validate fix.

How long recovery takes

Google has to recrawl the page to see the noindex has gone. Crawling can take "anywhere from a few days to a few weeks", and Google notes that depending on a page's importance "it may take months for Googlebot to revisit a page". Request indexing asks for a recrawl of one URL but does not guarantee it.

After a fix, Validate fix on the issue asks Google to recheck the affected URLs. Google says validation "typically takes up to about two weeks, but in some cases can take much longer". Without it, the count still updates as Google recrawls, and an issue leaves the table once 90 days pass with no instance.

Would monitoring have caught it?

A noindex appearing on a monitored URL, in the meta tag or the X-Robots-Tag header, is a critical change. It is re-checked after 60 seconds and alerts if it holds. A URL that already carries noindex the first time it is checked is reported on that first check rather than taken as the baseline.

stillindexed checks each monitored URL every 30 minutes on Starter and every 15 minutes on Agency, so the change is found on the next check and confirmed before it alerts, rather than waiting for this report to update.

See what monitoring covers

A noindex tag hiding the site from search, platform by platform

Further reading

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-06. If Google has changed a page since, Google's page wins and we would like to know.