“Sitemap Could Not Be Read”: What to Check First

What does “Sitemap could not be read” mean?

The message means Google Search Console has not successfully fetched or processed the submitted sitemap. In the Sitemaps report, the overall status may appear as Couldn't fetch. Opening the submission can reveal a more specific reason, including “Sitemap could not be read”.

The message identifies a problem with the sitemap submission or file. It does not automatically mean that every URL in the sitemap is broken, deindexed or blocked from search.

A sitemap is a discovery aid. It gives search engines a structured list of canonical URLs that you would like them to crawl and consider for indexing. Search engines can still discover pages through internal and external links, but an unreadable sitemap removes one useful discovery route and makes sitemap reporting less reliable.

Is it still processing or genuinely failing?

A newly submitted sitemap does not always receive a final status immediately. If you have just added it, the file loads correctly and Search Console gives no specific technical detail, allow Google time to process the submission before changing the site repeatedly.

Investigate when the status persists, when Search Console gives a clear fetch or parsing error, or when your own checks show that the sitemap is unavailable or malformed.

Use these questions to separate a short delay from a technical failure:

• Was the sitemap submitted only recently?
• Does the exact submitted URL load without a login?
• Does it return a successful 200 OK response?
• Is the response XML rather than an HTML error page?
• Can crawlers reach it without being blocked by robots.txt, a firewall or a security service?
• Does Search Console show a specific error in the submission details?

Avoid deleting and resubmitting the same sitemap several times while it is still being processed. That does not correct a technical problem and can make it harder to judge when the status changed.

Why this sitemap error matters

An unreadable sitemap deserves attention because search engines cannot use the file as intended.

• Discovery may be slower: new, updated or poorly linked pages lose a useful route through which crawlers can find them.
• Coverage becomes less clear: Search Console cannot report accurately on URLs from a sitemap it has not processed.
• Larger sites feel the effect more: sites with many products, articles or frequently changing pages often depend more heavily on clean sitemap discovery.
• The error may reveal a wider problem: a failed response, crawler block or incorrect hostname may affect more than the sitemap itself.

The error is not a penalty, and submitting a working sitemap does not guarantee that its URLs will be indexed. Every listed page still needs to be accessible, indexable, useful and supported by consistent site signals.

What to check first

Work from the simplest live checks towards the less visible configuration problems.

1. 01
   Open the exact submitted URL.

   Copy the full sitemap URL from Search Console and open that address. Do not type the address from memory. Check the protocol, hostname, subdomain, path and filename.

   http://example.com/sitemap.xml
   https://example.com/sitemap.xml
   https://www.example.com/sitemap.xml
   https://www.example.com/sitemap_index.xml

   The intended URL should load without a password, account session or consent step.

2. 02
   Check the HTTP response.

   The sitemap should normally return 200 OK. A 404 means the file is missing at that address. A 5xx response points to a server or application failure. A redirect may still be followed, but submitting the final working URL removes ambiguity and avoids depending on a redirect chain.

   Check the content as well as the status. Some systems return a friendly HTML error page with a 200 status. A browser may display that response without making it obvious that the XML file is missing.

3. 03
   Confirm that crawlers are allowed to fetch it.

   Review robots.txt and any protection in front of the site. A content delivery network, web application firewall, bot filter, rate limit, IP rule or maintenance screen can serve Google a different response from the one you see in a normal browser.

   The sitemap needs to be publicly accessible. Do not place it behind a login or restrict it to an office network.

4. 04
   Inspect the XML structure.

   A sitemap should be UTF-8 encoded and use the supported XML sitemap format. It should contain either a <urlset> for page URLs or a <sitemapindex> for links to child sitemaps, with the correct namespace and properly closed tags.

   Every location should be a complete URL:

   <url>
     <loc>https://www.example.com/example-page/</loc>
   </url>

   Unescaped special characters, broken tags, invalid encoding or HTML inserted before the XML can prevent successful processing.

5. 05
   Check the size and submission setup.

   A single sitemap is limited to 50,000 URLs or 50 MB when uncompressed. Split a larger set into separate files and connect them with a sitemap index.

   Also check that you are viewing the correct Search Console property. HTTP and HTTPS, and www and non-www, can be separate URL-prefix properties. A submission in one property will not necessarily appear where you expect in another.

Check the live setup in Clearcrawl

Clearcrawl checks the technical state of the live site. This helps you spot a missing file, incorrect declaration, access problem or mismatch between robots.txt and the sitemap you meant to submit.

Search Console supplies the other half of the diagnosis: whether Google has fetched and processed that submitted file. Use both views together rather than expecting either one to explain the entire path.

Understanding the likely causes

When the error affects a generated sitemap, fix the generator or template rather than editing the output once. A CMS or plugin may overwrite a manual correction the next time content changes. After fixing access or XML errors, verify the sitemap discovery setup and check whether the submitted pages can be indexed. A sitewide crawl with SEO software can help reveal recurring technical problems.

How to fix a sitemap that cannot be read

1. 01
   Decide which sitemap URL should be permanent.

   Choose one stable HTTPS URL on the intended hostname. If you have several child sitemaps, use a sitemap index as the main submission. Update internal settings so the same address is generated consistently.

2. 02
   Restore a clean public response.

   Make the file return 200 OK without a login, security challenge or avoidable redirect. Fix server errors and confirm that the response body contains sitemap XML rather than an HTML page.

3. 03
   Remove crawler access conflicts.

   Check robots.txt, firewall rules, CDN settings and bot protection. Make sure legitimate crawlers can retrieve the sitemap reliably. If the site uses aggressive rate limiting, test whether repeated crawler requests are being refused.

4. 04
   Correct the XML and contents.

   Repair malformed elements, character encoding and invalid URLs at their source. Keep each sitemap within the size limits and include fully qualified canonical URLs that belong in search. Remove redirects, error pages and unwanted duplicate versions from the URL list.

5. 05
   Align discovery and submission.

   Add the working sitemap or sitemap index to robots.txt using its complete URL:

   Sitemap: https://www.example.com/sitemap.xml

   Then submit that same address in the matching Search Console property. This gives supporting crawlers a public declaration while preserving Google-specific status reporting.

How to verify the fix

Verify the live response before waiting for Search Console to update.

• Open the exact sitemap URL and confirm that it returns the intended XML.
• Follow any child sitemap links and check that they also load.
• Review robots.txt and confirm that its Sitemap: line matches the working address.
• Run another Clearcrawl crawl and confirm that the previous live-site warning has cleared.
• Resubmit the repaired sitemap in Search Console if needed, then monitor its status.
• Once processed, review the discovered page count and any remaining sitemap-specific errors.

Google may need time to fetch the file again. A successful live repair can therefore exist before the Sitemaps report shows the new result. Continue investigating if the error persists after Google has had another opportunity to process the submission.

Common mistakes

Frequently asked questions