GSC status
How to fix “excluded by noindex tag”
Google is doing what the page asked. Find the noindex, decide whether it should stay, and only then request indexing. Submitting a URL that still sends noindex wastes the request.
What this status actually means
A directive, not a quality call
This is not crawled-not-indexed. Google is excluded by instruction. Until the instruction is gone on a recrawl, coverage will stay excluded.
What diagnose already reports
On fetch, a
name="robots" meta whose content contains noindex sets the flag. The next action is: remove the robots noindex meta or header if you want the URL indexed.Meta robots vs X-Robots-Tag
This page is not a live noindex checker. The checks above are what to look at; T2 is where a paste-a-URL tool belongs.
| Cause | Check | Fix |
|---|---|---|
<meta name="robots" content="noindex"> |
View-source, or let diagnose fetch the page. If that meta matches, the next action names noindex explicitly. | Remove it, or change it to index,follow, on URLs you want indexed. Keep it on thank-you, search, and filter pages that should stay out. |
X-Robots-Tag: noindex on the HTTP response |
Response headers, not HTML. curl -I or DevTools. Our diagnose fetch does not read this header today — a missing meta is not proof the page is indexable. | Drop the header at the origin, CDN, or plugin that sets it. Re-fetch headers until it is gone, then request indexing. |
Googlebot-specific meta (name="googlebot") with noindex |
A robots meta can say index while a googlebot meta says noindex. Google honours the googlebot one. Check both name values. | Align them. If Google should index the URL, neither meta may contain noindex. |
| SEO plugin injecting noindex on staging, pagination, or “noindex this post” | Rendered HTML after the plugin stack, not the theme file. A per-post checkbox survives a template change. | Turn the rule off for URLs you want indexed. Leave it on for staging hosts and internal search. |
| HTTP header and meta both present, disagreeing | If either says noindex, Google treats the URL as noindex. Inspection will still say excluded by noindex. | Clear both channels. Then recrawl. Do not submit in between. |
Remove the directive, then ask once
1
Find every noindex
Meta robots, googlebot meta, X-Robots-Tag. All three, not the first one you see.
2
Decide per URL
Some pages should stay noindex. For those, this GSC status is correct — leave it.
3
Recrawl after the tag is gone
URL Inspection → Request Indexing, or another method that still works. Submitting while noindex is present does nothing useful.
Common questions
Related: All indexing issues · Duplicate without user-selected canonical · Alternate page with proper canonical tag · Crawled — currently not indexed · Discovered — currently not indexed · Soft 404 · Blocked by robots.txt
Where can noindex live?
In HTML:
<meta name="robots" content="noindex"> (or a googlebot-specific meta). On the response: X-Robots-Tag: noindex. Either one is enough for Google to exclude the URL.Does IndexRanger’s diagnose catch both?
The fetch already flags the meta robots tag. It does not currently parse X-Robots-Tag headers — confirm those in DevTools or curl. A live header checker is a later tool page, not this one.
I removed the tag. Why is it still excluded?
Google has to recrawl and see the new HTML. Request indexing once after the tag is gone. Related: how recrawl works.
If I remove noindex, will it index?
Not automatically. We submit and measure. Nobody can guarantee Google indexing. Removing noindex only makes the URL eligible.
Submit it after noindex is actually gone.
We record coverageState, including excluded-by-noindex, on each inspect. 25 free, no card.
Start free