In Google Search Console, “Couldn’t fetch” means Google could not retrieve the sitemap file itself. It does not identify why the fetch failed, prove that your whole site is broken, or mean that every URL in the sitemap is unindexed. Check the sitemap’s report details and run URL Inspection’s Live test to narrow down the cause.
What “Couldn’t fetch” means
Google’s Sitemaps report documentation defines the top-level “Couldn’t fetch” status as a failure to retrieve the sitemap file itself. That is different from Google fetching and reading a sitemap but reporting errors in its contents or processing.
As an Amazon Associate I earn from qualifying purchases.
The status alone does not reveal the cause. Google lists several possibilities, including a sitemap blocked by robots.txt, an unresolved manual action, an incorrect or missing sitemap URL, a general error such as server unavailability, or low crawl demand. Google does not rank these causes by likelihood.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to diagnose the fetch failure
- Open the sitemap’s details. In Google Search Console, go to the Sitemaps report and select the affected sitemap entry. Review the details for its last fetch and open the reported error for more information.
- Check the exact submitted URL. Copy the sitemap URL shown in the report and confirm it is the intended address. A typo, a sitemap that is not located at that address, or a 404 response can prevent retrieval.
- Run a Live test. In URL Inspection, enter the sitemap URL and run the Live test. Expand Page availability and check for “Crawl allowed? = Yes” and “Page fetch = Successful.” These are the checks Google specifies for debugging fetch errors in its Sitemaps report guidance.
- Use the results to investigate the relevant configuration. If the report or test points to robots.txt, server availability, or another access issue, check that configuration with your site or hosting administrator. The report’s specific details are more useful for diagnosis than the top-level status alone.
Causes Google lists
- robots.txt blocks the sitemap. If a rule prevents Google from fetching the sitemap, Google’s guidance is to remove the rule that blocks it. Google’s robots.txt specification also recognizes a
Sitemapfield containing the complete sitemap URL. That field helps Google discover a sitemap; it does not, by itself, remove a fetch block or guarantee that a fetch will succeed. - An unresolved manual action. Google says it does not read sitemaps in this situation. Check Search Console for manual-action information if the error details suggest this applies.
- The URL is wrong or the sitemap is missing. Confirm the submitted address and whether the sitemap exists there; Google specifically includes a 404 response as a possible reason.
- A general or transient error. Server unavailability is one example. Google notes that some general errors can be transient, but its guidance does not promise a recovery time.
- Low crawl demand. Google lists this as another possible cause and says crawl demand is higher for higher-quality site content. The status by itself does not establish whether this is the reason for a particular sitemap.
Fetch failures are not the same as sitemap-content errors
A fetch failure means Google could not retrieve the sitemap file. A content or parsing error means Google fetched and at least partially read it, but encountered a problem in the sitemap or its processing. Do not rewrite the XML based only on the top-level “Couldn’t fetch” label; first use the report details to establish what happened. If an error names a URL inside a sitemap, Google advises inspecting that URL with URL Inspection.
#1 Best Overall
What to do if the cause is still unclear
A sitemap opening in your own browser does not, by itself, establish why Google’s fetch failed or complete the diagnosis. Compare the report’s last-fetch details with the Live test, then check the site’s URL, robots.txt rules, manual-action status, and server configuration as indicated by those results. If Google reports a general error, it may be transient, but the cited guidance gives no universal waiting period; use later report details to see whether the failure recurs.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
