Your XML sitemap is valid. It loads. robots.txt points to it. Yet Google Search Console still says ‘couldn’t fetch.’ Google’s Martin Splitt and John Mueller just unpacked why that happens, and the answer is often not technical.
Three reasons Google skips a sitemap
In a recent discussion, Splitt framed the problem: a sitemap is structured and easy to validate, yet the error still appears for many publishers. Mueller broke the ‘couldn’t fetch’ response into three practical causes.
- Host load. Your server is overwhelmed, or Googlebot has already used its crawl capacity for the site and never gets time to fetch the file.
- Crawl demand. Google’s systems decide they do not need more pages from you right now, so they skip the sitemap. This often reflects perceived site quality.
- The sitemap is not needed. If Google already has what it wants, it will not bother with the file until quality or demand improves.
Mueller said crawl demand is ‘very often based on the perceived quality of a website.’ That is the line to remember. Think of crawl demand as Google’s internal budget for your site. When it drops, Google stops spending time on files it considers low priority, including sitemaps. It is not a penalty, but it is a signal.
Why this matters for marketers
For SEO and growth teams, this changes the diagnostic order. A ‘couldn’t fetch’ error reads like a broken file, but it is often Google telling you the site has not earned enough crawl attention. Fixing the XML will not change that.
Start technical. Check the sitemap returns 200, is linked from robots.txt, and is not blocked. Then dig into server logs and Search Console for 500 responses and crawl spikes. After that, treat it as a quality audit: prune thin pages, consolidate duplicates, and strengthen internal links from your strongest pages.
What to do next
- Confirm the sitemap returns 200 and is linked in robots.txt.
- Review server logs for 500 errors and overnight crawl spikes.
- Cut low-value URLs and improve internal linking before resubmitting.
The frustrating part is that Search Console’s message does not explain any of this. Until Google improves it, treat ‘couldn’t fetch’ as a prompt to check both server health and whether your content deserves Google’s crawl budget.
Source: Search Engine Journal
