The sitemap could not be read Google Search Console message usually sits next to a “Couldn’t fetch” status in the Sitemaps report, and it is one of the least informative errors the tool produces. It does not say what went wrong. Sometimes nothing has gone wrong at all. The sensible approach is a short checklist of genuine faults, a resubmit, and some patience, because a sitemap is a helpful hint rather than the route by which your pages get indexed.
What the sitemap could not be read Google Search Console message means
Rank Math’s knowledge base article on the Couldn’t fetch error explains that the status means one of two things: either Google is yet to fetch your sitemap, or Google cannot access it because of an error. The report does not tell you which. That is the core problem, and it is why the fix is a process of elimination rather than a single setting.
The received wisdom treats the message as proof that something is broken. Often it is only proof that Google has not got round to the file yet, particularly on a new site or a newly submitted sitemap. The checks below are worth doing anyway, because if there is a real fault you want to find it, but expect that some of the time you will find nothing.
The checklist, in order
These are the checks Rank Math recommends, plus one general check for firewalls. Work through them roughly in this order; the first few are quick, and the last is simply waiting.
| Check | What you are ruling out | How |
|---|---|---|
| Open the sitemap URL yourself | A missing or broken file | Load it in a browser and confirm it returns XML |
| Validate the XML | Malformed markup | Run the file through an XML sitemap validator |
| Check the location | A sitemap outside the site root | Make sure it sits at the root of the property |
| Check posts are indexable | An empty sitemap | Confirm your posts are not all set to noindex |
| Flush the sitemap cache | A stale or broken cached copy | Clear the SEO plugin’s sitemap cache |
| Exclude from page caching | A caching plugin serving the wrong response | Add the sitemap URLs to the cache exclusions |
| Check firewalls and CDN rules | Googlebot being blocked | Review security and bot rules for blocks on the sitemap |
| Check the property URL | An http/https or www mismatch | Submit under the verified variation that matches the sitemap |
| Rename or resubmit | A stuck fetch | Submit again, try a new file name or a leading slash |
| Wait | Simple delay | Give Google time; it can find pages without the sitemap |
Rule out a broken or empty file
Start by opening the sitemap URL in a browser. If it returns a 404, a login page or an error, there is nothing for Google to read and the message is accurate. If it loads, run it through an XML validator. A stray character, a plugin printing output before the XML declaration or a broken tag can make the file unreadable to a parser while it still looks fine on screen.
Next, confirm the sitemap actually contains URLs. If every post is set to noindex, a well-behaved SEO plugin will leave it out, and you can end up with an empty sitemap. Check for a site-wide noindex setting left on from development. Our guide to XML sitemaps for SEO covers what should and should not be listed.
Location matters too. Rank Math advises keeping the sitemap at the site root, where it can describe the whole site. If yours lives elsewhere, check it is still on the same host as the property you submit it to.
Rule out caching and blocking
Caching is a common culprit on WordPress sites. If a page-caching plugin stores an old or broken copy of the sitemap, Google may keep receiving it long after you have fixed the file. Flush the sitemap cache in your SEO plugin, then add the sitemap URLs to your caching plugin’s exclusion list so they are always generated fresh.
Then check that nothing is stopping Googlebot reaching the file. Security plugins, server firewalls and CDN bot rules can challenge or block crawlers, and a sitemap behind a challenge page is unreadable. Look for rules that block unfamiliar user agents or particular paths. It is also worth confirming that your robots.txt does not disallow the sitemap’s location.
Check the property, then resubmit
A sitemap at https://www.example.com/sitemap_index.xml should be submitted to the property that matches that exact variation. If you verified http://example.com and the sitemap lives on the https www version, you are asking the wrong property to read it. Our guide on how to use Google Search Console explains the difference between property types.
Once the faults are ruled out, resubmit. Rank Math suggests two small tricks that sometimes clear a stuck status. One is to change the file name, citing John Mueller: “changing the name of the sitemap file can do the magic”. The other is to resubmit the same path with a leading slash, for example:
Neither changes anything about the file itself. Both give Search Console a fresh request to process, which is sometimes all that was needed.
Why waiting is a legitimate fix
The last step in Rank Math’s list is to wait, and it is not a cop-out. As the article puts it, “Google can find and fetch your URLs without a sitemap”. Internal links, external links and Google’s own crawling all lead to your pages. A sitemap helps, especially on large or new sites, but a site with good internal linking does not depend on it.
That changes the stakes. If you have opened the file, validated it, confirmed it lists indexable URLs, cleared caches, checked firewalls and submitted it to the right property, you have done what can be done. Check the Pages report for whether your URLs are being indexed. If they are, the sitemap status is cosmetic. If they are not, the cause is probably elsewhere, and our guide on how to get indexed by Google is the better place to look.
The limitation is the one the report itself imposes. Search Console does not distinguish between “not fetched yet” and “could not fetch”, so after every check passes you still cannot prove which applied. Treat a clean checklist as your answer, keep an eye on indexing rather than on the sitemap row, and resist the urge to resubmit daily. Repeated submissions do not make Google fetch faster.
Frequently asked questions
Does sitemap could not be read stop my pages being indexed?
Not on its own. Google can find and fetch your URLs without a sitemap through links. Check the Pages report to see whether your URLs are being indexed.
Why does the error appear on a brand new sitemap?
Often because Google has not fetched it yet. The status covers both a pending fetch and a real error, so a new sitemap can show it before anything has gone wrong.
Does renaming the sitemap really help?
Sometimes. Rank Math cites John Mueller saying that changing the file name “can do the magic”. It gives Search Console a fresh URL to process.
Can a caching plugin cause the error?
Yes. A cached copy of the sitemap can be stale or broken. Flush the sitemap cache and exclude the sitemap URLs from page caching.
The takeaway Check the file loads, validates and lists indexable URLs; clear caches, check firewalls and the property; then resubmit once and wait. Judge success by indexing, not by the sitemap status.
