Excluded by Noindex Tag in Search Console: Find and Remove It

"Excluded by 'noindex' tag" is one of the clearest statuses in Google Search Console, and one of the most expensive when it is a surprise. It means Google fetched the page, found a rule telling it not to index the page, and obeyed. If you put that rule there on purpose, the report is working as designed. If you did not, a page that should bring visitors is invisible to search.

This guide is for site owners and developers who see the status on pages that should be indexed. You will learn how to decide which URLs are meant to be noindexed, where an accidental rule can hide (page source, HTTP headers, CMS settings, plugins, scripts), how to remove it, and how to confirm that Google can now index the page. It will not promise that removing noindex gets the page indexed. It only removes the instruction that said no.

Before you begin

You need Search Console access, a way to see raw page source and response headers (a browser plus curl), and the ability to edit templates, CMS settings, server configuration or plugin settings. Know who else can change those: a marketing plugin, a developer, a host and a CDN can all add a noindex rule.

Allow an hour to find the source, longer if the rule comes from several places. Take a note of the current setting before you change it. Be careful with sites that have a staging copy. A rule meant for staging may have travelled to production, and removing the rule from the wrong environment can expose a staging site to search engines. Treat live and staging as separate checklists.

What the status means

Google's Page Indexing help says that "Excluded by 'noindex' tag" means Google found a noindex directive when it tried to index the page, and did not index it. If you want the page indexed, remove the noindex tag or HTTP header. To confirm, use the URL Inspection tool and check "Indexing allowed?" on the live test.

Google's documentation on blocking indexing explains the two forms. One is a meta tag in the page's <head>:

<meta name="robots" content="noindex">

A variant named googlebot targets only Google's crawlers. The other is an HTTP response header, which also works for non-HTML files such as PDFs:

X-Robots-Tag: noindex

Both have the same effect. The rule must be visible to the crawler, which is why a page blocked in robots.txt cannot be fixed by reading the report alone. See Noindex vs Robots.txt for the relationship between the two.

Step-by-step instructions

Step 1: Decide which pages should be noindexed

Export the URLs from the report (Indexing, then Pages, then the noindex reason) and mark each one. Typical intended noindex pages are thank-you pages, internal search results, account pages, carts, and thin utility pages. Pages you want in search include products, articles, services, categories and the home page. If your home page is on the list, treat it as urgent.

What success looks like: The list is split into "intended" and "should be indexed".

Step 2: Check the page source

Open one "should be indexed" URL, choose view-source and search for noindex. Check for several meta tags. A page can have more than one robots tag, and Google combines rules from multiple sources. Google also states that where rules conflict, the more restrictive one applies. Look for both name="robots" and name="googlebot".

curl -s https://example.com/page | grep -i -E 'name="(robots|googlebot)"'

Note which tag you find and which template output it.

What success looks like: You can point to the exact line in the HTML that carries noindex, or you confirm it is absent from the raw HTML.

Step 3: Check the HTTP headers

If the HTML is clean, look at the response headers, since the same rule can come from the server, a CDN or a security layer:

curl -sI https://example.com/page | grep -i x-robots-tag

If X-Robots-Tag: noindex appears, find where it is set: web server configuration, .htaccess, web.config, application middleware, a CDN rule or a hosting platform setting. The X-Robots-Tag guide lists the places to look. Also check unavailable_after values: a rule with a date in the past can remove a page from results after that date.

What success looks like: You know whether the rule comes from the HTML, a header or both.

Step 4: Check CMS and plugin settings

Many content systems can add a noindex rule site-wide or per page.

On WordPress, the Reading settings screen has the "Discourage search engines from indexing this site" option. WordPress documentation says that since version 5.3 the option causes a <meta name='robots' content='noindex,nofollow' /> tag to be added to the site's head, and that the setting only asks search engines not to index the site, because it is up to them to honour it. SEO plugins also have per-page and per-post-type switches, so check the individual page's SEO panel and the plugin's settings for post types and taxonomies. The WordPress discourage search engines guide covers it in detail.

For other platforms, look for a "hide from search engines" or "search engine visibility" option on the page, in the site settings and in the template. For headless or custom sites, search the code for noindex and for the name of any robots header.

What success looks like: You found the setting or code responsible, or ruled out the CMS.

Step 5: Check scripts and tag managers

A noindex tag can also be added by JavaScript. Google's JavaScript SEO documentation describes adding a noindex robots meta tag with JavaScript to error views in single-page apps, which shows that scripts can set it. A tag-management or A/B testing script, or a single-page app that applies the tag to all routes, can do this by accident. In URL Inspection, the "View crawled page" and live test show the rendered HTML Google saw; look for a robots meta tag there. If it exists only in the rendered HTML, the cause is a script.

What success looks like: You know whether scripts add or remove robots tags on the page.

Step 6: Remove the rule at the source

Fix it where it is generated, not on one page. Remove the meta tag from the template, turn off the CMS option, delete the header rule or correct the script condition. If the rule exists because of staging, make sure the production build does not include it, and keep noindex on staging by other means. See How to keep a staging site out of search.

After the change, request the page again with curl and view-source. The tag or header should be gone from the live response. Check a sample from every page type: home page, article, category, product.

What success looks like: Raw HTML and headers for each page type no longer contain noindex.

Step 7: Test live and ask Google to recheck

In URL Inspection, run the live test on a corrected URL and read "Indexing allowed?". It should say yes. Then press "Request indexing". Google says this asks it to crawl and queue the URL, does not mean the page will be indexed, is limited per day, and cannot be used for a URL the live test shows as non-indexable. Request only your most important URLs; see Request Google Indexing the Right Way.

Google explains that after you change a noindex rule it must recrawl the page, which depends on the page's importance and can take months. For many URLs, a sitemap with accurate lastmod values helps Google notice changes.

When every instance is fixed, press "Validate fix" on the issue. Google says validation typically takes about two weeks but can take much longer.

What success looks like: The live test shows indexing is allowed, and the pages leave the noindex report as Google recrawls them.

Final verification checklist

Every URL in the report is marked intended or should be indexed.
Pages that should be indexed have no robots meta tag containing noindex.
Those pages return no X-Robots-Tag: noindex header.
CMS, plugin and SEO settings no longer discourage indexing for those pages.
Rendered HTML in the live test has no noindex added by scripts.
robots.txt does not block the pages, so Google can see the corrected state.
URL Inspection shows "Indexing allowed? Yes" for a sample of each page type.
Staging and production have different settings, and staging stays noindexed.

Common mistakes to avoid

Removing noindex from intended pages. Thank-you pages, carts and internal search results often should stay out of search.
Fixing one page when the source is a template. Fix the template or setting, or the rule returns.
Forgetting HTTP headers. A clean page source does not rule out a header from the server or CDN.
Blocking the page in robots.txt while fixing it. Google must be able to crawl the page to see that noindex is gone.
Leaving a staging noindex in a production release. Add a launch check that compares the live HTML and headers.
Expecting instant indexing. Removing noindex only permits indexing. Google must recrawl the page and decide.
Ignoring plugin defaults. Some SEO plugin settings apply noindex to whole content types.
Requesting indexing for hundreds of URLs. Quotas apply; update the sitemap instead.

Frequently asked questions

Is "Excluded by noindex tag" an error?

Only when the page should be indexed. Google reports it because it found a directive and followed it.

How do I find the noindex tag on my page?

View the page source and search for noindex, check the response headers for X-Robots-Tag, and check the rendered HTML in URL Inspection for scripts that add the tag.

How long until my page is indexed after I remove noindex?

Google must recrawl the page, which depends on the page's importance and can take months for some URLs. Requesting indexing and keeping an accurate sitemap can help it notice sooner.

Why does noindex appear even though I did not add it?

Common sources are a CMS option such as WordPress's discourage search engines setting, an SEO plugin, a server or CDN header rule and leftovers from staging.

Does noindex remove my page from Bing too?

Bing says it honours robots meta tags, and that adding noindex to your page source makes the page disappear from its index after it is recrawled and reprocessed. Check Bing Webmaster Tools if you also depend on Bing.

Can I see noindex pages in the URL Inspection tool?

Yes. The tool's "Indexing allowed?" field reports whether indexing is explicitly blocked, for example by a noindex tag, and shows the reason.

Does Crawvix check for an accidental noindex?

Yes. Its "No accidental noindex" check reads the robots meta tag and the X-Robots-Tag header on the pages it loads and reports pages marked noindex, while ignoring login, cart and similar pages that are normally hidden on purpose.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.