Errors can be temporary
Google notes some fetch errors are transient. If the live test succeeds, wait and check whether the error repeats on later attempts.
Google could not retrieve the sitemap file itself. Common causes are a robots.txt block, a wrong address that returns 404, server errors, or an unresolved manual action.
Google notes some fetch errors are transient. If the live test succeeds, wait and check whether the error repeats on later attempts.
| Check | How to tell | Fix |
|---|---|---|
| Does the sitemap address load? | Open the exact submitted URL in a browser. | Correct the address if it returns 404, then resubmit.[1] |
| Is it blocked by robots.txt? | Check robots.txt for a rule matching the sitemap path. | Remove the rule that blocks it.[1] |
| Can Googlebot fetch it right now? | Run a live test of the sitemap URL in URL Inspection and look for a successful page fetch. | Fix server errors, then resubmit; Google stops retrying after a few days.[1][2] |
| Is there a manual action? | Open the Manual actions report. | Sitemaps are not read while a manual action is unresolved, so resolve it first.[1][3] |
No. A sitemap tells Google which URLs you care about; Google still decides what to crawl and index.[4]
Your website, fully managed — no big upfront cost.
We design, build, host, maintain and keep improving your site for one simple monthly fee.
A one-off custom build you own outright.
A defined scope and a single fixed quote — delivered once, and yours to keep.
Get a free, no-obligation quote for your project. We respond within 24 hours.