Google has explained why Search Console can show "Couldn't fetch" for a sitemap that is valid and reachable. John Mueller and Martin Splitt covered it in the Search Off the Record podcast published on October 1, 2026. The two usual causes are host load and low crawl demand, which Google links to how it perceives the quality of the site.
What we know
- Who and where: John Mueller and Martin Splitt of Google's Search Relations team, in episode 114 of Search Off the Record, "Do sitemaps still matter?", published on October 1, 2026.
- The question: Splitt described a sitemap that validates, is publicly accessible and is linked from robots.txt, yet still gets that status, according to the transcript published by Search Engine Journal.
- First cause, host load: Mueller said Google sometimes has no time to crawl the file because it is busy with other things, and that this is also shown as "Couldn't fetch", according to Search Engine Journal.
- Second cause, crawl demand: if Google's systems see no need to crawl much from a site, they skip the sitemap. Mueller added that crawl demand is very often based on the perceived quality of the site, the same outlet reports.
- Google's own summary: the official episode page says that when the file is valid and accessible, the cause is often host load throttling or low crawl demand linked to perceived site quality.
- It can be reversed: if the site's quality improves significantly over time, Google will go back to using the sitemap, Mueller said according to Search Engine Journal.
- Other points from the official episode page: Google dropped support for the priority and changefreq tags; lastmod only counts when it is reliable; each file can hold up to 50,000 URLs and 50MB uncompressed; and llms.txt does not replace an XML sitemap for search engines.
- What is missing: neither the official summary nor the published statements give numbers or thresholds. It is not known how much load slows crawling or what level of quality makes Google skip a sitemap.
The official episode transcript could not be opened for this article. The statements by Mueller and Splitt come from the transcript published by Search Engine Journal.
What changes and what doesn't
Nothing changes in how Google works, and there is no new guideline. Search Console's help page already lists low crawl demand among the reasons for this status, next to a robots.txt block, an unresolved manual action, a wrong URL and server errors.
What changes is how to read the status. The label is the same for a broken file and for a sitemap Google has decided not to read yet. In Mueller's words, quoted by Search Engine Journal, "it's not purely a technical thing". The outlet criticizes exactly that: the message does not state the real reason.
On its own, the status also does not mean your pages have dropped out of Google. According to the help page, what Google read from a sitemap earlier is not forgotten because of a later failure. If fetching keeps failing, Google retries for a few days and then stops trying.
How to tell if this affects you
- Check the status. Open the Sitemaps report in Search Console. The three possible values are "Success", "Couldn't fetch" and "Sitemap had X errors".
- Rule out the technical causes. Google's help page lists them: robots.txt must not block the file, the URL must exist (open it in your browser) and the site must have no unresolved manual action. Fix whatever fails and resubmit the sitemap.
- Run a live test. Paste the sitemap URL into the URL Inspection tool and click "Live test". Under "Page availability" you want "Crawl allowed?" = "Yes" and "Page fetch" = "Successful".
- Look at the server. Google caps how much it crawls from each server; its documentation calls this the crawl capacity limit. Under Property settings > Crawl stats, "Host status" shows whether Google ran into availability problems. If it did, take that to your hosting provider.
- If the technical side is clean, think about demand. Google's help page puts it this way: the higher the quality of the site's content, the higher the crawl demand. Editing the XML will not fix that. Review duplicate, empty or low-value pages first.
- Keep the file tidy. The episode page recommends listing only canonical URLs, without tracking parameters, and an accurate lastmod. If every page carries today's date, Google may ignore that signal.
- Do not switch it off. The same summary advises keeping the sitemap your CMS generates enabled, even on small sites: it has no downside and helps discovery as the site grows.
Related: How Long Google Takes to Crawl and Index: Its Own Numbers
Sources
- Google, Search Off the Record, episode "Do sitemaps still matter?", October 1, 2026
- Google, Search Console Help, "Sitemaps report"
- Google, "Build and submit a sitemap"
- Google, "Crawl budget management"
- Google, Search Console Help, "Crawl Stats report"
- Search Engine Journal, October 6, 2026
Updates: if Google changes the wording of this status in Search Console or its documentation on this error, it will be added here with a link.