Excluded by Noindex Tag: How to Find the Source and Fix It [2026]

A single checkbox can remove an entire website from Google. So can one line in a server config, or a setting copied across from a staging site during launch week.

When that happens, Search Console reports the affected URLs as "Excluded by 'noindex' tag". The excluded by noindex tag status is sometimes exactly what you asked for: thank-you pages, internal search results and admin screens should stay out of search. But when it appears on your homepage, your services or your products, you are invisible until the noindex is found and removed.

This guide shows you how to tell intended from accidental noindex, how to track down where the directive comes from, how to fix it on WordPress and other platforms, and how to handle the "Submitted URL marked 'noindex'" variant.

Key Takeaways

• Google obeyed an instruction. It found a noindex directive when it tried to index the page, so it left the page out.
• Intended noindex needs no fix. Google's own help says that if you did not want the page indexed, the status is working as designed.
• Accidental noindex has a handful of sources. WordPress's "Discourage search engines" setting, SEO plugin settings, staging leftovers, X-Robots-Tag headers and JavaScript cover most cases.
• Check the headers, not just the HTML. A noindex in an HTTP header is invisible when you view the page source.
• Do not remove noindex with JavaScript. Google may skip rendering once it sees noindex, so the removal may never be read.
• Validation takes time. Google says validation typically takes up to about two weeks, and sometimes longer.

What Does Excluded by Noindex Tag Mean?

Quick answer: Excluded by 'noindex' tag means Googlebot crawled the page, found a noindex directive in a robots meta tag or an X-Robots-Tag HTTP header, and therefore did not index it. If you meant to hide the page, nothing needs fixing. If you want the page in Google, find where the noindex comes from, remove it, confirm with a live test in URL Inspection, and request indexing.

Search Console shows this status as "Excluded by 'noindex' tag". Google's Page indexing report help lists the same reason as "URL marked 'noindex'", and explains that Google encountered a noindex directive when it tried to index the page. The help page is refreshingly direct: if you did not want the page indexed, congratulations; if you did, you should remove the directive.

Google's noindex documentation adds that once Googlebot extracts the tag or header, it drops the page from Search entirely, regardless of whether other sites link to it.

Noindex and the Three Canonical Statuses

Noindex is often confused with canonicalisation, because both keep a URL out of the index. They are different tools, and Google's guidance says it does not recommend noindex for choosing a canonical within a site, because it blocks the page from Search completely. If your URLs appear under one of these statuses instead, the fix is different:

Use a canonical tag when a page duplicates another page. Use noindex only when a page should never appear in search at all.

Intended or Accidental?

Start by sorting the URLs in the report. Many noindex tags are deliberate, and removing them would add low-value pages to the index.

If you want to hide a page from Google, you can relax. If a page in the right-hand column is listed, work through the sources below.

The Noindex Meta Tag and Header

A noindex directive can live in two places. The first is the noindex meta tag in the page's HTML. The second is an HTTP response header, which you cannot see in the page source. Google's robots meta tag documentation covers both.

<!-- In the <head> of the HTML page -->
<meta name="robots" content="noindex">

<!-- Applies to Google only -->
<meta name="googlebot" content="noindex">

HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
X-Robots-Tag: noindex

Two rules from Google's documentation matter here. First, when robots rules conflict, the more restrictive rule applies, so one stray noindex beats any number of "index" values. Second, these directives are only read if crawlers can access the page.

Where Accidental Noindex Comes From

WordPress's "Discourage search engines" setting

This is the most common cause on WordPress sites. Under Settings, then Reading, the Search engine visibility option has a checkbox labelled "Discourage search engines from indexing this site". According to the WordPress documentation, since version 5.3 ticking it adds a robots meta tag with noindex and nofollow to the <head> of every page. Developers often tick it while building a site, and it survives launch.

Yoast SEO and Rank Math settings

SEO plugins control noindex at two levels. In Yoast SEO, each post's Advanced tab asks "Allow search engines to show this content in search results?", and answering No sets noindex. The default for each content type comes from Yoast's Search Appearance settings. In Rank Math, the Advanced tab of the post's metabox holds the Robots Meta setting, and the site-wide defaults live under Rank Math SEO, then Titles & Meta.

Check both levels. A single post set to noindex affects one URL, while a content type default can affect hundreds.

Staging leftovers

Staging sites are usually noindexed, and migrations copy more than content. A database push can carry the WordPress visibility setting across, a deployment can ship a staging config file, or an environment variable that adds noindex may never be switched off in production.

X-Robots-Tag headers

Servers, hosting panels, CDNs and security plugins can all add X-Robots-Tag headers. They are common on PDFs and other files, where rules often target a whole file type, but a broad rule can catch HTML pages too. Because the header never appears in the HTML, people can stare at a clean page source for hours without finding it.

JavaScript-injected noindex

Some sites add or change the robots meta tag with JavaScript. Google's JavaScript SEO basics warns that when Google encounters noindex it may skip rendering and JavaScript execution. So a page that starts with noindex in its HTML and removes it with JavaScript may stay excluded. If you want a page indexed, keep noindex out of the original page code.

Website builders

On Wix, each page's SEO panel has a "Let search engines index this page" toggle under SEO Basics, and site-wide or page-group settings exist in the dashboard. Other builders have similar switches, often inside page or site privacy settings.

How to Find the Source: Step by Step

Google's help page gives the core of this process. Here it is in full:

1. Open the report. In Search Console, go to Indexing, then Pages, and click "Excluded by 'noindex' tag". Check whether important URLs are listed.
2. Inspect a URL. Click the inspection icon. Under Coverage, then Indexing, then Indexing allowed?, Search Console shows that noindex is preventing indexing.
3. Run a live test. Click Test live URL and look under Availability, then Indexing, then Indexing allowed? to see whether the noindex is still there today.
4. Search the HTML. View the page source and search for "noindex". Compare it with the rendered HTML in the live test, since JavaScript may add the tag after load.
5. Check the response headers. Use your browser's developer tools (Network tab) or run curl -I https://www.example.com/page/ and look for an X-Robots-Tag line.
6. Trace the output. For a meta tag, check the CMS visibility setting, the SEO plugin at page and content-type level, and the theme. For a header, check server config, hosting, CDN rules and security plugins.
7. Confirm Google can crawl the page. Google's noindex documentation says that if robots.txt blocks a page, Google never sees the noindex rule, or its removal. Test the URL with our robots.txt tester.

Excluded by Noindex Tag Fix: Solutions by Cause

How to Fix Excluded by Noindex Tag in WordPress

For WordPress specifically, work in this order, because it moves from the widest setting to the narrowest:

1. Go to Settings, then Reading, and make sure "Discourage search engines from indexing this site" is unticked.
2. Open your SEO plugin's site-wide settings and confirm that posts, pages and any custom post types are allowed in search results.
3. Open an affected post and check the plugin's Advanced tab for a page-level noindex.
4. Clear every cache layer: the page cache plugin, the host's cache and the CDN. A cached copy can keep serving the old noindex after you fix the setting.
5. View the source and headers again, then run a live test in URL Inspection.

Once the noindex is gone, the page still has to earn its place in the index. Our guide on how to get Google to index your WordPress website covers sitemaps, internal links and requests for indexing.

The "Submitted URL Marked 'noindex'" Variant

Older versions of Search Console used a separate label, "Submitted URL marked 'noindex'", for URLs that appeared in a sitemap and carried a noindex. It signals a contradiction: the sitemap says "index this", and the page says "do not".

In the current Page indexing report, you can recreate that view. Google's help explains that the sitemap filter above the chart can show All submitted pages, and that a URL counts as submitted even if Google also found it another way. Filter to submitted pages, open the noindex status, and resolve each URL one of two ways:

• You want it indexed: remove the noindex and keep it in the sitemap.
• You do not want it indexed: keep the noindex and remove the URL from the sitemap.

How to Validate the Fix

1. Confirm the noindex is gone from both the HTML and the HTTP headers.
2. Run Test live URL and check that "Indexing allowed?" no longer reports noindex.
3. Click Request Indexing for your most important pages, as Google's help page suggests.
4. Return to the status in the Page indexing report and click Validate fix.
5. Monitor progress. Google's help says validation typically takes up to about two weeks, but in some cases much longer.

Removing noindex makes a page eligible for indexing, not guaranteed to be indexed. If pages move into "Crawled - currently not indexed" afterwards, our guide to fixing Crawled, currently not indexed explains the next step. For sites that need many pages indexed quickly after an accidental noindex, our Google indexing services cover the whole recovery.

How Billion Game Handles Noindex Recoveries

Accidental noindex is one of the fastest indexing problems to fix once the source is found, and one of the slowest to notice. Our specialist team checks the HTML, headers, CMS settings and deployment pipeline together, fixes the source rather than individual pages, and adds a launch check so it does not come back. Reporting comes from your own Search Console, with raw exports attached.

If key pages are stuck behind a noindex you cannot find, our Google Search Console issue fixing service can trace and remove it.

Frequently Asked Questions

Final Thoughts

Noindex does exactly what it says, which is why a mistaken one is so costly. Google will not index a page that tells it not to, however good the page is.

Sort intended exclusions from accidental ones, check the headers as well as the HTML, fix the setting at its source, and keep noindexed URLs out of your sitemap. Do that, and excluded by noindex tag goes back to being what it should be: a list of pages you chose to keep out of Google.

About the author

Ganesh Shanmugam

Ganesh Shanmugam is an SEO and AEO consultant based in Chennai, India, and the founder of Billion Game — a boutique agency serving clients across the US, UK, Australia, Canada, and Ireland. He previously held SEO roles at 7 Eagles and Digital Scholar before going independent, and brings 4+ years of hands-on experience

More from Billion Game →