How do I fix \"Couldn't fetch\" for my sitemap?

"Couldn't fetch" means Google Search Console was unable to download your sitemap file. Open the exact submitted address in a browser and confirm it returns status 200 with XML, with no login, firewall block, robots.txt rule or redirect loop in the way. Then resubmit it. If the file is fine, check again later, because the status can be temporary.

Why it matters

Until the fetch works, Google gets no sitemap from you, so new pages rely on links alone for discovery. The cause is usually something small, such as a typo in the address or a security rule that treats Googlebot like an unknown visitor.

How to fix it

Copy the address exactly as it appears in the Sitemaps report. A missing www, a wrong folder or a trailing character is enough to fail.
Test the address from outside your own network:

curl -I -L https://www.example.com/sitemap.xml

Look at the final status line. It should be 200, and the content type should be an XML type such as application/xml or text/xml.

Make sure the host name resolves and the HTTPS certificate is valid and not expired. A certificate warning stops automated fetches.
Count redirects. One redirect, for example from http to https, is acceptable. A loop, or a redirect to a login page, is not.
Review firewall, security plugin and CDN bot rules. Googlebot should not receive a challenge page or a 403. The guides on verifying Googlebot and Bingbot and on Cloudflare bot blocking explain how to tell real crawlers from fakes.
Search your server logs for requests to the sitemap path from Googlebot, and read the status codes returned.
Check that the file is not so large or so slow to build that the request times out. Cache the generated file if your site builds it on each request.
Resubmit the same address in the Sitemaps report.

Common mistakes

Submitting a sitemap that sits behind staging authentication or an IP allow list.
Submitting under a URL-prefix property that does not match the address of the sitemap.
Blocking the sitemap path in robots.txt.
Rate limiting or blocking crawler traffic in a firewall without allowing known search engine crawlers.
Deleting and re-adding the sitemap repeatedly instead of finding the cause.

Frequently asked questions

Does "Couldn't fetch" always mean something is broken?

Not always. It can be a temporary state, so if the file loads correctly in a browser and from a terminal, resubmit it and check back later before changing anything else.

Will my site still be indexed?

Yes. Google does not need a sitemap to find pages that are linked from elsewhere. You only lose the sitemap's help with discovery and its error reporting.

What if the file loads for me but not for Google?

Suspect a rule that treats crawlers differently from people, such as bot protection, geo blocking or rate limits. Your server or CDN logs will show what Googlebot received.

To see how your site looks from the outside, Try the free website sample.