Excluded by noindex tag
Usually correct, not an error: the pages that should carry a noindex, how to spot an accidental one, and the robots.txt trap that stops it working.
“Excluded by ‘noindex’ tag” means Google found a noindex instruction on the page and did exactly what it says: kept the page out of the index. This is not an error report. Most of the time it is Google confirming that a page you never wanted in search results is, correctly, not in search results. The status exists so you can check that every noindex on the list is one you actually meant.
This is usually correct, not a problem
Plenty of pages should carry a noindex, because they add nothing to search results and can dilute the pages that matter. If the URLs on your list look like these, the report is working as intended and you should leave it alone:
Login, account and admin pages. Checkout, cart and thank-you pages. Internal search-results pages. Thin tag or filter archives. Duplicate print or AMP-style variants. Staging or preview URLs. A well-run site deliberately noindexes all of these, and a healthy Page indexing report will always have a “noindex” count above zero as a result.
When it is an accident
The status only matters when a page you want in Google shows up on the list. That happens more often than it should, because a noindex is a single line that is easy to apply too broadly:
Left over from staging. Many teams noindex the entire staging site, then forget to remove it when the site goes live. The classic symptom is a brand-new site that will not index at all.
A CMS or plugin default. A “discourage search engines” checkbox, an SEO plugin’s per-template setting, or a theme option can quietly stamp noindex on a whole section.
A template applied too widely. A noindex added to one shared header or layout component lands on every page that uses it, not just the one you were thinking of.
If real content pages, category pages, or your blog posts appear here — or if traffic dropped suddenly and these pages went with it — treat it as urgent and find where the tag is coming from.
Where the noindex actually lives
There are two places a noindex can be set, and you have to check both:
In the HTML. A <meta name="robots" content="noindex"> tag in the page’s <head>. View source and search for “noindex”, or use the meta tag checker to read the robots meta directly.
In the HTTP response. An X-Robots-Tag: noindex header, sent by the server before the HTML. This one is invisible in the page source, which is why it is the harder of the two to track down. The indexability checker reads both the meta tag and the header in one pass and tells you which is in force.
How to get the page indexed again
Once you have found the source, remove the noindex from that template, plugin setting, or server rule. Then confirm the page is genuinely indexable again with the indexability checker — it is easy to remove one noindex and miss a second copy. Finally, use URL Inspection in Search Console and request indexing so Google re-crawls sooner rather than waiting for its next scheduled visit.
The robots.txt trap
There is one combination that quietly breaks: a noindex tag on a page that is also blocked in robots.txt. For Google to obey a noindex, it has to crawl the page and read the tag — but robots.txt tells it not to crawl at all. So the noindex is never seen, and the page can end up indexed even though it is blocked. If your goal is to keep a page out of Google, allow crawling and use noindex; do not block it in robots.txt. Only after the page has dropped out of the index is it safe to block crawling as well.
For how this status sits alongside the rest of the report — which counts are normal and which need action — see the Page indexing report reference, or run a full site check to confirm nothing you want in Google is being quietly excluded.
Frequently asked questions
- What does 'Excluded by noindex tag' mean in Search Console?
- It means Google found a noindex instruction on the page — either a robots meta tag in the HTML or an X-Robots-Tag HTTP header — and kept the page out of its index as instructed. It is a confirmation that Google obeyed the tag, not an error. The report lists these pages so you can check that each noindex is one you meant to apply.
- Is 'Excluded by noindex tag' a problem I need to fix?
- Usually not. Login, account, admin, checkout, thank-you, internal search, and thin tag pages should all be noindexed, so a count above zero here is normal and healthy. It is only a problem when a page you actually want to rank — a real content page, category, or blog post — appears on the list. Then you need to find and remove the tag.
- Where is the noindex tag coming from?
- From one of two places. Either a robots meta tag in the page's HTML head, which you can see by viewing source or with a meta tag checker, or an X-Robots-Tag header in the HTTP response, which is invisible in the page source and needs a tool that reads response headers. Common accidental sources are a leftover staging setting, a CMS or SEO-plugin default, or a noindex added to a shared template.
- How do I remove a noindex tag so my page gets indexed?
- Find whether the noindex is in the HTML meta tag or the HTTP header, then remove it at the source — the template, plugin option, or server rule that sets it. Confirm the page is indexable again with an indexability check, since it is easy to miss a second copy. Then use URL Inspection in Search Console to request indexing so Google re-crawls the page sooner.
- I removed the noindex but the page still is not indexed. Why?
- Removing the tag only makes the page eligible again; Google still has to re-crawl it, which can take days to weeks. Check that no second noindex remains (for example an X-Robots-Tag header as well as a meta tag), that the page is not blocked in robots.txt, and that it is linked internally so Google has a reason to re-crawl it. Then request indexing and give it time.
- Should I block a noindexed page in robots.txt too?
- No — not while you are trying to keep it out of the index. Google has to crawl a page to see its noindex tag, and robots.txt blocks that crawl, so the noindex is never read and the page can stay indexed. Allow crawling and use noindex to deindex a page. Only once it has dropped out of Google is it safe to also block it in robots.txt.