Sitemap Read Error in Google Search Console Fix

Frustrating, right? Let's fix it now.

You upload your sitemap to Google Search Console, and instead of seeing "Success," you get the error: "Sitemap could not be read." It's annoying, but it's almost always one of two things. I'll walk you through both fixes, starting with the one that works 9 times out of 10.

Fix #1: Check the URL encoding and redirects

This is the most common cause. Google's crawler is strict about HTTP status codes. If your sitemap URL returns a 301 redirect or a 302 redirect, Google won't read it. It expects a direct 200 OK response.

Here's how to test this:

1. Open your browser and go to your sitemap URL directly. For example: https://yoursite.com/sitemap.xml
2. Open the browser's developer tools (F12) and go to the Network tab.
3. Reload the page and look at the first request for the sitemap. Check the Status column.
4. If you see anything other than 200, that's your problem.

What I see most often is a 301 redirect from http:// to https://, or from www to non-www. For example, if your sitemap URL is http://yoursite.com/sitemap.xml but your site redirects all traffic to https://yoursite.com, Google will follow the redirect but then fail to parse the file.

The real fix: Submit the final redirect destination URL in Search Console. So instead of submitting http://yoursite.com/sitemap.xml, submit https://yoursite.com/sitemap.xml. Same goes for www vs non-www. If your canonical domain is www.yoursite.com, make sure your sitemap URL in Search Console starts with https://www.yoursite.com.

After you change it, click the "Submit" button again. You should see the status change from "Could not read" to "Pending" within a few minutes.

Fix #2: Validate your XML syntax

If the URL is returning a 200 OK, then your sitemap file itself might have a problem. Google expects valid XML. A single unescaped character or a broken tag will cause the whole thing to fail.

To check your XML:

1. Open your sitemap file in a text editor. Or if it's generated by a plugin (like Yoast on WordPress), open the raw output by going to your sitemap URL in a browser.
2. Copy the entire content.
3. Paste it into an XML validator like W3Schools XML Validator or W3C Markup Validation Service.
4. If you get errors, fix them. Common ones include:
   • Unescaped & (ampersand) — use & instead.
   • Missing closing tags — every <url> must have a </url>.
   • Invalid characters — Google only allows UTF-8 encoding. Check for stray non-ASCII characters.

I've seen WordPress Yoast sitemaps fail because a post title had a stray & or a # in the URL slug. The plugin usually escapes these, but occasionally a custom field or a plugin conflict mangles the output.

Once you fix the XML, re-submit the sitemap in Search Console. If you're using a CMS, regenerate the sitemap (e.g., in Yoast, go to SEO > General > Features and hit "Reset" on the sitemap option).

Less common variations of the same issue

1. Sitemap index file points to invalid sub-sitemaps

If you have a sitemap index (like sitemap_index.xml) that lists multiple sub-sitemaps, Google might report "Could not read" for the index while the sub-sitemaps are fine. This happens when one of the sub-sitemap URLs in the index is wrong — maybe it points to a 404 or a redirect. Check each <loc> inside your index file. Each one must return a 200.

2. Gzip compression mismatch

Some servers serve sitemaps with gzip encoding automatically. If your server sends a Content-Encoding: gzip header but the file isn't actually gzipped, Google can't read it. This is rare, but it happens when you manually gzip a file and the server configuration is wrong. To test, run curl -I https://yoursite.com/sitemap.xml and check the Content-Encoding header. If it says gzip, the file must be compressed. If it's not, disable gzip for XML files in your server config (Apache: SetEnv no-gzip 1 for .xml files).

3. Firewall or security plugin blocking Googlebot

I've seen Wordfence, Sucuri, and Cloudflare block Googlebot's user agent, causing a 403 or 503 error. Check your server logs for requests from Googlebot and see if they're being blocked. If you're using Cloudflare, make sure you have "Under Attack Mode" turned off (it shouldn't be on unless you're being DDoSed). For Wordfence, go to Wordfence > Firewall > Rate Limiting and ensure "Immediately block crawlers" is not enabled.

4. Huge sitemap file (over 50MB)

Google's limit for a single sitemap is 50MB uncompressed. If your file is larger than that, it will fail. Split it into multiple sitemaps using a sitemap index. Most CMS plugins handle this automatically, but if you're generating manually, watch the file size.

Why these fixes work

Google Search Console is a robot. It doesn't interpret — it only follows rules. If the HTTP response isn't exactly a 200, it stops. If the XML isn't perfectly valid, it stops. That's why the most common fix is just submitting the right URL that returns a direct 200. The XML validation part fixes cases where your content is technically sound but has a tiny syntax error that makes it unreadable.

I've debugged hundreds of these errors. I'd say 95% of sitemap read errors are solved by Fix #1. The other 5% are Fix #2. The less common variations above cover the remaining edge cases.

How to prevent this from happening again

• Always submit the canonical domain's version — if you use www, submit the www version of the sitemap. If you use non-www, submit that.
• Test your sitemap URL first — before submitting to Search Console, visit the URL in an incognito browser. Make sure it loads as plain text (not a download) and shows XML content.
• Monitor your server logs — set up a weekly check for Googlebot requests. If you see 4xx or 5xx errors, investigate right away.
• Use a plugin that auto-regenerates — if you're on WordPress, Yoast or Rank Math regenerate your sitemap automatically when you publish new content. That keeps your XML fresh and less likely to have encoding issues.
• Double-check your robots.txt — make sure your robots.txt file doesn't accidentally block Googlebot from accessing the sitemap directory. A Disallow: /sitemap.xml will cause a read error.

That's it. Try the first fix, and if it doesn't work, move to number two. You should have a green "Success" status within 24 hours.