Excluded by ‘noindex’ tag
The page tells search engines not to index it. That may be exactly what you want for a utility page; it is a problem when an important public page inherited the instruction accidentally.
Troubleshooting guide · Public signals and practical next steps
What this means
Search Console reports an indexing exclusion caused by a noindex instruction. It can come from an HTML meta tag or an X-Robots-Tag HTTP header.
When it’s normal—and when to investigate
Often expected
Thank-you pages, internal search results, or other public utility pages may intentionally carry noindex. They do not all need their own search result.
Worth investigating
Review the instruction when it appears on a homepage, article, or other page meant for search, especially following migration from a staging environment.
Work through these checks
Check both HTML and headers
Look for robots and googlebot meta directives, plus X-Robots-Tag on the final response. A plugin setting alone does not tell you what the CDN or web server actually sends.
Trace the source of the instruction
Inspect site visibility settings, page-level settings, templates, middleware, and CDN rules. A response header can add noindex even if the HTML appears correct.
Check whether Google can fetch the page
Do not block crawling to hide a noindex instruction. If robots.txt prevents fetching, Google may not be able to see either the old directive or its removal.
Confirm the deployed response
After fixing an unintended exclusion, clear stale caches and test again. Compare a live inspection with the recorded crawl rather than expecting the report to update immediately.
Common causes
- A staging visibility setting remains enabled.
- A shared template applies noindex to more page types than intended.
- A hosting or CDN header adds the directive.
- An old cached response persists after the setting changes.
Possible fixes
- Remove unintended noindex at the responsible layer, including relevant headers.
- Check both generic and Googlebot-specific directives; an index instruction does not cancel a conflicting noindex.
- Keep intentional exclusions and remove those URLs from indexing-focused sitemaps.
- Request another inspection after the current response is correct.
Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.
What this tool can and cannot verify
It can
Read generic and Googlebot meta instructions and applicable X-Robots-Tag directives from the final public response.
It cannot
See directives inserted after JavaScript rendering, inspect authenticated responses, or confirm that Google has processed a change.
Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.
A useful follow-up
Does nofollow also prevent indexing?
No. Nofollow concerns following links; noindex concerns whether the page is included in the index. The none directive combines noindex and nofollow.
Official reference: Google: Block indexing with noindex. See also the Page indexing report documentation.