Sitemap Couldn't Fetch or Could Not Be Read in Search Console

You submitted your sitemap in Google Search Console and it says "Couldn't fetch" or "Sitemap could not be read" instead of Success — Google either could not download the file or could not make sense of what it got.

Common signs of this issue

• The Sitemaps report in Search Console shows a status of "Couldn't fetch" next to your sitemap instead of "Success".
• Clicking into the sitemap shows an error such as "Sitemap could not be read", "General HTTP error", or "Sitemap is HTML".
• The "Discovered pages" count for the sitemap stays at 0, even days after you submitted it.
• The status shows "Has errors" and lists problems like invalid URLs, an invalid date, or URLs not allowed.
• Opening the sitemap address in your browser shows a 404 page, a login screen, your homepage, or a security check instead of a list of links.
• It started after a redesign, an SEO plugin change, a move to a new host, or turning on a firewall or CDN.

Safe checks you can do yourself

None of these require sharing passwords with anyone.

• Open the exact sitemap address you submitted in a private browser window. A working sitemap shows a list of page addresses (often in a plain or styled table). If you see a 404, your normal homepage, a login prompt, or a "checking your browser" page, Google is seeing the same thing.
• Compare the address you submitted with the one your site actually uses. WordPress's built-in sitemap lives at /wp-sitemap.xml, while Yoast and Rank Math use /sitemap_index.xml. Submitting the wrong one, or the http or non-www version of your domain, is one of the most common causes.
• Look at the date. A sitemap submitted in the last day or two can show Couldn't fetch simply because Google has not processed it yet. If it is brand new, give it a few days before treating it as a real error.
• Check yourdomain.com/robots.txt. It should not contain Disallow: / or a rule that blocks the sitemap's folder, and ideally includes a line starting Sitemap: with the correct address.
• Use URL Inspection at the top of Search Console on the sitemap address itself and click Test live URL. If Google gets an error, a redirect, or a blocked response, you have found the problem without touching anything.
• If you use Cloudflare or a security plugin, ask whoever manages it whether bot protection or a challenge page is turned on for all visitors. These tools sometimes block Googlebot from the sitemap even though you can open it fine.
• Make sure only one tool is creating a sitemap. Two SEO plugins, or an SEO plugin plus a separate sitemap plugin, can fight over the same address and produce a broken or empty file.
• On a very large site, ask your developer whether the sitemap is split into smaller files. A single sitemap is limited to 50,000 URLs and 50MB uncompressed, and a huge file that takes too long to generate can time out.

What this usually means

Couldn't fetch means Google tried to download the sitemap and did not get a usable file back. That can be a temporary state on a brand-new submission, but if it persists it usually points to the address being wrong, the file being blocked by robots.txt or a firewall, the server returning an error, or the request being redirected somewhere unexpected. Sitemap could not be read is closely related: Google reached the address but what came back was not a valid sitemap — often an HTML page, an empty response, or broken XML.

The most common real-world causes are mundane. An SEO plugin was switched or deactivated and the old sitemap address no longer exists. A caching or minification plugin altered the file. A PHP warning or stray blank line at the top of the output corrupted the XML. A security tool decided Googlebot looked suspicious. Or the site moved to https or a new domain and the old sitemap address was never updated in Search Console.

It is worth knowing what a broken sitemap does not do: it does not remove your site from Google or block indexing on its own. Google still finds pages through links. But on a new site, or a site with many pages that are not well linked, a working sitemap is how Google learns about everything quickly, so a failing one slows discovery and should be fixed rather than ignored.

What not to do

• Don't delete and resubmit the sitemap over and over. It does not speed anything up and makes it harder to tell when the real fix worked.
• Don't panic about a Couldn't fetch status on a sitemap you submitted a few hours ago. New submissions often show it before Google gets to them.
• Don't install a second sitemap plugin to work around the first. Two generators competing for the same address is a cause of this error, not a cure.
• Don't block Googlebot in a firewall or security plugin to stop bad bots. Turning on aggressive bot blocking without exceptions for real search engines often causes exactly this.
• Don't hand-edit the sitemap file on the server if a plugin generates it. Your changes will be overwritten, and a single typo can make the whole file unreadable.
• Don't assume the sitemap is why traffic dropped. A broken sitemap slows discovery but rarely causes a sudden ranking fall on its own.

When to get help

If the sitemap opens fine in your browser but Search Console still says Couldn't fetch after a week, the problem is usually something only visible from the server side — a firewall rule, a CDN setting, a redirect that only Googlebot sees, or invalid characters in the output. Someone who can read the raw response and your server or Cloudflare logs can usually pin that down in under an hour. It is also worth bringing in help after a site move or domain change, when a stale sitemap is often a sign that other redirects and settings were missed too.

Frequently asked questions

Related free guides