Excluded by Noindex Tag: How to Find and Fix It in Search Console

This guide shows you how to read the excluded by noindex tag status in Google Search Console, decide which pages actually need fixing, and remove the rule safely. In my orders I see this status on almost every WordPress site I audit, and most of the time only a handful of the listed URLs are real problems.

Why are my pages excluded by noindex tag?

Your pages are excluded because Google found a noindex directive when it tried to index them, so it obeyed that instruction and kept them out of search results. Google’s help page for the Page indexing report lists this reason as “URL marked ‘noindex'” and explains that the directive must be removed if you want the page indexed.

The rule can live in two places. The first is a meta tag in the page head, such as <meta name="robots" content="noindex">. The second is an HTTP response header, X-Robots-Tag: noindex, which is common on PDFs and on sites where a server or CDN rule adds headers. Both methods are described in Google’s guide to blocking indexing with noindex.

The usual causes I find in client audits are:

• The WordPress setting “Discourage search engines from indexing this site” was left on after launch or after a staging copy was pushed live.
• An SEO plugin sets tag archives, author pages, attachment pages or search results to noindex by default.
• A page builder template or a theme adds a robots meta tag to every page using that template.
• A server, Cloudflare rule or hosting panel adds an X-Robots-Tag header to a whole folder.
• Someone noindexed thin pages during a cleanup and later improved them but forgot to switch the rule off.

Should I fix excluded by noindex tag pages?

You should only fix the pages you actually want to rank; noindex pages that you added on purpose are working as intended. Google’s own Page indexing report documentation notes that not indexed is not necessarily bad, and a healthy site often has many pages it deliberately keeps out of search.

I sort every URL in the report into one of three buckets before touching anything. This decision table is the same one I use in my technical SEO service:

The last row matters. A sitemap tells Google “please index this”, while noindex says the opposite. Sending mixed signals wastes crawling and makes the report harder to read, so keep the two lists consistent.

How do I remove a noindex tag in WordPress?

In WordPress you remove a noindex tag by turning off the site wide visibility setting and then checking the robots setting of each affected post in your SEO plugin. Work from the widest cause to the narrowest so you do not waste time editing pages one by one when one checkbox caused everything.

1. Export the list. In Search Console open Pages, click the noindex reason and export the example URLs to a sheet. Mark each one keep or fix using the table above.
2. Check the site wide switch. In WordPress go to Settings, then Reading, and make sure “Discourage search engines from indexing this site” is unticked. Save.
3. Check plugin defaults. In Yoast, Rank Math or All in One SEO, open the content type settings (posts, pages, products, categories) and confirm the types you want indexed are set to show in search results.
4. Check single posts. Open an affected post, go to the advanced or robots section of your SEO plugin box and set it to index. Update the post.
5. View the source. Open the live URL, view page source and search for “noindex”. If it is still there, a theme, page builder or second plugin is printing it.
6. Check the HTTP header. Use your browser developer tools (Network tab, click the document, look at response headers) to see if an X-Robots-Tag header is present. If it is, look at .htaccess, Nginx config, your host panel or CDN rules.
7. Clear caches. Purge your caching plugin, server cache and CDN so Google receives the new version.
8. Update the sitemap. Confirm fixed pages appear in the sitemap and pages you keep as noindex do not.
9. Add internal links. Link to the fixed pages from relevant posts so Google finds them again sooner.

One warning from Google’s documentation: a noindex rule only works if Google can crawl the page. If you also block the URL in robots.txt, Googlebot never sees the tag. You can check that with my free robots.txt tester before you move on.

How do I validate the fix in Search Console?

You validate the fix by testing one fixed URL live, confirming indexing is allowed, and then clicking Validate fix on the noindex issue in the Page indexing report. Doing it in that order avoids a failed validation caused by a page you missed.

1. Paste a fixed URL into the URL Inspection bar at the top of Search Console.
2. Click Test live URL. In the result, open the page availability details and check that “Indexing allowed?” says Yes.
3. If it is fine, click Request indexing for your most important pages only. There is a daily limit, so save it for money pages.
4. Go back to Pages, open the noindex reason and click Validate fix.
5. Wait. Google’s help page says validation typically takes up to about two weeks and sometimes longer. Do not click Validate fix again while it is running.

Pages you chose to keep as noindex will remain in the report, and that is fine. Validation only fails when a certain share of the URLs Google rechecks still carry the issue, which is another reason to remove intentional noindex URLs from your sitemap first. If you see other statuses in the same report, my guide to Search Console indexing errors explains each one.

What does a real noindex cleanup look like?

The lesson: always group by template first. When I see ten or more real pages with the same problem, the cause is almost never ten separate mistakes. If you would rather have someone go through the report with you, the free audit request is the quickest way to start.

Should I use noindex or robots.txt to hide pages?

Use noindex to keep a page out of Google’s index, and use robots.txt only to manage crawling. Google states that robots.txt is not a way to keep a page out of search results, because a blocked URL can still be indexed if other pages link to it.

If a page is both disallowed in robots.txt and tagged noindex, Google cannot read the tag. To remove a page cleanly, allow crawling, keep the noindex rule until the page drops out, and only then decide whether a robots.txt block is useful for crawl control.

Frequently asked questions

Sources

Facts checked against these official pages. Read how I check facts in my editorial policy.

• Google Search Console Help: Page indexing report
• Google Search Central: Block Search indexing with noindex