“Excluded by 'noindex' tag” in Google Search Console

What the status means

Google crawled the page and found a noindex directive, either in a robots meta tag or in the X-Robots-Tag HTTP header. It followed the instruction and kept the page out of search.

Google's help calls this status “URL marked 'noindex'”, while the Search Console interface usually shows “Excluded by 'noindex' tag”. They're the same thing.

Is it a problem?

Many of these URLs are there on purpose, so compare the list with the pages you expect in search.

How to find the directive

1. Open Indexing → Pages → Excluded by 'noindex' tag and look for pages you want indexed. A whole section points to a template or a setting rather than a single page.
2. Check the URL below. The checker reads both the meta tag and the header, and tells you which one blocks indexing. The header never shows up in the page source, so it's easy to miss when you only look at the HTML.
3. Confirm the live state. In URL Inspection, click Test live URL and look at Indexing allowed?. If the noindex is gone from the live page, you can request indexing. If it's still there, it has to be removed first.

Where the directive comes from

CMS and plugin settings. The most common source, and easy to switch on across a whole site by accident.

A template. A shared layout or category template that adds the tag to every page using it.

A staging setting that reached production. A launch or a migration copies over the “hide from search” option.

The server or CDN. An X-Robots-Tag rule in nginx, Apache or a CDN transform. It applies to whatever matches the rule, including pages your CMS says are indexable. If the CMS looks clean and the checker still reports noindex in the header, look here.

JavaScript. The original HTML has noindex, and a script is supposed to remove it. Google's documentation warns that this may not work: when Google sees noindex, it may skip rendering, so the script never runs. If you want the page indexed, don't put noindex in the original HTML.

How to fix it by platform

WordPress

• Settings → Reading: make sure Discourage search engines from indexing this site is off. It's the site-wide cause.
• Yoast: check the page (Advanced → Allow search engines to show this content in search results?) and the defaults per content type under Settings.
• Rank Math: check the page (Advanced → Robots Meta) and Titles & Meta for the content type.

Shopify

• Look for the seo.hidden metafield on the item, often set by an SEO app.
• Search theme.liquid for noindex. Some themes and apps add it conditionally.

Wix and Squarespace

• Wix: the page's SEO settings, Let search engines index this page.
• Squarespace: the page's SEO settings, Hide page from search results. Check the collection settings too.

Next.js and headless sites

• Check robots in the page's metadata and in the root layout, since a value there applies to every page that doesn't override it.
• Look for logic tied to an environment variable, such as noindex on everything except production. A wrong value on the production server gives you a site-wide noindex.
• In a headless setup, the SEO plugin in the CMS may pass its own robots value to the frontend. Check both ends.

After fixing

1. Check the URL again with the checker: both the meta tag and the header should be clean.
2. Request indexing in URL Inspection for your most important pages.
3. Run Validate fix for the issue. Google says validation typically takes up to about two weeks, and in some cases much longer.

The page should then move to indexed, unless Google has other reasons to leave it out. If it lands in Crawled - currently not indexed, the noindex is gone and the question is now about the page itself.

Using noindex correctly

• Don't combine it with a robots.txt block. Google's documentation says the page must not be blocked by robots.txt for the rule to work, because a crawler that can't fetch the page never sees the directive. That combination leads to Indexed, though blocked by robots.txt.
• Use the header for files. PDFs and other non-HTML files can't carry a meta tag, so use X-Robots-Tag.
• Don't use it on pages you only want to consolidate. If two pages are duplicates and you want signals in one place, use a canonical or a redirect.