A sitemap can validate, load in a browser and still show “Couldn’t fetch” in Google Search Console. On the 1 October episode of Search Off the Record, Google’s Search Relations podcast, John Mueller said that status on a working file frequently has nothing to do with the XML.

According to PPC Land’s account of the episode, titled “Do sitemaps still matter?”, Mueller gave two common reasons. Google’s crawlers may be too busy with other work to get to the file, or the site may have low crawl demand, which he said is very often based on how Google perceives the site’s quality. His summary, as reported: “So it’s not purely a technical thing.”

The distinction matters for B2B SaaS companies that rely on organic search for pipeline. A red error in Search Console usually becomes a developer ticket. If the cause is low demand, closing that ticket will not change the status, and the effort belongs with the content Google is deciding whether to crawl.

What does “Couldn’t fetch” mean for a sitemap that works?

Google’s Search Console documentation already allows for it. The Sitemaps report help page lists low crawl demand alongside the familiar technical causes of a “Couldn’t fetch” status: a sitemap blocked by robots.txt, an unresolved manual action, a wrong URL returning a 404, or a general server error. The same page links the two directly, stating that higher-quality site content brings higher crawl demand, and points site owners to Google’s guidance on creating high-quality content as the remedy.

The podcast therefore restates documented behaviour, and no policy has changed. What it adds is emphasis from Google’s own Search Relations team. Mueller said the error comes up often in Google’s help forums, according to PPC Land, and his explanation moves the default diagnosis away from the file.

It also echoes a Reddit reply he gave in February 2026, reported by Search Engine Journal. A site owner’s server logs showed Googlebot retrieving the sitemap with 200 responses while Search Console still flagged an error. Mueller’s answer then was that Google has to want to index more of a site’s content, and will not use the sitemap if it is not convinced there is new and important material there.

One caveat on the wording. Google’s transcript of the episode was not accessible to The Marketing Helm for independent checking, so the quotes above rely on PPC Land’s report. The mechanism itself, low crawl demand as a cause of “Couldn’t fetch”, is confirmed in Google’s documentation.

How can marketing teams tell a technical fault from a demand problem?

Marketing teams should rule out the technical causes first, because they are quick to check and fully within their control. Google’s documentation supports a simple order. Open the exact sitemap URL submitted in Search Console and confirm it returns the file, not a 404, a redirect chain or a login page. Check that robots.txt, firewall rules and CDN bot-management settings are not blocking Googlebot, and read the server logs for Googlebot requests and their response codes. Check the Manual Actions report. Then open the Crawl Stats report, which Google recommends for investigating crawl history and host availability, to see whether visits have been falling.

If all of that is clean and the status persists, the evidence points to demand. Google’s crawling guidance describes sitemaps as suggestions: listing a URL does not oblige Google to crawl it, or to crawl it promptly. The fixes on that side are editorial rather than engineering. Keep the sitemap to canonical URLs that should be indexed. Strip out redirects, duplicates and blocked pages. Strengthen internal linking, and consolidate thin pages that weigh on the site’s overall standing.

Content-led B2B programmes are likely to feel this most. Sites that have published at volume, including programmatic and AI-assisted pages, are judged on quality across the whole domain, not page by page. No public data shows how common quality-linked fetch failures are, or which kinds of site see them most, so the risk is plausible but unmeasured.

Which sitemap features does Google still use?

Google still relies on the core of the format, but on less of it than many CMS defaults suggest. Its documentation states that it ignores the priority and changefreq values. Mueller, according to PPC Land, said priority stopped being useful once sites marked every URL as maximum priority.

The lastmod date is used only when it is consistently and verifiably accurate. Google counts changes to main content, structured data or links as significant, and does not count a refreshed copyright date. Mueller’s reported view was that Google wants to use lastmod, but many sites get it wrong, which makes an automatic “updated today” stamp on every page counterproductive.

The size limits are 50,000 URLs or 50MB uncompressed per file, beyond which a sitemap has to be split. Google’s documentation also says some sites may not need one at all: those of about 500 pages or fewer, comprehensively linked internally, without significant video, image or news content. On the episode, Mueller reportedly said smaller websites probably do not need a sitemap because Google can simply crawl them.

For larger sites, the sitemap remains the clearest way to tell Google which URLs have changed. Whether Google acts on it depends on crawl demand, and Search Console publishes no crawl-demand figure for any site.