Google Search Console says “Couldn't fetch” for a sitemap

Start with the sitemap row's details in the Sitemaps report. “Couldn't fetch” means Google could not retrieve the sitemap file for its latest reported request. It is different from a sitemap that was fetched but had parsing errors. A sitemap opening in your own browser does not establish that Google's fetch succeeded, and the status alone does not identify the cause.

What should I check first?

1. Open the submitted sitemap row. In Search Console, select the sitemap and expand the latest error details. Record the exact sitemap URL, last request information, and specific error text. Google says the report shows the latest request status and details for submissions through the report or API.
2. Confirm the URL and property. Compare the URL in the report with the sitemap's actual location, including https versus http, hostname, path, and any redirect. Google says the Sitemaps report does not follow redirects for the submitted sitemap URL and only shows sitemaps in the current property; a different scheme or host can mean you are viewing another property.
3. Check whether Google can fetch it now. Copy the sitemap URL from the report details into URL Inspection for the matching property and run a live test. Review “Crawl allowed?” and “Page fetch.” Google’s Sitemaps guidance says the sitemap should be accessible to Googlebot, not blocked by login, and have a successful page fetch. This is a current test; it does not rewrite the prior request shown in the Sitemaps report.
4. Follow the specific failure. If the report names a robots.txt block, remove only the rule that blocks the sitemap if that block is unintended. For a 404, confirm the submitted path exists. For server errors, review the relevant hosting/CDN logs and retry after a transient outage. If the property has an unresolved manual action, Google says sitemaps are not read until it is resolved. Do not guess from a generic “Couldn't fetch” label when the report gives a more specific reason.
5. Separate fetching from parsing. If the status changes to “Sitemap had X errors,” Google fetched and partially read the sitemap. Then follow the listed parsing error, such as malformed XML, unsupported format, or a size limit. Don't troubleshoot individual page indexing as if it caused the sitemap file fetch to fail.
6. Decide whether to wait or resubmit. Google says temporary fetch failures can be retried over the following days. If the live check succeeds and the report has no specific continuing error, keep the exact sitemap submitted and check the report again later rather than repeatedly changing a valid file. If you fixed an actual fetch problem and it still fails, submit a new request after the fix.

Why can the sitemap open for me while Search Console cannot fetch it?

A browser request and Google's crawl are separate observations. Your browser may use a logged-in session or a different network path, while Google’s fetch can be affected by the sitemap URL, robots.txt, a manual action, server availability, or other retrieval errors described in the report. The Search Central Community thread cited below documents one user reporting that the sitemap and robots.txt opened in a browser while Search Console said it could not read the sitemap. The reply is a single case, not proof of a universal delay or diagnosis.

Does “Couldn't fetch” mean my pages are not indexed?

No. It describes the latest sitemap-file fetch status, not the index status of every URL listed in that file. Google's Sitemaps report and Page indexing report answer different questions. A sitemap is one way to tell Google about URLs; it does not guarantee that Google crawls or indexes them. Use URL Inspection for a specific page's indexed data, and use the Page indexing report for site-level status patterns.

What should I include in a support or hosting report?

Record the checked time and timezone, exact sitemap URL and Search Console property, the full Sitemaps report status and expanded error, the live-test “Crawl allowed?” and “Page fetch” values, and whether a redirect or authentication is involved. If asking a host to investigate, give them the request time and sitemap path so they can check relevant access logs. Do not share account credentials or private Search Console exports publicly.

Method and limits

This workflow was checked against Google's Sitemaps report, URL Inspection, and Page indexing documentation on November 3, 2026. It classifies the report's sitemap-file fetch status and uses URL Inspection as a current access check. The cited community thread is one user's report and a reply, included only as a qualitative example. This page does not access Search Console, test any live sitemap, or infer why a particular fetch failed.

For URL-level status observations across dates, use the local Google indexing status log. This guide addresses retrieval of the sitemap file itself.