“Couldn’t fetch” means Google didn’t retrieve the sitemap file on its last attempt. Google lists five reasons: robots.txt blocks it, the site has a manual action, the URL is wrong, a server or network error, or low crawl demand. Check them in that order: open the sitemap URL yourself, confirm it is in the right property, run a Live test in URL Inspection, and look for a firewall or redirect in the way. If the live test fetches the file and nothing is blocked, the likely explanation is that Google simply hasn’t prioritized it yet; Google’s John Mueller said in October 2026 that this is often about crawl demand and site quality, not the XML.
Why Search Console says “Couldn’t fetch”
The Sitemaps report shows one status per submitted sitemap: Success, Has errors, or Couldn’t fetch. The last one means Google couldn’t retrieve the file at all, so it never got as far as reading the URLs inside. Google’s help page lists the reasons: the sitemap is blocked by robots.txt, the site has an unresolved manual action (“Sitemaps are not read” while it lasts), the URL is wrong and returns a 404, a general error such as the server being unavailable, or “low crawl demand for the sitemap.” The same page says Google keeps trying for a few days after a failed fetch and then stops, so a fix needs a resubmit.
The last reason is the one that confuses most people, because everything looks fine. In episode 114 of Google’s Search Off the Record podcast, published October 1, 2026, Martin Splitt asked why a valid, public sitemap linked from robots.txt still shows the status. John Mueller answered: “We actually see this a lot in the forums.” He gave two reasons, both about how much Google wants to crawl: host load, where “we don’t have any time to crawl this sitemap file because we’re too busy with other things,” and crawl demand, which “is very often based on the perceived quality of a website.” His summary: “So it’s not purely a technical thing.” You can read it in the episode transcript.
Owners keep running into this. A Vercel Community thread from October 2026 describes a sitemap returning 200 with valid XML and 57 URLs, passing Google’s live inspection, yet showing “Could not fetch” and zero discovered URLs for a week; the cause was still unconfirmed (community report). A Shopify Community thread from February 2025 has the same pattern: Shopify reports no errors, Search Console says it can’t fetch. So the job is to rule out the causes you can fix, then decide whether you are waiting on Google.
| What you see | Likely cause | Fix (step n) |
|---|---|---|
| The sitemap URL shows a 404 or a home page in your browser | Wrong address or the file isn’t generated | Find the real sitemap URL and submit that (step 1) |
| The sitemap is missing from the report or shows in another property | Submitted in the wrong property (http, www) | Submit it in the property that matches the URL (step 2) |
| Live test says Crawl allowed: No | robots.txt blocks the sitemap path | Remove the blocking rule (step 3) |
| Live test fails, the page opens fine in a browser | Firewall, bot protection or redirect in the way | Let Googlebot through and submit the final URL (step 4) |
| Manual action listed in Search Console | Sitemaps aren’t read during a manual action | Fix the issue and request review (step 5) |
| Live test fetches it, nothing blocked, still “Couldn’t fetch” | Pending, host load or low crawl demand | Resubmit once, keep it in robots.txt and wait (steps 6 and 7) |
Before you change anything
- Copy the exact URL you submitted. The report shows it in the Sitemap column. Google says redirects are not followed for this URL, so a sitemap submitted as http, or without www, can fail even though the browser lands on the right file.
- Check whether your pages are indexed anyway. Google finds pages through links too. If the Pages report shows your important pages indexed, the sitemap status is a nuisance, not an emergency.
- Know your platform. Google’s help page says hosts such as Squarespace and Wix manage the sitemap for you, and that a site of about 500 pages or fewer, with every page reachable by links, probably doesn’t need one at all.
- Don’t delete and resubmit every day. Repeated resubmits don’t change how Google schedules the fetch, and they make it harder to tell when something actually changed.
- Write down what you change. One change at a time, with the date, so you know which one worked.
How to fix it, step by step
Step 1: Open the sitemap URL yourself
Paste the submitted URL into a private browser window. You should see XML (or plain text for a .txt sitemap), not a 404 page, a login page or your home page. WordPress SEO plugins usually publish an index such as sitemap_index.xml rather than sitemap.xml, and Shopify generates /sitemap.xml automatically. If the file lists other sitemaps, open one or two of those as well. Google’s guide to building a sitemap sets the limits: UTF-8, absolute URLs, at most 50,000 URLs or 50MB uncompressed per file, ideally at the site root.
Step 2: Submit it in the right property
The Sitemaps report only shows sitemaps submitted in that property, and Google’s page warns about mixing up http and https or www and non-www. With a Domain property you are covered for every version. With a URL-prefix property, the sitemap URL must start with exactly that prefix. Submit the final address, the one that loads without a redirect.
Step 3: Run a Live test in URL Inspection
Google’s own debugging steps: copy the sitemap URL from the report, paste it into the URL Inspection box, click Live test and expand Page availability. You want Crawl allowed? = Yes and Page fetch = Successful. Ignore the “not on Google” verdict; a sitemap isn’t a page and isn’t meant to be indexed. A Product Expert in a 2019 Search Central Community thread gave the same advice and added: don’t click Request indexing on a sitemap (community answer). If Crawl allowed says No, open yourdomain.com/robots.txt and remove the Disallow rule that matches the sitemap path.
Step 4: Look for a firewall, challenge or redirect
If the live test fails while the file opens in your browser, something is treating Googlebot differently from you. Common suspects on small business sites are a security plugin, a CDN bot-protection or “under attack” mode, a geo-block, a rate limit or a redirect that only some visitors get. Check the firewall or CDN logs for requests to the sitemap path and their response code. A bot challenge page returns HTML, which can look like a working page to a person and like a broken sitemap to Google (our inference, not a documented Google case). Turn the rule off for verified search engine crawlers, then test again.
Step 5: Rule out a manual action
Open Security and Manual actions, then Manual actions, in Search Console. Google’s Sitemaps help says sitemaps are not read while a manual action is unresolved. If there is one, the sitemap is the least of the problems: fix what the notice describes and request a review first.
Step 6: Check the file for parse errors
A file Google can fetch but not read shows as Has errors, not Couldn’t fetch, but it is worth one check while you are here. The help page lists the usual parse errors: dates not in W3C format, unescaped ampersands in URLs, URLs on another host or protocol than the sitemap, and a sitemap index that lists another index. Fix those, then resubmit once.
Step 7: Make the sitemap easy to find, then wait
Add a line such as “Sitemap: https://www.example.com/sitemap.xml” to robots.txt, which Google’s build guide lists as a second way to point to it. Then leave it. Google says submitting a sitemap “is merely a hint” and that it doesn’t guarantee a download. If the live test succeeds and nothing blocks Googlebot, the likely explanation is the one Mueller gave: Google hasn’t found the time or the need yet. Some owners rename the file or submit a .txt copy to force a fresh fetch; the Vercel thread above tried both without success, so treat it as optional.
Step 8: Work on the reason Google might not care
If the status stays for weeks and your new pages aren’t being found either, crawl demand is the thing to work on. Mueller tied it to “the perceived quality of a website” and said Google will come back to the sitemap if the quality “improves significantly” over time. In practice that means fewer thin or duplicate pages, stronger pages for your main services, and links to new pages from pages Google already indexed. The crawled, currently not indexed guide walks through that work.
What these steps can’t do
- They can’t make Google fetch the sitemap on demand. Submitting it is a hint, and Google decides when to read it.
- They can’t turn a sitemap into rankings. Google says a URL listed in a sitemap is no guarantee it will be crawled or indexed.
- They won’t erase what Google already knows. The help page says a later failure doesn’t make Google forget earlier successful reads, so a temporary error is not a reset.
- They won’t explain a platform-wide problem. If many sites on the same host report the status at once, as in the Vercel thread, the fix may sit with the host.
Also keep the lastmod dates honest. Mueller said Google uses them when the dates in a file look reasonable and otherwise falls back on the URLs themselves, so a generator that stamps every page with today’s date throws away a useful signal.
Our SEO service starts with a technical audit that checks the sitemap, robots.txt, redirects and firewall rules against what Googlebot actually receives. You can also send your site for a free website audit or contact us with a screenshot of the Sitemaps report.
Frequently asked questions
What does “Couldn’t fetch” mean for a sitemap?
Google couldn’t retrieve the sitemap file on its last attempt, so it didn’t read the URLs inside. Google lists the causes as a robots.txt block, a manual action, a wrong URL, a server or network error, or low crawl demand for the sitemap.
My sitemap opens in the browser. Why can’t Google fetch it?
Run a Live test on the sitemap URL in URL Inspection. If it fails, something such as a firewall, bot protection or a redirect treats Googlebot differently. If it succeeds and nothing is blocked, Google may simply not have fetched it yet; Google’s John Mueller said this often comes down to host load or crawl demand.
Should I click Request indexing on my sitemap?
No. A sitemap is not a page and isn’t meant to be indexed. Use the Live test only to confirm Google can fetch it, then resubmit it once in the Sitemaps report.
Do I even need a sitemap for a small website?
Google’s help page says a site of about 500 pages or fewer, with every page reachable by links from the home page, probably doesn’t need one. Most systems generate one anyway, and Mueller recommends keeping it turned on, so fix the status if it is easy and don’t worry if your pages are indexed.
How long until the status changes?
Google doesn’t give a timeline. It retries a failed fetch for a few days before stopping, so resubmit after a fix and check again after a week. If the live test passes and the status stays, work on the site’s content and internal links rather than the file.
Sources
- Google Search Console Help: Sitemaps report (fetch and parsing errors)
- Google Search Central: Build and submit a sitemap
- Google Search Central podcast, Search Off the Record ep. 114: Do sitemaps still matter? (transcript, Oct 1, 2026)
- Vercel Community (community): Search Console cannot fetch sitemap despite HTTP 200 (Oct 2026)
- Shopify Community (community): Google will not fetch my sitemap (Feb 2025)
- Google Search Central Community (community): Sitemap could not be read (2019)