Sitemap could not be read

“Sitemap could not be read” and “Couldn’t fetch”: how to fix them

Sometimes the sitemap is fine and Google just hasn’t fetched it. Here’s how to tell, and the full checklist for when something really is wrong.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

“Sitemap could not be read” and “Couldn’t fetch” in Google Search Console mean Google didn’t get your sitemap file on its last attempt. Often the file is fine and Google simply hasn’t fetched it yet, particularly right after you submit it; Google has said the status also appears when it is too busy or sees little reason to crawl. If it lasts more than a few days, check that the sitemap URL returns a 200 status with real XML, isn’t blocked by robots.txt or a firewall, and belongs to the property you submitted it in, then resubmit.

Fast test: paste the sitemap URL into our free sitemap checker, which checks the status code, content type, XML and size limits in one go, then run it through URL Inspection’s Test live URL, which fetches as Googlebot. If both pass, the file is reachable and Google will most likely read it on a later try. If either fails, work through the checklist below.

What the messages mean

The Sitemaps report (Indexing > Sitemaps) gives each submitted sitemap one of three statuses. Click a sitemap to see its details, where the specific error appears. Descriptions from Google’s Sitemaps report help:

MessageMeaning
SuccessLoaded and processed with no errors.
Has errorsFetched, but with one or more errors, such as invalid XML, invalid URLs or too many URLs.
Couldn’t fetchGoogle couldn’t fetch the sitemap. Google lists robots.txt blocks, a 404, temporary server problems, an unresolved manual action and low crawl demand as causes.
Sitemap could not be readThe message on the details page of a sitemap that couldn’t be fetched. Same problem as Couldn’t fetch.
General HTTP error / HTTP errorGoogle got an HTTP error, such as a 404 or another 4xx, when it requested the file.
Temporary errorA passing problem. Google suggests resubmitting only if it lasts several hours.

Is it really broken? What Google said in October 2026

In early October 2026, Google’s Martin Splitt and John Mueller discussed this exact case: a sitemap that is valid, reachable and listed in robots.txt, yet shows “Couldn’t fetch”. Mueller’s explanation was that the status can mean Google hasn’t had time to fetch the file, that the server or crawl capacity got in the way, or that crawl demand is low, which he tied to Google’s perceived quality of the site (Search Engine Journal, 6 October 2026).

So the first step is to rule out a real fault. If the sitemap URL loads, returns 200 and contains valid XML, give it a few days: Google’s help says it keeps trying to fetch a sitemap for a few days after a failure. If the status stays on a site that is otherwise crawled normally, keep going through the checklist. If the whole site is crawled slowly, the sitemap is a symptom; the cause is in why Google isn’t crawling your pages.

The full checklist

1. The URL and the property match

A sitemap belongs to one Search Console property. In a URL-prefix property such as https://www.example.com/, submit only sitemaps under that prefix, listing only URLs under it. If the sitemap or its URLs use http, or drop the www, Google reports “URL not allowed” or “Path mismatch”. Google’s help specifically warns about mixing up http/https and www/non-www properties. A Domain property avoids most of this.

2. The sitemap returns 200, without redirects

Check the status code the server really sends:

curl -sI https://www.example.com/sitemap_index.xml

You want HTTP/2 200. A 404 means the path is wrong or the plugin’s sitemap is off. A 403 or 5xx means the server or a security layer refused. A 301 or 302 means you submitted an old address: submit the final URL instead.

3. It is really XML, served as XML

Open the URL and view the source. The file should start with an XML declaration and a <urlset> or <sitemapindex> element using the http://www.sitemaps.org/schemas/sitemap/0.9 namespace. Serve it as application/xml or text/xml. A text/html response is a common sign that the site returned a web page instead: single-page apps and some frameworks answer every unknown path with the home page, which looks fine in a browser’s address bar and is not a sitemap.

4. robots.txt allows it

A rule such as Disallow: /*.xml or a blocked folder can stop Google fetching the sitemap (more on robots.txt blocks). Check your robots.txt, and Search Console’s robots.txt report to see the version Google last fetched. See sitemaps in robots.txt for the right setup.

5. No firewall, CDN or security plugin is blocking Googlebot

This is the most common cause when the file loads fine for you. Country blocks, rate limits, bot challenges and “under attack” modes can give Googlebot a block page or a challenge instead of XML. Look in your server or CDN logs for requests to the sitemap from Googlebot and the status they got. Confirm they are really Google using Google’s reverse DNS check, then allow verified Googlebot through. The URL Inspection live test is a good confirmation, since it fetches with Google’s own crawler.

6. The file is within the size limits

A single sitemap can hold at most 50,000 URLs or 50MB uncompressed. Larger sites split URLs across several sitemaps and list them in a sitemap index, which can list up to 50,000 sitemaps (Google’s large sitemaps guide). A sitemap index can’t list another sitemap index; Google reports that as “Nested sitemap indexes”. You can submit up to 500 sitemap index files per site.

7. Compression is done properly

Sitemaps may be gzipped, and the 50MB limit applies to the uncompressed file. A “Compression error” usually means a file named .xml.gz that isn’t really gzip, or one compressed twice. Recompress it, upload it and resubmit.

8. The XML is valid

9. It loads quickly

Plugin sitemaps are often built on the fly when requested. On a directory with tens of thousands of listings, a sitemap that takes 30 seconds to generate can time out for Google even if it eventually loads for you. Cache the sitemap files or generate them on a schedule, and keep each file well under the limits.

10. Resubmit once, then wait

After fixing the cause, open the sitemap in the Sitemaps report and resubmit it, or submit it again from the top of the report. Deleting and re-adding it repeatedly doesn’t help. Google rereads successfully fetched sitemaps on its own schedule.

Sitemaps on directory platforms

Most directories don’t write their sitemaps by hand; a plugin or add-on does, and that is where these errors usually start:

Split sitemaps by page type (sitemap-listings-1.xml, sitemap-cities.xml, sitemap-categories.xml) even when one file would fit. Then the Page indexing report, filtered by sitemap, tells you which template Google is leaving out.

Does “Couldn’t fetch” stop pages being indexed?

Not directly. Google calls submitting a sitemap merely a hint, and it finds most pages through links anyway. On a small, well-linked site a sitemap error changes little. On a large directory where many listings are linked only from deep pagination, the sitemap is how Google learns about new and changed pages, so a sitemap that can’t be fetched means new listings get found much later.

How DirectoryLens helps

The Sitemaps tab in Google indexing lists the sitemaps you submitted in Search Console and re-reads every one each day, following sitemap indexes and unzipping gzipped files. For each sitemap it shows the URL count and when it was last read, and any sitemap that couldn’t be loaded is listed at the top with the error, such as the HTTP status. You also get URL counts per sitemap now, 7 days ago and 30 days ago, a chart of total sitemap URLs, and an alert when a sitemap or the total loses 20% or more of its URLs within a week (you can change the threshold).

One honest limit: DirectoryLens fetches your sitemaps with its own crawler, not as Googlebot, and it doesn’t show Google’s own status from the Sitemaps report. A firewall rule that blocks only Googlebot won’t show up there; the URL Inspection live test is the check for that. What it catches well is the sitemap that quietly broke or shrank after a plugin update, before Google’s status changes. For every other indexing status, see the page indexing issues guide.

Questions

Why is my sitemap not working?

Usually the URL doesn’t return 200 with XML, robots.txt or a firewall blocks Googlebot, the sitemap is in a different Search Console property than its URLs, or the file breaks a limit or has XML errors. Sometimes Google just hasn’t fetched it yet.

How do I fix “Sitemap couldn’t fetch”?

Open the sitemap URL to confirm it loads as XML with a 200 status, check robots.txt and any firewall or CDN rules, test it with URL Inspection’s live test, then resubmit it once in the Sitemaps report and wait a few days.

Why isn’t Google reading my sitemap?

Google may not have fetched it yet, may be blocked from it, or may see little reason to crawl the site. Google’s John Mueller said in October 2026 that low crawl demand, often tied to perceived site quality, can cause the status.

How do I add a sitemap to Google?

In Search Console, open Indexing > Sitemaps, enter the sitemap URL and click Submit. You need owner access; without it, list the sitemap in your robots.txt with a Sitemap: line.

Should I delete and resubmit my sitemap?

Resubmit once after you fix the cause. Deleting and re-adding it again and again doesn’t speed anything up, and Google rereads sitemaps on its own schedule.

Does “Couldn’t fetch” stop my pages being indexed?

Not directly; Google also finds pages through links. But on a large site with weak internal linking, new pages will be found much more slowly until the sitemap can be read.

Know the day a sitemap breaks.

Connect Search Console and DirectoryLens re-reads every submitted sitemap daily and alerts you when one fails or loses URLs.

Explore the live demo →

5 days free · no card needed · ends on its own