Noindex URL in XML Sitemaps: How to Fix the Conflict

TL;DR: A URL that sits in your XML sitemap while also carrying a noindex directive sends Google two opposite signals. Google honors the noindex and drops the page, but wastes crawl budget and logs a coverage error first. Fix it by removing the URL from the sitemap (if it should stay noindexed) or removing the noindex (if it should be indexed).

What a noindex URL in your XML sitemap means

Your XML sitemap is a list of URLs you're telling Google "these are worth indexing, please crawl them" — so when one of those URLs also carries a noindex directive, you're shouting two contradictory instructions at the same crawler. The page says "keep me out of the index"; the sitemap says "put me in it."

Google resolves the conflict by honoring the noindex and dropping the URL — but not before wasting crawl budget re-checking a page you never wanted indexed, and Search Console logs it as a coverage error ("Submitted URL marked noindex"). At scale that's thousands of wasted crawls and a noisy report that hides the errors you actually care about.

A real example and the fix

Here's the contradiction. The sitemap includes the URL:

<url>
  <loc>https://example.com/tag/summer-sale/</loc>
  <lastmod>2026-06-30</lastmod>
</url>

...but that same page returns a noindex directive:

$ curl -sI -A 'Mozilla/5.0' https://example.com/tag/summer-sale/ | grep -i x-robots-tag
x-robots-tag: noindex, follow

# or in the HTML head:
<meta name="robots" content="noindex, follow">

The fix is to pick one signal and make it consistent. Decide whether the page belongs in the index, then align both:

• If it should NOT be indexed (the usual case for tag/filter pages): keep the noindex and remove the URL from the sitemap. The sitemap should only ever list canonical, indexable URLs.
• If it SHOULD be indexed: remove the noindex directive and leave it in the sitemap.

Which fix applies to your page type

How to detect it

1. Screaming Frog crawl: crawl in List mode against your sitemap URL, then use Reports > Sitemaps > Non-Indexable URLs in Sitemap. It hands you the exact list.
2. Google Search Console: the Pages report surfaces "Submitted URL marked 'noindex'" — that error is this issue by definition.
3. curl a suspect URL: curl -sI -A 'Mozilla/5.0' https://yourdomain.com/suspect-page/ | grep -i x-robots-tag and view-source for a <meta name="robots"> tag in the head.
4. Diff the two lists: export every <loc> from your sitemap and every noindexed URL from a full crawl; the overlap is your problem set.

How to fix it

Trace the source, because sitemaps are almost always auto-generated.

• Yoast / Rank Math (WordPress): these plugins normally exclude noindexed URLs automatically. If a noindexed page still appears, the noindex was likely added manually or by a second plugin after the sitemap cached — clear the sitemap cache and re-check.
• Custom / CMS sitemaps: add a build-time filter so any URL flagged noindex is excluded from the <urlset> before the file is written.
• Confirm the intent first: don't reflexively strip the noindex. A tag page that's noindexed on purpose should leave the sitemap, not get force-indexed.
• Resubmit: once the sitemap only lists indexable URLs, resubmit it in Search Console and the coverage errors clear on the next crawl.

Don't reach for robots.txt to fix this

A tempting-but-wrong move is to Disallow the noindexed URL in robots.txt so Google "stops bothering with it." That backfires: if Google can't crawl the page, it can't read the noindex, and the URL can linger in the index as an untitled "blocked" result — fed, ironically, by the sitemap entry still advertising it. The correct combo is: leave the page crawlable, keep the noindex so Google reads and obeys it, and remove the URL from the sitemap. Robots.txt controls crawling; noindex controls indexing. They are not interchangeable, and stacking them here creates a worse mess than the one you started with.

Common mistakes

• Force-indexing a page that should stay out. The flag isn't always telling you to remove the noindex — more often it's telling you to remove the sitemap entry.
• Fixing one URL by hand on a templated site. If tag pages are noindexed, all of them are wrong in the sitemap — fix the generator, not the single URL.
• Not clearing the sitemap cache. Plugins cache the XML; your fix won't show until the cache regenerates and you resubmit.

FAQ

Will this hurt my rankings?

Not directly — the noindexed page was never going to rank anyway. The cost is wasted crawl budget and a cluttered coverage report that can mask genuine indexing problems on pages you do care about.

Does noindex, follow vs noindex, nofollow change anything here?

For the sitemap conflict, no — either way the URL shouldn't be in the sitemap. The follow/nofollow part only affects link equity flow. See noindex and nofollow together.

Google is ignoring my noindex — is the sitemap why?

Possibly. If the page is blocked in robots.txt, Google can't crawl it to see the noindex, so it may stay indexed from the sitemap signal alone. Unblock it in robots.txt so the noindex is actually read.

Should tag and category pages ever be in the sitemap?

Only if you've deliberately made them indexable and useful. Most sites noindex thin taxonomy pages — in which case they belong nowhere near the sitemap.

Where can I learn how sitemaps should be built?

Our XML Sitemaps complete reference covers the rules, and the noindex glossary entry explains how the directive is read.