Quick answer
A sitemap noindex conflict occurs when a URL appears in a sitemap but the crawled page sends a noindex directive. The sitemap suggests discovery for the URL while the page says it should not be indexed. Decide which signal matches the page's purpose, then remove the URL from the sitemap or remove noindex only when the page should be indexable.
What the issue means
XML sitemaps are lists of URLs that site owners want crawlers to discover. A noindex directive in a robots meta tag or X-Robots-Tag header asks search engines not to index the page. Keeping both signals can make the site's intended state harder to interpret and often indicates a stale sitemap, a shared template setting, or a page that changed purpose.
Why it matters for SEO
Search systems may discover a URL from a sitemap even when it should not be indexed. An accurate sitemap helps focus crawling on preferred, public URLs, while an intentional noindex keeps utility, duplicate, or private content out of search. Aligning the two signals improves consistency; it does not force indexing or guarantee rankings.
How NOTABIS detects it
After crawling, NOTABIS compares the unique page URLs collected from sitemap sources with each measured page's noindex measurement. That measurement is true when the robots meta value or X-Robots-Tag contains noindex. When both conditions are present, the page receives the high-severity sitemap-noindex-conflict finding.
The check only covers URLs and directives that this audit measured. It does not decide whether the page should be indexable, validate every sitemap entry, or inspect search-engine indexing outcomes.
How to check it yourself
- Open the sitemap or sitemap index and locate the affected URL.
- Request the URL and inspect the HTML robots meta tag and
X-Robots-Tagheader. - Confirm the canonical, response status, authentication, and page purpose.
- Check whether a template, CMS rule, or query variant added
noindexunexpectedly. - Reconcile the sitemap after choosing the intended state and test the final URL.
How to fix it
For an important public page, remove the unintended noindex, return a successful response, and keep the canonical and sitemap entry aligned. For a utility, duplicate, private, or retired URL, keep noindex when it is appropriate and remove the URL from the sitemap. Update internal links and regenerate sitemap indexes, then re-run the audit.
Do not remove noindex merely to clear a report if the page should remain out of search.
When this is intentional or does not need fixing
The conflict can be deliberate during a migration or while a page is being tested, but temporary exceptions should have an owner and an expiry. A page that is intentionally non-indexable should normally be excluded from the sitemap so the two signals do not disagree.
Related issues
Read noindex directives, XML sitemaps, sitemap accessibility, and canonical and noindex. Google’s sitemap overview and noindex guidance explain the separate discovery and indexing controls. Duplicate URLs covers common variant cases.
Run a NOTABIS audit
Run a NOTABIS SEO audit to compare sitemap URLs with measured noindex directives and inspect the affected page evidence.