Sitemap Could Not Be Read: Causes and Fixes

1. Read the detailed Search Console error

Open Sitemaps, select the affected submission and expand the error details. Record the exact URL, status and last read date. “Couldn’t fetch” concerns retrieving the sitemap; parsing errors concern the file’s contents. Do not treat either as proof that every listed page has disappeared from the index.

Some fetch failures are temporary or related to low crawl demand. If your checks show a healthy file, compare later processing attempts instead of endlessly rewriting XML.

2. Check the final URL and HTTP response

• 404: verify that the submitted address actually exists. A CMS change may have moved the sitemap. Submit its real final address.
• 403, login or a bot challenge: review hosting and firewall rules. A successful browser visit does not prove Googlebot has access. Use Google’s live test and relevant server logs before changing security rules.
• 5xx or timeout: investigate application errors, hosting availability and intermittent failures. A timeout may have no HTTP response to report.
• 200: inspect the response body. An HTML maintenance page returned with 200 is still not the sitemap you intended to publish.

curl -i https://example.com/sitemap.xml

This command tests access from your connection. Changing its user agent to Googlebot does not reproduce or verify a real Googlebot request.

3. Validate the XML and child files

Check the root element, namespace, closing tags and absolute loc values. Escape special characters in URL query strings; for example, write & in XML rather than an unescaped ampersand. An index must point to readable sitemap files, not normal HTML pages.

A standard sitemap supports up to 50,000 URLs and 50 MB uncompressed. Split larger files and reference them from a sitemap index. These protocol limits are different from SitemapXML’s free processing limits: 2 MB per file, up to 10 files and 5,000 unique URLs for XML tools.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url><loc>https://example.com/catalog?page=1&amp;lang=en</loc></url>
</urlset>

4. Check what Google can retrieve

Paste the sitemap address into Search Console’s URL Inspection tool and run the live test. Review crawl permission and page fetch results. Check robots.txt for a rule blocking the sitemap itself, and compare the test with server logs around the failed request.

Do not disable a firewall or remove crawl restrictions blindly. Identify the rule or failing endpoint first. A child sitemap can fail even when its parent index loads correctly.

5. Separate XML errors from page exclusions

A readable sitemap can still list a noindex page, a redirect or a URL whose canonical points elsewhere. Those are page-level decisions, not evidence of malformed XML. Use URL inspection for indexing conclusions.

SitemapXML’s checker validates sitemap structure and metadata. Its website crawler records HTTP responses for the pages it actually visits. Parsing a list of XML URLs does not fetch those pages or prove their availability.

6. Recheck and resubmit after the fix

Validate the published file again, including child files, then resubmit the corrected URL. Review the next read date and error details rather than promising an instant status update. If errors recur after a release, check CMS updates, caching and the deployment path so the same problem does not return.