Sitemap and noindex on the same page: a contradictory signal

In brief

A page declared in the sitemap but carrying a noindex sends two opposite orders: Google obeys the noindex yet keeps re-crawling it, wasting budget and polluting your indexing reports. Pick one intent: remove it from the sitemap, or remove the noindex.

WarningP2 — CTR / SERP

What is it?

This page is declared in your sitemap.xml but carries a noindex directive (robots meta tag, googlebot meta tag or X-Robots-Tag HTTP header).

Why it hurts SEO and AI

The sitemap tells Google "this URL matters, index it" while the noindex says "ignore it". Google always sides with the noindex — the page will not be indexed — but it keeps re-crawling it since the sitemap presents it as important: crawl budget wasted on a page you exclude yourself. It is also one of the causes behind the Search Console "Excluded by noindex tag" report, which pollutes your indexing data with perfectly intentional exclusions. AI systems that read the sitemap as the site's inventory receive the same contradictory signal.

When it is NOT a problem

  • The page just switched to noindex and is not yet removed from the sitemap: the conflict clears as soon as you update the sitemap.
  • The noindex was just removed on purpose to index the page: it rightfully belongs in the sitemap, no conflict left.
  • It is a deliberate temporary noindex (page under rework) that you are tracking and will lift soon.
Before
<!-- sitemap.xml -->
<url><loc>https://site.com/page</loc></url>

<!-- /page in <head> -->
<meta name="robots" content="noindex">
After
<!-- Page to index: remove the noindex -->
<meta name="robots" content="index, follow">

<!-- OR page to exclude: drop it from the sitemap -->
<!-- (the URL no longer appears in sitemap.xml) -->

One single intent: either the page matters and stays indexable, or it is excluded and leaves the sitemap. Never both.

How to fix it

  1. Decide whether this page should rank in Google or stay out of the index.
  2. If it should rank: remove the noindex directive (robots/googlebot meta tag and X-Robots-Tag header).
  3. If it should stay excluded: keep the noindex and remove its URL from sitemap.xml.
  4. Re-crawl the page and check in Search Console that the "Excluded by noindex tag" conflict disappears.

This scan checks the HTTP status, noindex and canonical of every page

Is this issue on your site?

Is one of your pages both in the sitemap and set to noindex? Enter a URL: Seogard cross-checks your sitemap against each page's real indexing directives and alerts you the moment they contradict each other. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

The sitemap becomes a reliable statement of intent again: Google focuses its crawl on the pages you actually want indexed, and Search Console reports stop mixing intentional exclusions with accidents.

Seogard catches this regression automatically — through its monitoring for your metas and canonicals.

Frequently asked questions

Will Google index a noindex page if it is in the sitemap?

No. Facing a conflict, Google always honors the noindex: the page will not be indexed, but it keeps re-crawling it as long as the sitemap presents it.

Where do I check a page's noindex directive?

In the robots or googlebot meta tag in the HTML, and in the X-Robots-Tag HTTP header returned by the server: either one is enough to block indexing.

Related rules

Temporary redirect on removed pageA page removed from the sitemap redirects with a 302/307 (temporary). Google keeps the old URL indexed and is slower to consolidate signals toward the target. If the removal is permanent, a 301 (permanent) redirect passes link equity cleanly. Removal without 410 or 301A page removed from the sitemap returns a bare 404. It works, but the signal is ambiguous: Google keeps re-crawling it for weeks. Permanent deletion — return 410 (faster deindexing); moved content — 301 (preserves backlink equity). Meta description removedThe meta description is gone. Google generates an automatic snippet instead: possible impact on click-through rate, but no deindexing and no ranking loss.

Updated July 10, 2026