Sitemap could not be read or couldn’t fetch: check what the URL returns

Updated · Check Before Publish

“Sitemap could not be read” in Search Console's Sitemaps report means Google failed to fetch the sitemap file; “Couldn't fetch” is the same failure on the main list. Check what the URL returns: a 200 status, valid sitemap XML rather than an HTML page, and no robots.txt rule blocking it. Then fix what you find and resubmit.

A sitemap Google could download but that has problems shows as “Has errors” instead. Some fetch errors are temporary: Google says to wait a bit and see whether the error keeps appearing on later crawl attempts. If every check below passes, wait before changing anything.

Check these in order

  1. Is it the right URL? Search Console shows only the sitemaps of the current property, and confusing http and https, or www and non-www properties, is a common reason you don't see yours. The URLs inside a sitemap must use the same protocol and host as the sitemap file.
  2. Does it return 200? Google lists a 404 at the submitted address as a cause, and it does not follow redirects on the address you submit, so submit the final URL. Bot protection that turns crawlers away can also stop the fetch.
  3. Is it XML, or an HTML page? Google's report has an “Unsupported format” error, and sitemaps must be XML, text or RSS/Atom, so an HTML page will not work. Many sites answer any unknown address with their home page or a “not found” page and a 200 status. Google then receives an HTML page where it expected XML. Open the URL and View Source: it should start with <?xml and a <urlset> or <sitemapindex> element.
  4. Is the XML valid? A single unescaped & in a URL is enough to break the file; it must be written as &amp;. The root element must be urlset or sitemapindex.
  5. Is it within the limits? A sitemap may list up to 50,000 URLs and be up to 50 MB uncompressed; larger sites need a sitemap index that points to several files. An empty sitemap is reported as an “Empty sitemap” error.
  6. Does robots.txt block it? Google respects robots.txt when fetching sitemaps, so a Disallow rule that matches the sitemap's path stops the fetch.

Check it in one go

Paste your site or sitemap address. The checker finds the sitemap (from the Sitemap: lines in robots.txt, then /sitemap.xml and /sitemap_index.xml), checks the status, whether it is XML or an HTML page, whether the XML is valid, the size and URL limits, and then samples the URLs it lists for 404s, redirects, noindex and robots.txt blocks.

Opens the Sitemap Checker and runs it. Free, no account. The address is not stored and never goes into the URL bar.

How to fix it

  • HTML instead of XML, or a 404: the sitemap doesn't exist at that address. Generate it (most CMSs and SEO plugins can) or submit the address where it really lives. On a static or JavaScript-framework site, make sure the build actually writes the file.
  • Invalid XML: fix the generator, or escape the characters that break it.
  • Wrong host: submit the sitemap in the property that matches the live address.
  • Blocked: remove or narrow the robots.txt rule (see Blocked by robots.txt), and adding a Sitemap: line to robots.txt helps other search engines find it too.

How to confirm the fix

Run the check again until the sitemap loads as valid XML, fix whatever it found, then resubmit it in Search Console. The status updates when Google next fetches it. The listed URLs matter as much as the file: a sitemap full of redirects or noindex pages sends mixed signals, which is why the checker samples them.

What this check can't tell you

We fetch from our own server, not from Google's. A firewall that treats Google's crawler differently from ours can give different results. For large sitemaps we sample the listed URLs rather than reading every one.

Sources

We read these official pages on 2026-10-13.

Fixed this one? Before you send people to the page, run the full pre-publish check for everything else: indexing signals, link preview, broken links, alt text, structured data and HTTPS in one pass.