In short
"Couldn't fetch" means Googlebot could not retrieve a valid sitemap at the URL you submitted. The usual causes, in order: the URL is wrong or redirects; robots.txt or a firewall blocks Googlebot; the file is not valid XML or exceeds 50,000 URLs or 50 MB; the server returned an error or was slow; or Search Console simply has not fetched it yet and is showing the status prematurely, which resolves on its own within a day or two. Check the URL in a browser and with URL Inspection first; most cases are fixed there.
What the status means
When you submit a sitemap in Search Console, Google queues a fetch of that URL. "Success" means it retrieved a valid sitemap and read the URLs. "Has errors" means it retrieved a file with problems. "Couldn't fetch" means it did not get a usable file at all: the request failed, was blocked, returned something that was not a sitemap, or has not been attempted yet.
That last case matters. Search Console frequently shows "Couldn't fetch" immediately after submission, before any fetch has happened, and updates to "Success" within hours or a couple of days. If the sitemap was submitted today and the URL works in a browser, wait before doing anything else.
Cause 1: the URL is wrong or redirects
Open the exact URL you submitted in a browser. If it 404s, the path is wrong; common mistakes are sitemap.xml versus sitemap_index.xml, a missing trailing path from a plugin, or a sitemap that lives on a subdirectory. If it redirects, for example from http:// to https:// or from www to non-www, submit the final URL instead; Google follows some redirects for sitemaps but is inconsistent about it, and the property must match the sitemap's host exactly. A sitemap submitted to the https://www. property must live on https://www..
Cause 2: something blocks Googlebot
The file loads for you and not for Google. Check robots.txt for a Disallow covering the sitemap's path or the whole site; a staging block left in place is a frequent cause. Check for a firewall, a bot-protection service, or a hosting rule that challenges or refuses unknown user agents; Cloudflare's bot fight mode and similar features sometimes block Googlebot's sitemap fetches. A password on the site or on the sitemap's directory blocks it too.
The definitive test is Search Console's URL Inspection tool on the sitemap URL itself: it fetches as Googlebot and reports whether the request was allowed and what came back.
Cause 3: the file is not a valid sitemap
Google needs well-formed XML in the sitemap protocol, or a plain text list of URLs, served with an appropriate content type. Common failures: a sitemap generated by a broken plugin that outputs HTML or an error page; a byte-order mark or whitespace before the XML declaration; unescaped ampersands in URLs; a gzipped file served without the right headers; a file over 50,000 URLs or 50 MB uncompressed, which must be split and listed in a sitemap index; or a sitemap listing URLs on a different domain than the one it lives on.
View the file's source and run it through an XML validator. If it is a sitemap index, check that each child sitemap also fetches and validates.
Cause 4: the server failed or was slow
A 5xx error, a timeout, or a server that takes too long to generate a large dynamic sitemap all produce the status. Dynamically generated sitemaps on slow hosting are a recurring case: the file works when you open it because you wait, and fails for Googlebot because it does not. Cache the sitemap, generate it on a schedule rather than per request, or pre-build it as a static file.
Cause 5: it has not been fetched yet
As above. If the URL loads, validates, and is not blocked, and the submission is recent, the status is provisional. Resubmitting does not speed it up. Check the "Last read" date in the sitemap report; if it is empty, Google has not tried.
The check in order
- Open the submitted URL in a browser. 404 or redirect: fix the URL. Loads: continue.
- Run URL Inspection on the sitemap URL. Blocked by robots.txt, or fetch failed: fix the block or the server. Fetched: continue.
- View source and validate the XML. Invalid: fix the generator. Valid: continue.
- Check size and URL count; split if over the limits.
- Check the "Last read" date. Empty and recent: wait 48 hours.
After fixing
Resubmit once through the sitemap report, then leave it. Google will refetch on its own schedule, typically within a day for an active site. A sitemap that fetches successfully but lists URLs that are noindexed, redirected or blocked will move to "Has errors" or show discovered-but-excluded pages; those are indexing questions, not sitemap ones.
A sitemap is worth setting up properly, alongside Search Console itself, once and then rarely touching. If yours refuses to fetch after the five checks, book a call and we will look at what Googlebot is actually receiving.
Common questions
How long does 'Couldn't fetch' take to resolve in Search Console?
If the sitemap is valid and reachable, the status usually updates to 'Success' within a few hours to two days of submission, once Google actually fetches it. The status often appears immediately after submitting, before any fetch has occurred. Check the 'Last read' date; if it is empty, Google has not tried yet, and resubmitting does not speed it up.
Why can I open my sitemap but Google cannot fetch it?
Something is treating Googlebot differently from your browser: a robots.txt disallow, a firewall or bot-protection rule challenging unknown user agents, a password, or a server that times out on the slow dynamic generation you waited through. Search Console's URL Inspection on the sitemap URL shows exactly what Googlebot received.
Should I submit sitemap.xml or sitemap_index.xml?
Whichever is the top-level file your site actually serves. Many CMS plugins generate a sitemap index that lists several child sitemaps; submit the index and Google reads the children. Submit the exact final URL on the same host and protocol as the Search Console property, with no redirect.
What makes a sitemap invalid?
Malformed XML, unescaped ampersands in URLs, whitespace or a byte-order mark before the XML declaration, an HTML or error page served in place of the file, a wrong content type, more than 50,000 URLs or 50 MB uncompressed in one file, or URLs on a different domain from the sitemap. Validate the file's source and split large sitemaps into an index.
Does a sitemap error hurt my rankings?
Not directly. A sitemap helps Google discover and prioritise URLs; a failed fetch means Google relies on links and its previous crawl instead, which for a small, well-linked site changes little. It matters more for large or new sites and for pages with few internal links, where the sitemap is the main discovery route.
