Fix the 'Submitted URL Marked 'noindex'' Issue in Search Console in 2026

This page is for SEO managers, marketers and business leaders whose pages are excluded from Google by a no-indexing directive. It covers noindex in Google Search Console: the status long shown as "Submitted URL marked 'noindex'" now appears under the "Excluded by 'noindex' tag" label in the Pages report.

You will learn where to find the directive, how to decide whether to remove or keep it, and how to verify the fix. The other reports are covered in our complete guide to Google Search Console.

Noindex in Google Search Console: Understand, Diagnose and Fix It Without Losing Visibility

Why Search Console Shows "Excluded by 'noindex' tag"

This status appears when Googlebot crawls a URL that carries a no-indexing instruction, either in the HTML or in the HTTP header. The page is crawled, then excluded from the index: it no longer receives any organic traffic.

A URL listed in the sitemap and marked noindex reveals a mismatch: you are pushing the page towards the index while asking Google to exclude it. The sitemap should only list indexable URLs, as our guide to sitemaps in Search Console explains.

What Search Console Can (and Cannot) Do With a noindex Directive

Google Search Console (GSC) is built to detect and verify, not to fix. Its tools cover three needs:

• Spot the affected URLs: the Pages report groups them under a single status.
• Confirm the cause: the URL Inspection tool shows whether a noindex was detected and the crawl date.
• Monitor at scale: the URL Inspection API reads the status of many URLs, but it does not request indexing (at the time of writing).

The fix itself happens in the code, the CMS or the server configuration.

Where the noindex Directive Comes From (and How to Confirm It)

A noindex can come from three places, and each is read differently. The following table shows where to look and who acts:

In the HTML: Meta Robots Tag, CMS and Templates

The directive sits in the HTML head: <meta name="robots" content="noindex">. It comes from a CMS setting, a template applied to certain page types (tag archives, author pages) or a staging environment deployed by mistake. Check the rendered version of the page and confirm with the URL Inspection tool.

Noindex is also applied deliberately to some templates (pagination, filters, internal search, baskets); a poorly placed rule then affects strategic pages. A sudden spike in "Excluded by 'noindex' tag" URLs almost always signals a template error.

In the HTTP Header: X-Robots-Tag at Server Level

Noindex can also be sent via the HTTP response header (X-Robots-Tag: noindex), especially for non-HTML resources. Invisible in the HTML, it shows up in the response headers or the URL Inspection tool. Setting it is a matter of server or CDN configuration, and therefore of hosting.

noindex vs robots.txt vs Canonicals vs Removal

These four mechanisms do not act at the same stage. The following table compares them:

The key point concerns robots.txt: if the URL is blocked from crawling, Googlebot never sees the noindex directive. To deindex with noindex, keep the URL crawlable until GSC confirms the exclusion. Diagnosing a crawl block is covered in our guide to the robots.txt report in Search Console.

Mixing canonical signals and noindex across related pages creates contradictory instructions: the URL you want to rank should remain indexable and consistent.

Removing a noindex Tag Without Unintended SEO Side Effects

Pre-change Checklist

Removing a noindex can bloat your index or expose a weak page. Before acting, answer these questions:

• does the page have real value for Google Search?
• does it serve a clear business objective?
• does it attract internal or external links?
• could it compete with a similar page that is already indexed?

Remove noindex at the Source, Then Check in Search Console

Delete the directive where it is emitted (code, CMS, template, server), deploy, then make sure no global rule reapplies it elsewhere. The checks follow this order:

• Live test: in the URL Inspection tool, check that Googlebot no longer detects a noindex.
• Indexing request: keep it for strategic pages; it sometimes speeds up processing, with no guarantee.
• "Validate fix": launch it in the Pages report once every URL of the same template is fixed.
• Monitoring: check the URL status, then the return of impressions.

Indexing requests and the Pages report are covered in our guide to indexing in Google Search Console.

How to Deindex a Page Effectively Using Search Console

The Removals tool hides a URL from search results for about 6 months (at the time of writing), but its effect is temporary. Lasting exclusion requires action on the page itself: methods and timelines are detailed in our guide to removing a URL from Google's results.

A Simple Decision Tree Based on Your Goal

The right tool depends on your goal, and each choice produces its own status in the Pages report:

Noindex does not provide any confidentiality: the page remains accessible to anyone who has the address. Do not combine it with robots.txt blocking either, as this would make the directive invisible to Google.

Advanced Troubleshooting: When a Page Stays Excluded or Reappears in the Index

Google Still Sees noindex: Key Checks

If GSC still reports a noindex after your fix, the directive survives somewhere. Check in this order:

• no conflicting directive between the HTML and the HTTP header;
• consistent URL variants (parameters, trailing slashes, uppercase);
• what Googlebot actually renders;
• the last crawl date, and whether it predates your fix.

Conflicting Signals: Sitemaps, Internal Links, Canonicals and Redirects

A page deliberately set to noindex must be treated consistently across the whole site:

• remove noindexed pages from the sitemap;
• take them out of important internal linking;
• do not point canonicals or redirects at a non-indexable URL;
• fix the source of the signal (template, rule) rather than a single URL.

Removing a noindex only takes effect at Googlebot's next crawl.

Best Practice: Using noindex Methodically Within an SEO/GEO Strategy

Pages to Exclude First, Pages to Protect

Noindex suits pages that are useful to visitors but have no value in search results:

• internal search pages and low-value faceted URLs;
• utility pages (basket, account, confirmation);
• temporary variants and test pages.

The goal is not to have zero exclusions, but intended ones. Conversely, these pages should not be excluded without careful thought:

• high-potential categories;
• evergreen content, a long-term traffic driver;
• pages attracting inbound links.

A noindex on these pages often hides a content or structural problem. On the GEO side, a page excluded from the index appears neither in AI Overviews nor in AI Mode, as our guide to Generative Engine Optimization explains.

Document Rules and Prevent Regressions

Template errors are the leading source of accidental noindex. Three habits keep them in check:

• maintain the list of page types to exclude and those to protect;
• review robots directives before each release;
• monitor the "Excluded by 'noindex' tag" status in the Pages report every week.

Measuring Impact: Linking Indexation, Performance and ROI

Cross the Pages and Performance reports on the affected URLs, then measure the effect on traffic and conversions in Google Analytics 4: you will know whether the noindex is strategic or accidental. Four indicators guide the decision:

• "Excluded by 'noindex' tag" status: its trend by template reveals deployment errors.
• Impressions and clicks: a drop on strategic URLs points to an accidental noindex.
• CTR: after reindexing, improve it through the title and meta description.
• Cannibalisation: a reindexed page can take visibility from a page with a similar intent.

Compare before and after over equivalent periods before drawing conclusions.

Depending on Your Situation

Depending on what your diagnosis reveals, continue with the relevant article:

• The page is excluded without any noindex. Check that Googlebot can reach it with our guide to crawl monitoring in GSC.
• The page no longer exists. Choose between redirect, 404 and 410 with the guide to 404 errors in Search Console.
• You are reviewing the indexing policy of the whole site. Define what should enter the index with the guide to website indexing.
• You are preparing a full audit. Place noindex among the other checks with our technical SEO audit method.

To spot the templates that spread a noindex by mistake and rank fixes by page value, rely on the Incremys 360° SEO and GEO audit.

FAQ: noindex and Google Search Console

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

This status means Google crawled the page, detected a noindex directive and excluded the page from the index. This Pages report label replaces the former "Submitted URL marked 'noindex'" label. If the exclusion is intended, there is nothing to fix; otherwise, remove the directive at its source.

How long does it take for a noindex page to leave the index?

A noindex page leaves the index at Googlebot's next crawl, when the directive is read. The delay depends on how often the page is crawled, from a few days to several weeks. In an emergency, the Removals tool hides the URL from search results in the meantime.

Can I combine noindex and robots.txt?

No, you should not block with robots.txt a page you want to deindex with noindex. The block prevents Googlebot from reading the directive, so the URL can stay in the index. Keep the page crawlable until GSC confirms the exclusion in the Pages report.

How do I remove a noindex tag?

You remove a noindex tag by deleting the directive where it is emitted: template, CMS setting or server configuration. Deploy, then run a live test in the URL Inspection tool. For a strategic page, then request indexing and follow "Validate fix" in the Pages report.

How do I deindex a page in Google Search Console?

Search Console hides a page from search results with the Removals tool, but only temporarily. Lasting exclusion happens on the page itself: noindex if it remains useful to visitors, 410 if it is gone, authentication if it is confidential.

Where is the noindex tag located?

The noindex directive sits either in the HTML code, as a meta robots tag, or in the HTTP header, via X-Robots-Tag. A template, a CMS setting or an environment rule can inject it. The URL Inspection tool, which shows what Googlebot received, locates it reliably.

Does noindex protect confidential content?

No, noindex only prevents the page from appearing in Google's search results; the page remains accessible to anyone who knows its address. For confidential content, authentication is the only real protection. It also removes the page from the index, since Googlebot can no longer access it.