Excluded by 'noindex' Tag: Is It Normal, and How Do You Fix It?

Excluded by 'noindex' tag is the one indexing status you created yourself, on purpose or by accident. Google's Page indexing report documentation describes the reason in three sentences: "When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it. If you do not want this page indexed, congratulations! If you do want this page to be indexed, you should remove the 'noindex' directive." This guide helps you decide which side of that sentence each URL is on, find the exact source of an unwanted rule, and fix it without breaking anything else.

What does "Excluded by 'noindex' tag" mean?

A noindex rule tells search engines not to show a page in their results. Google reads it in two places, as its guide to blocking indexing with noindex explains:

• A robots meta tag in the <head> of the HTML: <meta name="robots" content="noindex"> for all search engines, or name="googlebot" for Google only.
• An X-Robots-Tag HTTP header sent by the server with the response, with the value noindex or none. This is the only option for files without HTML, such as PDFs.

When Googlebot finds either one, it keeps the URL out of the index. The status appears in Google Search Console under Indexing, then Pages, in the table "Why pages aren't indexed". The help page lists the same reason as "URL marked 'noindex'"; both labels describe one situation.

Three facts change how you read the report:

• Google obeyed you. Unlike "Crawled - currently not indexed", where Google decides against a page, this status reflects an instruction the site sent.
• It requires a crawl. Google can only see a noindex rule on a page it is allowed to fetch. A page blocked by robots.txt never reaches this status.
• The rule can come from anywhere in the chain. HTML, CMS, plugin, theme, server configuration and CDN can each add it, and the page source does not show HTTP headers.

Is it normal or an error?

Most sites have URLs in this status, and many of them belong there. Google's report states that pages listed as not indexed are there "not necessarily because of an error". Sort the list by URL type before fixing anything.

The last line matters more than it looks. A sitemap tells Google "index these pages", a noindex says the opposite. Keep the sitemap limited to indexable, canonical URLs (our guide to submitting a sitemap to Google covers how to clean it).

Where does an unwanted noindex come from?

When an important page carries noindex, the cause is almost always one of the sources below. Check them in this order, from the most frequent to the rarest.

The WordPress case is common enough to name. According to the WordPress documentation on the Reading screen, ticking "Discourage search engines from indexing this site" adds noindex,nofollow in the head of every page (since version 5.3). One forgotten checkbox after a launch is enough to remove a whole site from Google. Site launches and redesigns are the riskiest moments, which is why an SEO migration checklist always includes a check of robots rules. For WordPress-specific settings, see our page on WordPress SEO and GEO.

How do you diagnose the status, step by step?

1. Open the report. In Search Console, go to Indexing, then Pages, click "Excluded by 'noindex' tag" and export the list.
2. Sort the URLs with the table above. Set aside those that should stay out of the index.
3. Inspect one important URL. Paste it in the URL Inspection tool. The "Indexing allowed?" line tells you whether Google saw noindex and whether it came from the robots meta tag or the X-Robots-Tag header.
4. Test the live URL. Click "Test live URL": if the live version no longer has noindex, the rule was already removed and Google only needs a recrawl.
5. Check both places yourself. Look for noindex in the page source, then in the response headers (browser developer tools, Network tab). A free HTTP headers checker shows the X-Robots-Tag without opening any developer tool, and the indexability checker tests meta tag, header and robots.txt in one pass.
6. Trace the source with the sources table, starting with the CMS setting and the SEO plugin.

How do you fix it?

The fix depends on the source. Change the setting where the rule is generated, never only the visible output, or it comes back at the next update.

After the fix, request indexing for the most important URLs in the URL Inspection tool, and resubmit the sitemap if many pages were affected. For a group of fixed URLs, click "Validate fix" in the report; Google says validation "typically takes up to about two weeks, but in some cases can take much longer." Clear any page cache or CDN cache first, or Google may fetch the old version with the old rule. If pages still do not appear weeks later, our guide to getting pages indexed by Google lists the next levers, and if they move to Crawled - currently not indexed, the problem is now the content, not the rule.

Noindex, robots.txt or canonical: which one should you use?

The three tools are often mixed up, and combining them wrongly creates the most confusing reports.

Google states it plainly: if robots.txt blocks a page, "the crawler will never see the noindex rule." If you want a page out of the index, leave it crawlable with noindex until it disappears, then decide whether to block it. Test your file with the robots.txt checker, and read the robots meta tag specification for the full list of rules; it also notes that when rules conflict, "the more restrictive rule applies."

Why does it matter for SEO and for AI visibility?

A page under noindex receives no organic clicks from Google, whatever its quality. On a large site, an unwanted rule on a template can remove hundreds of product or article pages at once, and the first sign is often a drop in traffic weeks later. If your site seems to have disappeared altogether, start with our checklist on a website not showing up on Google.

AI assistants add a second cost. ChatGPT, Perplexity and Gemini often answer by retrieving pages from web search indexes and citing them, so a page missing from the index has little chance of being cited. Our study of the platforms AIs cite most shows which sources they favour.

Sorank is our product: an autopilot SEO and GEO software. Its GEO and SEO dashboard shows clicks, impressions and positions from Search Console, so a sudden fall in impressions on a group of pages stands out quickly, and the free Sorank Chrome extension flags SEO issues on any page you open.

The short version: leave noindex on pages that should never rank, remove it at the source on pages that should, keep the sitemap free of noindexed URLs, and never block a page in robots.txt while waiting for Google to read its noindex. To publish pages built to be indexed and cited, see Sorank's plans, from $49 per month with a 3-day free trial.