How to Fix 'Excluded by noindex Tag' in Search Console

"Excluded by noindex tag" is a status in Google Search Console's Page indexing report. It means Google crawled the page, found an instruction not to index it, and followed that instruction. For login pages, thank-you pages and internal search results, that is exactly what you want. For a product page or a blog post you expected to rank, it usually means a noindex was left behind by a staging setting, a plugin or a template.

What "Excluded by noindex Tag" Means

A page can tell search engines not to index it in two ways:

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

HTTP/2 200
content-type: text/html
x-robots-tag: noindex

Either one is enough. If Google sees either, the URL is listed as excluded by noindex tag and stays out of search results. In newer versions of Search Console the same reason can appear as "Excluded by 'noindex' tag". The fix is the same.

Step 1: Decide Which URLs Should Be Indexed

Export the list from Indexing, then Pages, then the "Excluded by noindex tag" row. Sort the URLs into two groups.

Leave the first group alone. Only the second group needs fixing. If it is a single page, look at that page. If it is a whole section or every page, look for a site-wide setting.

Step 2: Find Where the noindex Comes From

• View the page source and search for noindex. Check the rendered page too, because JavaScript can add a robots tag after load.
• Check the response headers with curl -sI https://example.com/page and look for x-robots-tag.
• The meta tag checker reads the robots tag along with the title, description and H1, and the SEO Optimizer checks robots directives across up to 25 crawled pages, which shows quickly whether one page or a whole template is affected.

Step 3: Remove the noindex at the Source

• WordPress: under Settings, Reading, make sure "Discourage search engines from indexing this site" is unchecked. In SEO plugins such as Yoast or Rank Math, check the per-post advanced setting and the defaults for each post type and taxonomy.
• Shopify, Wix, Squarespace and Webflow: check the page's SEO settings for a "hide from search engines" option, and the site-wide setting that hides the whole site before launch.
• Next.js and other frameworks: look for robots: { index: false } in metadata, a default layout that sets noindex for every route, or an environment check that treats production like staging.
• Server and CDN: look for an X-Robots-Tag header added in nginx, Apache, Vercel, Netlify or Cloudflare rules. These are easy to miss because they are not in the HTML.

The most common cause of a site-wide excluded by noindex tag problem is a staging setting that went live with the launch. Make the noindex depend on the environment, so production never inherits it.

Step 4: Check robots.txt Is Not Blocking the Page

Google has to crawl a page to see that the noindex is gone. If robots.txt blocks the URL, Google cannot recrawl it and the old status can stick. Test the URL with the robots.txt tester. The reverse matters too: to keep a page out of the index, use noindex and let it be crawled. Blocking it in robots.txt does not remove it. The robots.txt guide explains the difference.

Step 5: Request Indexing and Validate

Inspect a fixed URL in Search Console, click Test live URL to confirm "Indexing allowed? Yes", then Request indexing. For many URLs, click Validate fix on the report row. Make sure the pages are linked internally and listed in your sitemap so Google comes back soon.

Related Indexing Statuses

If the page is crawlable and has no noindex but still is not indexed, look at "Crawled, currently not indexed" and "Discovered, currently not indexed". Both are about Google's choice, not your instructions. A full technical SEO audit covers all of these checks in one pass.