How do you fix “Submitted URL marked noindex” in Search Console?

What the error means

The URL appears in a sitemap, but Google found a noindex directive on the page, usually a meta robots tag or an X-Robots-Tag response header. A sitemap asks Google to consider URLs for crawling; it does not override a noindex instruction.

Why Google rejects it

This often happens when a page was intentionally excluded and later added to the sitemap, a staging setting or SEO plugin left noindex enabled, or a template applies the directive to an entire page type. If the page should stay out of Search, the sitemap entry is the conflicting signal.

How to fix it

1. Decide whether the page should be indexed. If not, keep noindex and remove the URL from the sitemap; do not ask Google to index a page you intend to exclude.
2. If it should be indexed, inspect the rendered HTML for a robots meta tag and check the HTTP response headers for X-Robots-Tag. Remove the unintended noindex at its source.
3. Check the page’s template and SEO settings, not just the individual URL. A shared setting can affect every product, collection, category, or post of that type.
4. Confirm the URL returns a successful response, is not blocked from crawling in robots.txt, and has a sensible canonical. Google must be able to crawl the page to see that noindex is gone.
5. Refresh or regenerate the sitemap so it contains only canonical, indexable URLs. Test with URL Inspection, then request indexing for the important page.

Common causes

The sitemap includes pages intentionally excluded from search

A page may correctly carry noindex while a sitemap generator still lists every published URL. The two signals conflict: the sitemap presents the URL as a discovery candidate, while the page tells Google not to index it. Decide the intended status first, then align both sources.

A template applies noindex to an entire content type

A theme, SEO plugin, or platform setting can emit noindex on every product, collection, tag, or archive page. A single URL inspection may be a clue to a broader template rule. Compare a working page of the same type and inspect the rendered robots meta tag and HTTP headers.

A staging or launch setting was carried to production

A site-wide search visibility setting can be useful while building a site and harmful after launch. Check whether the directive appears across unrelated pages and whether it was introduced during migration, a theme change, or plugin configuration.

A response header adds noindex outside the HTML

The page source can look clean while the server returns an X-Robots-Tag: noindex header. This is common when server rules target a path or file type. Inspect the HTTP response headers as well as the HTML; removing a meta tag alone will not clear a header instruction.

The sitemap or SEO plugin has stale indexability data

A page may have become indexable but an old sitemap or cache still includes incorrect data, or the reverse: a noindex setting was removed but a cached response still serves it. Compare live output, the sitemap, and the settings in the source plugin before requesting another crawl.

Fix it on your platform

On Shopify

1. Inspect the page's public source for <meta name="robots" content="noindex"> and check whether the noindex came from theme Liquid, an SEO app, or a product visibility setting.
2. Shopify's searchability settings distinguish publishing from search visibility. Confirm the product is published to Online Store and is not intentionally hidden or unlisted; inspect the current platform setting before changing theme code.
3. If the page should be indexed, remove the unintended rule at its source and check that the sitemap no longer conflicts with the resulting indexability state.
4. Do not block the page in robots.txt while trying to remove noindex: Google must be able to crawl the URL to see the updated directive.

On WooCommerce

1. Inspect the SEO plugin's page-level robots settings and global settings for the affected post type, taxonomy, or archive.
2. Check the actual response headers for X-Robots-Tag in addition to the rendered meta robots tag; server configuration can add a directive independently of the plugin.
3. If the URL should be indexed, remove noindex in the setting that emits it, clear page/CDN cache, and regenerate the SEO plugin sitemap if needed.
4. If the page should stay noindex, leave the directive and exclude it from the XML sitemap rather than turning off the intended restriction.

On other platforms

1. Wix: check the page's SEO settings for an indexing toggle and confirm the published page output reflects the intended choice.
2. Squarespace or BigCommerce: inspect page-level SEO visibility and any site-wide or collection-level noindex setting, then compare the live tag with the sitemap entry.
3. For custom hosting, inspect both HTML and HTTP headers; remove an unintended X-Robots-Tag at the server or CDN rule that adds it.
4. On any platform, allow crawling while Google needs to discover a changed noindex directive; a robots.txt block can prevent that discovery.

How to confirm it is fixed

1. Fetch the live HTML and response headers for the URL; confirm the unintended noindex is gone from both the meta tag and X-Robots-Tag header.
2. Check robots.txt permits crawling and the canonical points to the URL you intend to index. A blocked URL prevents Google from seeing updated page directives.
3. Run the index signals check to compare public sitemap, noindex, canonical, status, and robots signals.
4. Use Search Console URL Inspection's live test, then request indexing for an important corrected URL. Update or regenerate the sitemap so it contains only URLs intended to be indexable.

A worked example

Hypothetical case: a home decor store marks discontinued products noindex so they stop appearing in Search, but the SEO plugin's sitemap still lists those product URLs. Later, a new product template inherits the same noindex setting, so current products show Submitted URL marked noindex in Search Console. The owner compares a current product with a discontinued one and finds the robots meta tag on both. They correct the product-template setting, retain noindex for the retired products, and update the sitemap rules to exclude those intentionally hidden URLs. A live URL Inspection test can now crawl the current product and reports indexing allowed, while the retired pages remain excluded by design.

Other errors like this