stillindexedStart free trialOpen the app

Search Console: Sitemaps report

Sitemap could not be read in Search Console: the fix

The Sitemaps details page says Sitemap could not be read: the fetch failed. How to find which fetch error it was and when to resubmit.

This message on a sitemap's details page means the fetch failed, for one of the reasons shown beneath it. Expand the error, reproduce the fetch with a sitemap validator, fix the URL, robots.txt rule or server error, then resubmit. Google retries a failed sitemap a few times before it stops trying.

What "Sitemap could not be read" means

Google: "If the details page says Sitemap could not be read, then the fetch failed for one of these reasons, as shown in the details page. Expand the section below the error to see more details. Try to fix the problem and resubmit the sitemap to the report. If a sitemap fetch fails, Google will try a few more times, but will eventually stop trying to read that sitemap." It is the details-page form of the top-level Couldn't fetch status, not a separate error type.

Is it a problem?

Usually a problem

Yes, if you rely on the sitemap for discovery. A file Google cannot fetch contributes nothing, and Google eventually stops trying. If the file fetches cleanly for a crawler today, read the Couldn't fetch page: the cause may be crawl demand rather than your server.

Causes, most likely first

  1. The submitted URL returns 404 or another 4xx.
  2. robots.txt blocks the sitemap path for Googlebot.
  3. A server, CDN or firewall error when Googlebot requested the file.
  4. Low crawl demand or an unresolved manual action, the two non-technical reasons Google lists for fetch failures.

How to confirm it

  1. Expand the section under the error in Search Console to see which fetch error Google recorded.
  2. Run the sitemap validator on the submitted URL for the status code and parse result a crawler gets now.
  3. Run the robots.txt tester on the sitemap URL.

Sitemap validatorSitemap hygiene checkRobots.txt validator and tester

How to fix it

  1. Fix the cause the details page shows: the URL, the robots.txt rule, or the server response.
  2. Confirm with the sitemap validator that the file returns 200 and parses.
  3. Resubmit the sitemap in the Sitemaps report, as Google's help page instructs.

How long recovery takes

Google says that after a failed fetch it "will retry for a few days, and then stop if the sitemap continues to be unavailable or has critical errors". Resubmitting after the fix asks it to try again.

Would monitoring have caught it?

A sitemap that stops being fetchable, or whose URL count drops by more than half, is a warning on the next daily sitemap check, and the change history keeps the status and the count we saw. It reads the sitemap as our crawler receives it; it cannot see Google's crawl demand, a manual action, or what Search Console shows.

stillindexed reads each site's sitemap once every 24 hours on every plan, independently of Search Console.

Start the 14-day free trial, 3 sites, no card required

Sources

Every claim above about how Google behaves is from Google's own documentation, read on 2026-10-22. If Google has changed a page since, Google's page wins and we would like to know.

Quotes from Google staff are as reported here, not from Google's documentation: