stillindexedStart free trialOpen the app

Search Console: Sitemaps report

Couldn't fetch sitemap in Search Console: what it means

Why the Sitemaps report says Couldn't fetch: robots.txt, a manual action, a wrong URL, a server error, or low crawl demand. How to tell which.

Google did not retrieve the sitemap file. Google lists five reasons: robots.txt blocks it, an unresolved manual action, a wrong URL (404), another error such as the server being unavailable, or low crawl demand. Fetch the file as a crawler would; if it returns valid XML with a 200, the cause is usually on Google's side.

What "Couldn't fetch" means

Google's Sitemaps help: "Couldn't fetch: The sitemap could not be fetched for some reason", meaning "Google couldn't retrieve the sitemap file itself". The listed reasons are a robots.txt block ("Google respects robots.txt when fetching sitemaps"), an unresolved manual action ("Sitemaps are not read when a site has an unresolved manual action"), a wrong URL returning 404, "some other general error" such as server unavailability, and "low crawl demand for the sitemap". In October 2026 John Mueller said Google may show the same status when it simply had not got round to the file: "we didn't have time to actually fetch it".

Is it a problem?

Depends on the URL

Only if the file is actually unreachable. If a crawler fetch returns the sitemap with a 200 and valid XML, the status may only mean Google has not fetched it yet, and Google says a sitemap it read before is not forgotten: "A later failure or success to read a sitemap will not cause Google to "forget" the information from previous reads." URLs Google finds through links still get crawled without the sitemap.

Causes, most likely first

  1. The sitemap URL is wrong or returns 404: a typo on submission, a plugin that moved the file, or a CMS change from sitemap.xml to sitemap_index.xml.
  2. A robots.txt Disallow rule matching the sitemap path, often a broad rule such as "Disallow: /*.xml" or a staging "Disallow: /".
  3. A server, CDN or bot protection error when Googlebot requested the file, which Google says can be transient.
  4. Low crawl demand. Mueller tied crawl demand to "the perceived quality of a website" and said "it's not purely a technical thing".
  5. An unresolved manual action on the site. Check the Manual actions report.

How to confirm it

  1. Run the sitemap validator on the exact URL you submitted. It fetches the file, reports the HTTP status, and parses the XML.
  2. Run the robots.txt tester with the sitemap URL to see whether any rule blocks it for Googlebot.
  3. Run the sitemap audit to check that the URLs listed inside it return 200 and are indexable, which is what makes a sitemap worth Google's time.
  4. Open the Manual actions report, and Crawl stats for host availability problems over the past 90 days.

Sitemap validatorSitemap hygiene checkRobots.txt validator and tester

How to fix it

  1. If the URL is wrong, submit the correct one and remove the dead entry from the report.
  2. If robots.txt blocks it, remove or narrow the rule. Google says "You must remove the rule that prevents Google from fetching your sitemap."
  3. If the server returned an error, fix it for crawler requests and confirm with the sitemap validator.
  4. If the file fetches cleanly and no manual action exists, leave it. Google says some of these errors are transient: "wait a bit and see if Google continues to encounter this error in later crawl attempts." Resubmitting does not create crawl demand.

How long recovery takes

Google says that when a fetch fails it "will retry for a few days, and then stop if the sitemap continues to be unavailable or has critical errors". It documents no timeline for a sitemap affected by low crawl demand.

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

robots.txt blocking pages that should be crawled, platform by platform

Further reading

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: