Why Does Search Console Say It Could Not Fetch My Sitemap?
Troubleshoot a sitemap that Google cannot fetch by checking its exact address, public response, access rules and format before resubmitting.
Part of our guide: What Is an XML Sitemap and Does My Website Need One?
“Couldn’t fetch” in Search Console’s Sitemaps report means Google could not retrieve the submitted sitemap. Start with that file’s exact address and the detailed report, rather than assuming every page on the website has an indexing problem.
A sitemap is a list or index of URLs. Its retrieval, parsing and the indexing of the pages it lists are separate stages.
Confirm the submitted address
Copy the sitemap address from the report and open it while signed out. Check the protocol, hostname, spelling and path.
Do not assume every platform uses the same filename. Some sites expose a sitemap index that points to several smaller files.
Our sitemap guide explains the structure. If you are unsure which property you are viewing, use the Search Console setup guide to confirm the scope.
Read the detailed fetch result
Google’s Sitemaps report documentation distinguishes a fetch failure from errors in a sitemap that was retrieved. It also notes that the submitted sitemap URL is exact and redirects are not followed in this context.
Prefer the actual final sitemap address rather than a guessed address that redirects elsewhere. Record the last attempt and any detailed reason.
A failure that happened during a short outage may differ from a persistent configuration problem. Keep timing in the investigation.
Use a response-check worksheet
Ask the developer or host to help with the technical fields.
| Check | Evidence to record |
|---|---|
| Address | Exact submitted URL and intended current URL |
| Response | Actual HTTP status, not just what the browser displays |
| Content | Sitemap XML, supported feed or text rather than an HTML error page |
| Access | No unintended login, firewall or crawler restriction |
| Robots rules | Sitemap retrieval not accidentally blocked |
| Child files | Every referenced sitemap is available |
| Recent changes | Host move, deployment, plugin update or security rule change |
An attractive error page can still be an error. Equally, a browser download prompt does not necessarily mean a valid XML file is broken.
Separate access from format problems
If the file cannot be reached, resolve that before rewriting its contents. Check hosting availability and any restrictions introduced during a migration.
If the file is reachable but reports parsing errors, inspect the detailed message and the generating system. Ask for a correction at the source rather than manually editing a generated file that will be overwritten next time.
The technical SEO guide provides a broader framework for response and access issues.
Check the listed destinations
Once the sitemap is readable, sample important entries. They should be the intended current URLs, not obsolete redirects, private pages or temporary preview addresses.
A sitemap index can succeed while an individual listed page still has a problem. Conversely, one retired page does not necessarily make the whole sitemap unreadable.
Our indexing guide explains why submission does not guarantee selection. A discovered but not indexed page requires a different investigation from an unavailable sitemap file.
Re-submit after fixing the cause
Record the correction and then use the report’s appropriate submission workflow. Check the subsequent fetch result rather than treating the button press as proof of recovery.
Avoid repeatedly submitting the same broken address. That creates activity without resolving the underlying failure.
Keep the existing sitemap and deployment process understandable to whoever maintains the site. If a plugin or build step generates it, document that dependency.
Prevent the problem at the next release
Add sitemap access to your pre-launch checklist. Check the public file after a host move, URL change or major content-system update.
For a small business, a useful acceptance statement is simple: the correct property can retrieve the intended sitemap, the file is valid, and sampled entries lead to the right public pages.
A working sitemap helps Google discover pages. Useful content, clear internal links and accessible pages still need their own checks.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
