“Submitted URL marked ‘noindex’” means a URL listed for discovery also tells search engines not to index it. The key question is whether the page is intentionally excluded. If it should be searchable, remove the directive; if not, remove it from the sitemap and keep the exclusion intentional.

Find the source of the noindex directive
A noindex instruction can appear in a page’s robots meta tag or in an HTTP X-Robots-Tag response header. It can also be added by a CMS setting, SEO plugin, template, or deployment rule. Check the rendered page and response headers rather than relying only on what an editor screen shows.
Inspect the exact affected URL, including redirects and alternate versions. A sitemap can point to one URL while the final page or a template emits a directive from another layer.
- Use URL Inspection to check the indexed and live-page details.
- Review page-level visibility settings and SEO plugin controls.
- Check headers if the page is a PDF or a non-HTML response.
Choose the correct outcome
If the page should be indexed, remove the noindex directive from the canonical URL and confirm that robots.txt does not prevent crawling. Keep the URL in the sitemap only after it returns the intended page and has consistent canonical signals.
If the page should stay out of search—such as a private utility page, a duplicate, or a low-value internal result—leave noindex in place and remove that URL from the sitemap. A sitemap is intended to describe URLs you want considered for indexing, not every URL your system can generate.
- Indexable page: remove noindex, confirm crawl access, keep in sitemap.
- Excluded page: retain noindex, remove from sitemap, check internal links.
- Redirected page: list the final destination rather than the redirecting URL.
Validate the change safely
After correcting the source, inspect the live URL again and test a representative sample if the directive came from a shared template. Then submit the sitemap or request recrawling for important pages. Search engines decide whether to index a page; removing noindex only makes it eligible.
Avoid changing a site-wide setting until you know which template or page group it affects. A single accidental setting can exclude many otherwise useful URLs.
A frequent cause is a template-level setting inherited by many pages, especially staging, archive, filtered, or recently migrated content. If many URLs show the same status at once, inspect the shared template or deployment configuration before editing individual records.
How did this article land?
Choose one reaction. You can change it anytime.
