Google Search Console indexing guide · reviewed November 7, 2026
Excluded by noindex tag: what it means and what to check
When Google reports Excluded by 'noindex' tag, the page carries a directive telling search engines not to show it in search results. For private or intentionally excluded content, this may be the correct outcome.
First decide whether the page should be indexed
A checkout completion page, internal account screen or intentionally private resource often belongs outside search results. An important public article or product page usually does not. Check the page's purpose before changing robots directives.
Where can noindex come from?
The HTML document can contain a robots meta tag with noindex, or the HTTP response can include an X-Robots-Tag: noindex header. A CMS, template, staging configuration, server or CDN rule may add one of these even when an editor did not.
How to investigate a reported noindex
- Open Google Search Console → Indexing → Pages, then select the noindex reason and inspect one affected URL.
- Use URL Inspection to compare the previously indexed/crawled information with the Test live URL result. The two views can differ while Google processes changes.
- Review the real response headers and HTML source for noindex directives. Our HTML canonical checker checks a different signal and cannot detect response headers.
- If the page is meant to be publicly indexed, remove the unintended noindex instruction from the responsible layer, then confirm it no longer appears in the live page or response.
- After fixing the underlying issue, consider the URL Inspection request-indexing action for an important page. It cannot guarantee indexing and may be quota-limited.
Example: a staging rule reached production
A fictional site launches a help article, but its production template still includes <meta name="robots" content="noindex">. Search Console correctly excludes the article. The right fix is to remove the unintended directive from the template, not repeatedly submit a sitemap.
Common mistakes
Blocking Googlebot with robots.txt while relying on a page-level noindex can prevent Google from seeing that directive. Do not treat robots.txt as a reliable deindexing tool. Do not remove intentional noindex from account, private or duplicate pages without understanding why it was added.
Is a successful live test enough?
No. A live test reflects what Google can see at test time, but the indexed status may lag. Monitor the report after Google recrawls; do not assume every public page will be indexed.
Related: Why pages are not indexed, Google chose a different canonical, and free SEO tools.
Official references
Google: Page indexing report and noindex status · Google: Control indexing with noindex. This is general troubleshooting guidance, not an inspection of your live site.