Excluded by noindex tag shows up in the Page indexing report in Search Console, and it tends to cause more alarm than it deserves. The report is listing pages where Googlebot found a noindex rule and left them out of the index as instructed. A long list under this heading can be a sign of a healthy site that keeps its thin pages out of search. The job is to sort the list into pages that should be there and pages that should not.
What excluded by noindex tag means
Google’s documentation on blocking search indexing with noindex describes two ways to apply the rule, and Search Console treats both the same way.
| Meta robots tag | X-Robots-Tag header | |
|---|---|---|
| Where it lives | In the page <head> | In the HTTP response headers |
| What it looks like | <meta name="robots" content="noindex"> | X-Robots-Tag: noindex (or none) |
| Works on | HTML pages | Any file, including PDFs and images |
| Where to check | View the page source | The network tab of your browser’s developer tools |
| Who usually sets it | An SEO plugin, theme or template | Server or CDN configuration |
The header is the one people forget. If the page source looks clean and the page is still reported as noindexed, check the response headers before assuming Search Console is wrong.
When the status is correct, and when it is not
Plenty of pages should carry noindex. Tag archives that list the same posts in a different order, thank-you pages after a form, internal search results, login and account pages, and staging copies all belong outside the index. If those are what fill the report, there is nothing to fix. Removing noindex from them would add thin pages to the index and give Google more low-value URLs to judge your site by.
The status is a problem only when the URL is one you expect to rank: a product page, a service page, a post that earns traffic. Export the report, sort by URL path, and mark each group as intended or accidental. That one pass usually shows whether you are looking at a handful of mistakes or one template applying noindex everywhere.
The common accidental causes
When important pages are excluded, the cause is rarely a hand-written tag. It is usually a setting that applied noindex to more than someone intended.
- A CMS-wide “discourage search engines” option. Many platforms have a single checkbox, meant for development sites, that noindexes everything. It is often left ticked after a launch.
- An SEO-plugin content-type setting. Plugins let you noindex whole post types, categories or taxonomies. One wrong toggle can remove every page of a type.
- A per-page advanced setting. A noindex box ticked on a single page, sometimes copied across when that page was duplicated as a template.
- A header set at server or CDN level. A rule meant for a staging hostname or a file directory that also matches live URLs.
Check them in that order. The sitewide option explains a sudden drop across the whole site; the plugin setting explains a whole section; the per-page box explains scattered single URLs.
Noindex, robots.txt and nofollow are not interchangeable
The most damaging mistake here is combining noindex with a robots.txt block. Google is explicit: “For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file.” If it is blocked, “the crawler will never see the noindex rule, and the page can still appear in search results.” Blocking a page in robots.txt to make doubly sure it stays out can therefore have the opposite effect. Our guide to robots.txt for SEO covers what the file does and does not control.
Nofollow is a different thing again. Noindex is about whether the page itself is indexed; nofollow is about the links on it, or a single link. A page can be noindexed and still have its links followed, and a nofollowed link does not stop the target page being indexed. Our post on nofollow links covers the link side.
A canonical tag pointing to another URL and a noindex on the same page send mixed messages: one says “index that version instead”, the other says “index nothing”. Pick the one that matches what you want.
How to fix excluded by noindex tag on pages that should rank
- Confirm the rule is still there. Open the page source and the response headers. If neither shows noindex, the report may be reflecting an older crawl.
- Find the setting that applied it. Work from sitewide to per-page, as above. Fix the setting, not just the one URL, or the next page published will have the same problem.
- Check robots.txt is not blocking the URL. Google has to crawl the page to see that the noindex is gone.
- Inspect the URL in Search Console. URL Inspection shows what Google saw on its last visit and lets you test the live page.
- Validate the fix. Once the group is corrected, use the validation option in the Page indexing report and let Google recrawl.
Removing the tag makes a page eligible for indexing; it does not guarantee it. A page that was noindexed for months may come back as “crawled, currently not indexed” if Google does not think it adds enough. That is a different status with a different fix, covered in crawled, currently not indexed.
What the report cannot tell you
The limitation is that the report tells you Google found a noindex rule, not who put it there or whether it was meant. Only your own records can answer that. A team that documents which templates and content types are noindexed on purpose can read this report in minutes; a team that does not will rediscover the same tag archives every quarter.
Treat the report as an inventory rather than an alarm. Once a month, export it and compare the URL groups with last month’s. A new group appearing is worth investigating the same day, because it usually means a plugin update, a theme change or a deployment switched something on. A stable list of archives and utility pages is the report working as designed.
If you are launching a new site, the sitewide option is the first thing to check. A site that was built with search engines discouraged and launched without changing it will show every page under this status, and no amount of waiting fixes it. Once it is off, our guide on getting a website indexed by Google covers what to do next. For a wider view of how indexing problems fit into site strategy, the strategy archive collects the related posts.
Frequently asked questions
Is excluded by noindex tag bad for SEO?
Not by itself. It means Google respected a noindex rule. It matters only when the excluded page is one you want to rank.
Should I block noindexed pages in robots.txt as well?
No. Google says the page must not be blocked by robots.txt for noindex to work. If it is blocked, Google never sees the rule and the URL can still appear in results.
What is the difference between noindex and nofollow?
Noindex keeps the page itself out of the index. Nofollow concerns links, either all the links on a page or a single link, and does not control whether a page is indexed.
Can noindex be applied to a PDF?
Yes, through the X-Robots-Tag HTTP header. A meta tag only works in HTML, but the header works for non-HTML files such as PDFs and images.
The takeaway Sort the report into intended and accidental. Leave the intended pages alone, fix the setting behind the accidental ones, and never pair noindex with a robots.txt block.
