What does 'Excluded by noindex tag' mean in Google Search Console?

This status means Googlebot crawled your page but found a 'noindex' directive (either in the HTML meta tag or HTTP header). Consequently, Google obeyed your request and removed the page from its search index. It is not always an error; sometimes it is intentional.

How do I find the noindex tag on my website?

You can view the page source (Right-click > View Page Source) and search for 'noindex'. Alternatively, use the Digispot AI Chrome Extension to instantly detect noindex tags in the HTML head or X-Robots-Tag HTTP headers.

Should I remove the noindex tag from every page?

No. You should only remove the tag from pages you want to rank in search results (like blog posts, product pages, and service pages). Keep the tag on admin pages, cart pages, thank-you pages, and low-value utility content.

Why does my page still say 'Excluded' after I removed the tag?

Google needs to recrawl the page to see the changes. After removing the tag, go to Google Search Console, inspect the URL, and click 'Request Indexing'. It may take anywhere from a few hours to a few weeks for the status to update.

Can a plugin cause the noindex tag error?

Yes, SEO plugins like Yoast, RankMath, or All in One SEO often have settings that accidentally apply 'noindex' to entire content types (like tags or media) or specific pages. Check the 'Advanced' section of your SEO plugin on the affected page.

What is the difference between blocked by robots.txt and excluded by noindex?

Robots.txt prevents Google from *crawling* (visiting) the page. The 'noindex' tag allows Google to visit but tells them not to *index* (save) the page. You cannot use both; if a page is blocked by robots.txt, Google cannot see the noindex tag.

How do I fix 'Excluded by noindex tag' in WordPress?

First, check Settings > Reading to ensure 'Discourage search engines' is unchecked. If that's clear, check your specific page settings in the editor sidebar or your SEO plugin's meta settings to ensure the page is set to 'index'.

Is X-Robots-Tag different from a meta noindex tag?

Yes. The meta tag appears in the HTML code ` `, while the X-Robots-Tag is sent in the server's HTTP response header. Both function identically for SEO, but the header version is harder to spot without technical tools.

Excluded by Noindex Tag: Troubleshooting Guide & Fixes (2026)

Opening your Google Search Console (GSC) Page Indexing report and seeing a spike in grey bars labeled "Excluded" can trigger immediate anxiety. Among the various statuses, "Excluded by 'noindex' tag" is one of the most common—and misunderstood—signals Google sends to webmasters.

Often, this status is exactly what you want. It means your directives to keep admin pages, shopping carts, and internal search results out of Google's index are working.

However, when this status appears on your high-value landing pages, blog posts, or product categories, it is a critical SEO emergency. A "noindexed" page is invisible to searchers. It drives zero organic traffic. It generates zero revenue from search.

In this guide, we will break down exactly how to diagnose the source of the noindex tag, how to determine if it’s intentional or accidental, and the specific steps to fix it across different platforms.

What "Excluded by 'noindex' tag" Actually Means

When Googlebot visits a URL, it looks for instructions on how to handle the content. If it encounters a directive telling it not to add the page to the search results, it reports this status.

This instruction comes in two primary forms:

HTML Meta Tag: A line of code in the <head> section of your website.
HTTP Header (X-Robots-Tag): A server-side response sent before the page content even loads.

When you see this status in GSC, it confirms two things:

Google can access the page (it is not blocked by robots.txt).
Google respected your instruction to drop the page from the index.

The "Noindex" vs. "Blocked by Robots.txt" Conflict

A common misconception is that you should block unwanted pages in robots.txt and add a noindex tag. This is incorrect.

If you block a page in robots.txt, Googlebot cannot visit the page to read the "noindex" tag. The page might still appear in search results (usually without a description) because Google knows it exists from external links. To properly exclude a page, you must allow crawling so Google can read the "noindex" directive.

Diagnosing the Source: Where is the Tag Hiding?

Before you can fix the issue, you must locate the directive. This is often where troubleshooting fails, as the tag isn't always visible in the source code.

1. The HTML Meta Tag (Most Common)

This is the standard implementation. You can verify this manually or with tools.

Manual Check:

Open the affected URL.
Right-click and select View Page Source (or Ctrl+U).
Search (Ctrl+F) for "noindex".

You are looking for code that looks like this:

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

Or potentially:

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

Automated Check: Searching source code manually for hundreds of pages is inefficient. You can get instant SEO insights on any page, including hidden indexation tags, with our free Chrome extension. It flags indexability issues immediately upon page load.

Digispot AI Chrome Extension displaying meta tags, indexability status, and head section SEO signals

2. The X-Robots-Tag HTTP Header (The Stealth Killer)

If you view the source code and cannot find a <meta> tag, but GSC still reports "Excluded by noindex," the culprit is likely the HTTP header.

This directive is set at the server level (Apache, Nginx) or via backend code (PHP, Python) and is invisible in the HTML.

How to check: You need to inspect the server response headers.

Open Chrome DevTools (F12).
Go to the Network tab.
Refresh the page.
Click the first resource (the document).
Look under Response Headers for x-robots-tag: noindex.

3. JavaScript Injection

Modern websites rely heavily on JavaScript. Sometimes, the raw HTML source looks clean, but a JavaScript framework (like React or Angular) or a rogue Google Tag Manager script injects a noindex tag after the page renders.

To diagnose this, use the URL Inspection Tool in GSC:

Inspect the URL.
Click Test Live URL.
View Tested Page > HTML.
Search for "noindex" in this rendered code.

Step-by-Step Troubleshooting & Fixes

Once you have identified that a page is wrongly excluded, follow these steps to remove the tag.

Scenario A: The "Whole Site" Accident

If your traffic has flatlined and nearly all pages are showing as excluded, you likely have a global setting enabled.

WordPress:

Go to Settings > Reading.
Look for "Search Engine Visibility".
Uncheck "Discourage search engines from indexing this site".
Save changes.

Shopify:

Go to Online Store > Preferences.
Ensure "Limit access to your store with a password" is unchecked (unless you are still in development). Password-protected stores are automatically noindexed.

Scenario B: Plugin Misconfiguration

SEO plugins are powerful, but one wrong click can de-index a whole section of your site.

Yoast SEO:

Go to the page edit screen.
Scroll down to the Yoast meta box.
Expand the Advanced section.
Ensure "Allow search engines to show this Post in search results?" is set to Yes.

RankMath:

Open the page editor.
Click the RankMath icon in the top right.
Go to the Advanced tab (briefcase icon).
Ensure the Index checkbox is selected, not No Index.

Scenario C: Developer/Server Headers

If the issue is an X-Robots-Tag and you are not technical, you may need developer assistance.

Apache (.htaccess): Look for lines like this and remove them for the affected pages:

Header set X-Robots-Tag "noindex"

Nginx (nginx.conf): Look for:

add_header X-Robots-Tag "noindex";

If you are managing complex server environments, regular audits are vital. Digispot AI can help you identify and fix these issues automatically with AI-powered audits analyzing 200+ ranking factors, including deep server header analysis.

When "Excluded by Noindex" is Actually Good

Not all "Excluded" statuses are errors. A healthy SEO audit checklist includes verifying that low-value pages are excluded. You should intentionally noindex:

Thank You Pages: These distort analytics and offer no value to searchers.
Internal Search Results: Prevents "search results in search results" spam.
Admin/Login Pages: Security and relevance.
Taxonomy Archives (sometimes): If you have tags with only one post, they create thin content issues.
Staging Sites: To prevent duplicate content issues before launch.

If you find pages in this report that should be there, no action is required. The status is simply Google confirming it is following your rules.

Validating the Fix

After removing the rogue tags, you cannot sit and wait. You must prompt Google to recognize the change.

Clear Caches: If you use caching plugins (WP Rocket, W3 Total Cache) or server-side caching (Varnish, Cloudflare), clear them. Googlebot might still be served the old cached version with the noindex tag.
Use URL Inspection: Enter the fixed URL in GSC and click "Test Live URL". Ensure the availability says "URL can be indexed".
Request Indexing: Click the "Request Indexing" button.
Validate in Bulk: If you fixed a template issue affecting thousands of pages:
- Go to the Pages report in GSC.
- Click on "Excluded by 'noindex' tag".
- Click "Validate Fix".

Google will now prioritize recrawling these URLs. This process is not instant; it can take days for the graph to reflect the recovery.

Advanced Edge Cases

The "Soft" Noindex via Canonicals

While not strictly a "noindex" tag, using a canonical tag that points to a different URL (rel="canonical") tells Google: "Don't index this page; index that one instead."

If you see pages excluded under "Alternate page with proper canonical tag," do not add a "noindex" tag to them. The canonical is sufficient. Mixing canonicals and noindex tags sends conflicting signals (one says "this page is equivalent to X," the other says "do not index this").

Crawl Budget Implications

For large e-commerce sites (10,000+ pages), relying on "noindex" to manage Crawl Budget is inefficient. Google still has to crawl the page to see the noindex tag.

If you have thousands of generated filter pages (e.g., /shop/?color=blue&size=small), using robots.txt disallow rules is often better for saving crawl budget than letting Google crawl them just to find a "noindex" tag.

Schema Markup and Noindex

If a page contains rich structured data but is marked as noindex, Google will ignore the schema. Don't waste time optimizing JSON-LD for pages you don't intend to index. Use the free Schema Markup Generator to ensure your indexed pages have valid, eligible structured data.

Prevention: Automated Monitoring

The most dangerous aspect of the "Excluded by noindex" error is that it is silent. Your site doesn't break; traffic simply evaporates.

Manual checking is impossible for growing sites. You need a system that alerts you when high-value pages drop out of the index.

Best Practices for Prevention:

Staging Environment Checks: Always scan your staging site for noindex tags before pushing to production. A common disaster occurs when developers copy the database from Staging (set to noindex) to Live.
Regular Audits: Schedule a monthly technical crawl.
Monitor GSC Emails: Google sends "Index Coverage" alerts. Do not ignore them.

Ready to improve your search visibility and automate this monitoring? Try Digispot AI for comprehensive website audits. Our platform tracks your indexation status in real-time, alerting you to "noindex" injections before they kill your organic traffic.

Conclusion: Start Improving Your Indexation Today

The "Excluded by noindex tag" status is a double-edged sword. It is a powerful tool for controlling your site's quality signals, but a single misconfiguration can cost you thousands in lost revenue.

Your Action Plan:

Identify if the exclusion is intentional (admin pages) or accidental (blog posts).
Use the Digispot Chrome Extension to instantly verify headers and meta tags.

Digispot AI Chrome Extension visualizing robots.txt, canonicals, and XML sitemap status for advanced troubleshooting

Turn invisible SEO data into clear visuals with our Free Chrome extension

Fix the root cause in your CMS settings, plugin configurations, or server headers.
Validate the fix in Search Console immediately.

Don't let a simple tag hide your best content from the world. Master your indexation strategy, and you master your visibility.