"Sitemap could not be read": how to fix it

Sitemap could not be read means Google's download failed. The details below it, such as General HTTP error or an HTTP error with a code, tell you why.

Where you see it

In Indexing > Sitemaps, click the sitemap. The details page says Sitemap could not be read. Expand the section below the error to see the details.

What it means

This is the details page for a fetch that failed. On the main table, the same sitemap usually shows Couldn't fetch.

Google shows the reason below the message. Two of the most common are General HTTP error and HTTP error with a status code, such as 404.

Common causes

The server answered with an error code. 404 means no file at that address. 403 means the server refused. 5xx means the server failed.
A redirect leads somewhere Google can't follow, such as a login page or another domain.
A firewall or bot protection answered Googlebot with a challenge page.
The server timed out because the sitemap is built on the fly and is slow to make.

Find the cause

Expand the details under the error. Note the code if Google shows one.
Open the sitemap address in a private browser window and watch where it ends up.
Run Test live URL in URL Inspection on the sitemap address, then click View tested page and look at the HTTP response.

How to fix it

For 404: submit the address that really serves the sitemap, or turn the sitemap back on in your platform or plugin.
For 403, 429, or a challenge page: let Googlebot through your firewall, CDN, or security plugin.
For 5xx or timeouts: ask your host why the server fails, or cache the sitemap so it loads fast.
Run Test live URL again until Page fetch says Successful.
Resubmit: type the address in Add a new sitemap and click Submit.

Each message and its fix

"General HTTP error"

Google got an HTTP error that has no more specific message. Google's help says this can also be a 404.

Expand the details in Search Console to see what kind of error it was.
Open the address in a private browser window and run Test live URL to see the status code.

"HTTP error [specific code]"

Google got a 400-level error, and the message shows the code, such as 404.

Make sure the sitemap URL you submitted is correct and the file exists there.
Then resubmit the sitemap.

See which of your pages Google skipped, and why. Free for up to 500 pages.

Get my free report

On your platform

Shopify

Shopify makes your sitemap at /sitemap.xml and links it to smaller sitemaps for products, collections, blogs, and pages. Submit only sitemap.xml, in the Search Console property for your primary domain. Google can't read the sitemap while the store is in private mode with a password page. Submitting a sitemap from your myshopify.com address or another domain that redirects is a common cause. Shopify pages not indexed

WordPress

WordPress itself serves /wp-sitemap.xml. Yoast SEO and Rank Math serve /sitemap_index.xml instead, and Yoast turns off the WordPress one. Submit the address your site really uses. WordPress turns its sitemap off when Settings > Reading > Discourage search engines from indexing this site is checked. For a 404 on Yoast's sitemap, open Settings > Permalinks and click Save without changing anything. If that does not help, your server's rewrite rules need the sitemap rules. WordPress pages not indexed

Cloudflare and other firewalls

A challenge page answers with an error code to a crawler. Check your security events log for the sitemap address, and change the rule so it leaves out known bots.

Catch sitemap problems before they cost you pages

On paid plans, CrawlCoach downloads your sitemaps every day and reads Search Console's sitemap data for each fix list. When a sitemap stops loading, Search Console reports errors in it, or Google stops reading it, the fix goes in your fix list with the steps and a link to the right guide. See plans and prices.

Questions

What does General HTTP error mean for a sitemap?

Google could not download the sitemap because of an HTTP error that has no more specific message. Expand the details in Search Console to see the kind of error, then open the address yourself and run Test live URL on it.

Why does my Shopify sitemap say it could not be read?

Common causes are a sitemap submitted in a property that does not match the primary domain, and a store in private mode. Submit sitemap.xml in the property for your primary domain, and turn off the password page.

How long after a fix does the error go away?

Resubmit the sitemap after the fix. Google tries to fetch a sitemap as soon as you submit it, and the status updates after that try.

Sources

Checked on October 8, 2026. Search Console's wording can change after that date.

"Sitemap could not be read" and General HTTP error: how to fix it