How to Fix Noindex Tags in Your WordPress Sitemap

If Google reports Noindex page in sitemap or your sitemap URLs keep dropping out of the index, the most common cause is a X-Robots-Tag: noindex HTTP header being sent on the sitemap itself. Your sitemap is telling Google not to index your list of URLs. This page shows how to confirm the header, remove it safely, and keep the fix in place through plugin updates.

Quick answer

Check the header your sitemap actually serves: curl -A "Mozilla/5.0" -I https://yoursite.com/sitemap_index.xml. If you see X-Robots-Tag: noindex or a noindex meta on the sitemap page, that is the bug. Remove it by replacing the header with index, follow at the output-buffer level, not by editing the SEO plugin's files — plugin updates will overwrite file edits. Then resubmit the sitemap in Google Search Console.

Why it happens

SEO plugin defaults. Several SEO plugin versions have shipped sitemap output that includes a noindex header on sitemap files. It is often a legacy setting nobody remembers toggling.
Caching layers. A caching plugin or CDN can serve a stale cached copy of the sitemap with old headers for days after the underlying setting is corrected. Clear every cache layer before you conclude the fix failed.
Old hand-edited code. Snippets pasted into functions.php that add robots headers sitewide can catch the sitemap page too.
Plugin conflicts. Two plugins both filtering robots headers can produce a header stack where the last one wins, and it may be the wrong one.

The DIY fix, step by step

Confirm the served header with curl using a browser user agent (default curl UAs are often blocked on shared hosting).
Check your SEO plugin's sitemap settings for a noindex option and turn it off.
Clear plugin cache, server cache and CDN cache for the sitemap URLs.
Curl again. If still noindex, add a small mu-plugin that registers an output-buffer handler, strips the X-Robots-Tag header at flush and re-sets index, follow. A mu-plugins file survives plugin updates.
Resubmit sitemap_index.xml in Google Search Console and wait for the next crawl.

The Brambyl route

Brambyl's sitemap header check fetches the served header (not the file) and flags noindex as a critical finding. The repair strips the noindex header via the output-buffer method above, records scoped rollback SQL, and survives SEO plugin auto-updates because it does not edit plugin files. The companion sitemap coverage check then compares the sitemap's URL count against your published-post count so you can see whether Google's view of your site changed.

FAQ

Does clearing the sitemap cache alone fix it?

If plugin settings still emit the header, no. Cache clearing is step three; the settings fix and the persistent header fix are what keep it gone.

Do noindexed sitemap entries get deindexed?

The sitemap file itself is a document, but the signal it sends can suppress crawling of the URLs it lists. Fix the header, resubmit, and let Google re-crawl.

Does this work with Rank Math and Yoast?

Yes. Both have shipped sitemap noindex behaviour in some versions. The header-level check is engine-agnostic: it reads what your server actually serves.

Which SEO plugin should I use?

Both Yoast and Rank Math are solid on-page plugins; as of today they read Search Console signals rather than repairing them. Brambyl runs alongside either and repairs what they surface. Compare specifics in Brambyl vs Yoast and Brambyl vs Rank Math.