Ranking Fixer Sitemap Could Not Be Read (Couldn't Fetch): How to Fix It
"Sitemap could not be read" means Google tried to fetch your sitemap and did not get a usable file, so the status shows "Couldn't fetch". Google's documented causes are a robots.txt block, a manual action, a wrong URL, server errors and low crawl demand. Test the sitemap URL live before changing anything.
The error alone does not keep pages out of Google, but it slows down how fast new pages are found. When it comes with pages that are not indexed, indexing fixes look at both together.
What the sitemap statuses in Search Console mean
| Status | What Google says | What happens to the URLs |
|---|---|---|
| Success | The sitemap was loaded and processed with no errors | All URLs are queued for crawling |
| Has errors | The sitemap was fetched but has one or more errors | URLs that could be parsed are still queued |
| Couldn't fetch | The sitemap could not be fetched for some reason | Nothing from this file is read until a fetch works |
Is it a real problem?
- Test the sitemap URL in URL Inspection. If Test live URL fetches it successfully, Google can reach the file, and the cause is more likely the file itself or low crawl demand.
- Check whether pages are indexed anyway. On a small site that Google crawls through links, a sitemap error costs little while you fix it.
- Look at the site's age. Google names low crawl demand as one of the causes, and a new site with little content and few links is where that happens. Better content and links raise demand.
Why Google cannot read a sitemap
Blocked by robots.txt
Google follows robots.txt when it fetches the sitemap. A rule that blocks the folder or the file blocks the fetch.
Wrong address
The submitted URL returns 404, redirects, or points to a file a plugin or platform change moved somewhere else.
Server or firewall
Server errors, timeouts or bot protection that answers Google with a challenge page instead of the file.
Not XML at all
A login page, a maintenance page or a consent wall served in place of the sitemap is HTML that Google cannot parse.
Invalid file
A blank line before the XML declaration, a file that is not UTF-8, unescaped ampersands or relative URLs.
Manual action or low demand
Google does not read sitemaps on sites with an unresolved manual action, and lists low crawl demand for the sitemap as a cause too.
How to test the sitemap yourself
Four commands in a terminal show most problems in a minute:
curl -I https://example.com/sitemap.xml
curl -s https://example.com/sitemap.xml | head -c 300
curl -s https://example.com/sitemap.xml | xmllint --noout -
curl -s https://example.com/robots.txt- Status: the first command should return 200 directly, without a redirect.
- Type: the headers should say XML. A
text/htmlresponse usually means you got a different page. - Start of the file: it should begin with the XML declaration or the
urlsetorsitemapindexelement, with nothing before it. - Validity:
xmllintprints nothing when the file is well formed, and the line number of the error when it is not. - robots.txt: no Disallow rule should match the sitemap path.
A request from your computer can succeed while Googlebot is blocked by bot protection, so the live test in URL Inspection is the one that counts.
How to fix "Sitemap could not be read"
- Test the sitemap URL live. Paste the sitemap address into URL Inspection and run Test live URL. If the fetch fails there, the problem is access, not the file.
- Check robots.txt. Google respects robots.txt when it fetches a sitemap. Remove any rule that blocks the sitemap path, and list the sitemap with a Sitemap: line.
- Submit the final address. Use the exact URL that answers 200, with the right protocol and host. A sitemap that redirects or moved with a plugin update should be submitted again at its new address.
- Let Googlebot through. Make sure firewall, CDN and security plugin rules do not challenge or block Google. A challenge page is HTML, not a sitemap.
- Make the file valid. UTF-8, nothing before the XML declaration, special characters escaped, absolute URLs, and no more than 50,000 URLs or 50 MB per file.
- Check for manual actions. Google does not read sitemaps for sites with an unresolved manual action. The Manual actions report tells you if there is one.
- Resubmit and watch. Submit the sitemap again in Search Console. Google retries failed fetches for a few days before it stops.
Notes by platform
WordPress
WordPress has its own sitemap at
/wp-sitemap.xml, and SEO plugins replace it with theirs. Submit the one that is actually active.Shopify
The sitemap at
/sitemap.xmlis generated for you. While the store is behind a password page, Google cannot fetch it.Wix and Squarespace
Both generate
/sitemap.xmlautomatically. A site set to private or not yet published cannot be fetched.Custom and static sites
Generate the sitemap from the same data that builds the pages, as this site does at build time, so it never lists pages that do not exist.
Questions about sitemap errors
What does "Sitemap could not be read" mean?
It means Google tried to fetch the sitemap and did not get a usable file. Google lists the causes as a robots.txt block, a manual action, a wrong sitemap URL, server errors, or low crawl demand for the sitemap. The status in the report shows as "Couldn't fetch".
How long does Google keep trying to fetch a sitemap?
According to Google, when a sitemap fetch fails it retries for a few days, then stops if the sitemap stays unavailable or has critical errors. After fixing the cause, submit the sitemap again so Google tries it once more.
Should I rename the sitemap file?
Only if the old address is wrong. Renaming a sitemap does not fix a robots.txt block, a firewall, a server error or an invalid file; those follow the new name. Find the cause first, then submit the address that actually works.
Does a sitemap error stop my pages from being indexed?
No. Google also finds pages through links. A broken sitemap slows down the discovery of new and deep pages, which matters most on large sites and on new sites that have few links yet.
How large can a sitemap be?
Google accepts up to 50,000 URLs or 50 MB uncompressed per sitemap. Larger sites split the URLs into several sitemaps and list them in a sitemap index file. An index file can list sitemaps, but not other index files.
Sitemap still not read?
Email the sitemap address and a screenshot of the Sitemaps report. I reply with what is blocking it and how to fix it.
- Email: calebe.development@gmail.com
- WhatsApp: +55 11 98838-5247
- Who replies: Calebe Araujo, the developer who does the work
Page updated on .