Excluded by 'noindex' tag: how to find and remove a noindex

Last updated: 2026-10-30

In short

This status means Google crawled the page, found a noindex rule in a robots meta tag or an X-Robots-Tag HTTP header, and therefore did not index it. If you do not want the page in Google, this is working. If you do, remove the noindex at its source, confirm with Test live URL and request indexing.

Exact label in Search Console: Excluded by 'noindex' tag

What it means

Google's Page indexing help says that when Google tried to index the page, it encountered a noindex directive and therefore did not index it. noindex can be set in a robots meta tag in the HTML head or as an X-Robots-Tag HTTP response header; both have the same effect, and the header also works for PDFs and other non-HTML files. Once Google extracts the rule, it drops the page from Search regardless of whether other sites link to it.

For noindex to work, Google has to be able to crawl the page. If the URL is also blocked by robots.txt, Google never sees the rule. Google's help article titles this reason URL marked 'noindex', while the report row reads Excluded by 'noindex' tag.

Is it a problem?

Not if you set it on purpose. Thank-you pages, internal search, login screens, tag archives and staging copies are commonly noindexed. It is a problem when pages you want to rank carry noindex, often after a launch, theme change or plugin setting. Google's report guide says a drop in indexed pages without matching errors can mean you are blocking existing pages with noindex.

Common causes

Intentional noindex

Pages you deliberately keep out of Search.

Staging settings shipped to production

A site-wide setting that discourages search engines, or a template flag, left on after launch.

Plugin or theme defaults

SEO plugins or themes that noindex archives, attachment pages, paginated pages or new content types by default.

A header set by the server or CDN

An X-Robots-Tag noindex header added in server or CDN configuration, often for a whole directory or file type. It is invisible in the HTML.

JavaScript that changes the tag

Google's JavaScript guide warns that when Google finds noindex in the original HTML it may skip rendering, so removing noindex with JavaScript may not work.

How to fix it

  1. Confirm where the noindex comes from. Inspect the URL: under Indexing allowed? Search Console shows whether noindex prevented indexing. Search the page source for a robots meta tag and the response headers for X-Robots-Tag.
  2. Remove it at the source. Change the CMS or plugin setting, template or server rule that adds it. Make sure the original HTML no longer contains noindex rather than relying on JavaScript to remove it.
  3. Test the live page. Run Test live URL. If Indexing allowed? no longer reports noindex, click Request indexing. If it still does, the rule is still being served, possibly from a cache or CDN.
  4. Keep the URL crawlable. Make sure robots.txt does not block the page, or Google cannot see that the noindex is gone.
  5. Validate the group. After fixing a whole template, click Validate fix on the issue. Google says validation typically takes up to about two weeks.

Check it with GSC Magic

gsc_inspect_urls_batch returns the indexing state for each URL, including whether Google saw noindex in the robots meta tag or in an HTTP header, so your assistant can scan your key pages after every release and list any that are blocked. report_index_health runs the same check on everything in a sitemap. If noindexed pages had traffic before, gsc_query_analytics shows how many clicks they lost.

gsc_inspect_urls_batchreport_index_healthgsc_inspect_urlgsc_query_analytics

Prompts to copy

Inspect my 100 most important URLs and list any where indexing is not allowed because of a noindex robots meta tag or X-Robots-Tag header.

Run an index health check on my sitemap and tell me whether any URL in it is excluded by a noindex tag, since a sitemap should not list noindexed pages.

For these URLs that were noindexed by mistake, compare clicks for the 28 days before and after the release date I give you.

Guides on the blog

Blocked by robots.txt

Blocked by robots.txt means a rule in your robots.txt file stops Googlebot from crawling the URL, so Google cannot index its content. If the block is intentional, leave it. If the page should be in Google, remove or narrow the rule; if you want it out of Google, use noindex instead, because robots.txt does not reliably prevent indexing.

 Indexed, though blocked by robots.txt

This warning means Google indexed the URL even though robots.txt blocks crawling it, usually because other pages link to it. Google cannot read the page, so any snippet is very limited. If you want the page out of Google, remove the block and add noindex; if you want it in Google, remove the block.

 Crawled - currently not indexed

Crawled - currently not indexed means Googlebot fetched the page but Google decided not to add it to the index, at least for now. Google says it may or may not be indexed later and that you do not need to resubmit it. For pages that matter, make them clearly distinct and useful, link to them internally and check canonical signals.

Frequently asked questions

How long after removing noindex will the page be indexed?

Google has to recrawl the page to see the change. Its noindex documentation says it can take months for Googlebot to revisit a page, depending on the page's importance, so request indexing in URL Inspection for key URLs.

Can I use robots.txt and noindex together?

Not on the same URL if you want noindex to work. Google says that if a page is blocked by robots.txt, the crawler never sees the noindex rule and the page can still appear in results.

Does noindex save crawl budget?

No. Google's crawl budget guide says not to use noindex for that, because Google still requests the page and then drops it, which wastes crawling time.

Does noindex work in other search engines?

Google says some search engines might interpret the noindex rule differently, so a page might still appear in their results.

Sources