Google Search Console noindex
-
Hello,
I am experiencing an issue with the XML sitemaps generated by Yoast SEO on my website blisstver.ru.
Google Search Console refuses to process my sitemap and returns the error:
“Couldn’t fetch / Sitemap could not be processed.”
After checking the HTTP response, I discovered that the sitemap files generated by Yoast include the following header:
X-Robots-Tag: noindex, follow
Because of this header, Google does not accept the sitemap.
Here are the verified facts:
- When I deactivate Yoast SEO, the sitemap returns a 404 error — confirming that Yoast is generating the sitemap.
- All regular website pages return normal headers without noindex.
- Only the sitemap files created by Yoast SEO return:
X-Robots-Tag: noindex, follow
- My hosting provider (REG.ru) confirmed that the header is not added by the server (nginx), but specifically by the Yoast SEO plugin.They wrote:“The X-Robots-Tag: noindex header is generated by the WordPress SEO plugin, not by the Nginx server.”
The problem is that I cannot find any setting inside Yoast SEO that would enable or disable the noindex header for XML or sitemap files.Environment:
- WordPress
- Yoast SEO version 26.5
- Sitemap URL: https://blisstver.ru/sitemap_index.xml
- HTTP response for sitemap (via httpstatus.io):
HTTP/2 200
Content-Type: text/xml
X-Robots-Tag: noindex, followI kindly request your assistance with the following:
- Where exactly in Yoast SEO (in my version) is the setting located that controls the noindex header for XML/sitemap files?
- How can I disable Yoast SEO from adding X-Robots-Tag: noindex to sitemap files?
- Is it possible that this noindex header is added automatically if some content types or sections in Yoast are set to “Do not show in search results”?If so, please specify where I should check this.
I need the sitemap to be indexable (or at least not include a noindex header), otherwise Google Search Console cannot process it.
Thank you in advance for your help!
The page I need help with: [log in to see the link]
You must be logged in to reply to this topic.