Coverage states
Fix "Excluded by 'noindex' tag" when you didn't mean to block the page
Search Console: "Excluded by 'noindex' tag" on a page you want indexed.
A noindex directive — in a <meta robots> tag or an X-Robots-Tag header — is telling Google to keep the URL out, and Google is obeying. Find the source (stale draft tag, CDN/plugin header, CMS toggle), remove it, confirm it's gone from both HTML and headers, then push a re-crawl. Recovery is usually fast.
"Excluded by 'noindex' tag" is Search Console doing exactly what you (accidentally) told it to. Somewhere on the page or in its HTTP headers, a noindex directive is telling Google to keep the URL out of the index — and Google is obeying. The whole job is finding where that directive comes from.
The usual culprits
- A leftover <meta name="robots" content="noindex"> from when the page was a draft or a staging build.
- An X-Robots-Tag: noindex HTTP header set by your server, CDN, or a security plugin.
- A CMS toggle: WordPress "Discourage search engines," a Webflow/Framer "hide from search" switch, a Shopify draft/hidden product.
- An SEO plugin rule that noindexes a whole template (tag pages, author archives) and is catching pages it shouldn't.
- A staging robots/meta config that shipped to production during a launch.
Find the exact source
- View source on the live URL and search for "noindex" in the HTML <head>.
- Check the HTTP response headers (curl -I or your browser's network tab) for X-Robots-Tag.
- If the HTML looks clean but Google still sees noindex, the page may render it via JavaScript — check the rendered DOM, not just the raw source.
- Run the indexability checker, which checks both the meta robots tag and the X-Robots-Tag header for you in one pass.
If a whole section — or your entire site — shows "Excluded by noindex," check for WordPress's "Discourage search engines from indexing this site" setting, or a global noindex that survived a staging-to-production deploy. This single checkbox has deindexed more sites than almost any other SEO mistake.
Fix and recover
- Remove the noindex meta tag or the X-Robots-Tag header from the affected pages.
- Confirm the page now returns no noindex directive in either the HTML or the headers.
- Push the URL through the Indexing API to request a fresh crawl.
- Re-check status after 24–48 hours. Recovery is usually fast once the directive is gone, because Google was actively excluding a page it already knew about.
IndexerNow runs on your own Google account, your own Cloud project, and your own quota — we never pool submissions through a shared account. Connect your GSC and push the URL through Google's Indexing API in two clicks.
Connect your own GSC and index nowFrequently asked
Where does the noindex come from if it's not in my HTML?
Most often an X-Robots-Tag HTTP header set by your server, CDN, or a security/SEO plugin — or a noindex injected by JavaScript after the initial HTML loads. Check the response headers and the rendered DOM, not just View Source.
How fast does a page recover after I remove the noindex?
Usually within a day or two of the next crawl, because Google already knew the URL — it was deliberately excluding it. Pushing the URL through the Indexing API speeds the re-crawl.
Should I block the page in robots.txt instead?
No — that's the opposite goal. If you want the page indexed, never block it. If you want it out, keep it crawlable and add noindex so Google can actually read the directive.
Related fixes
Fix "Blocked by robots.txt" in Google Search Console
"Blocked by robots.txt" means Google can't crawl your URL at all. Here's how to find the offending rule, fix it, and get the page indexed.
How to remove or deindex a URL from Google (the right way)
Need a page gone from Google? Here's how to remove a URL fast, how to deindex it permanently, and the common mistakes that leave pages stuck in the index.
Fix "Duplicate without user-selected canonical" in Search Console
Google found multiple near-identical URLs and picked the canonical for you — maybe not the one you wanted. Here's how to take back control and consolidate.