Lees deze gids in het Nederlands →
“Sitemap could not be read” (or “Couldn’t fetch”) means Google tried to load your sitemap and failed — wrong URL, a block, broken XML, or simply a brand-new submission that has not been processed yet.
- First check: open the sitemap URL yourself in a private window. Loads fine → usually wait; fails → fix URL, block or XML.
- The classic mistake is submitting /sitemap.xml out of habit while your plugin serves /sitemap_index.xml.
- On brand-new sites “Couldn’t fetch” often flips to “Success” by itself within days — ours did within minutes.
- Limits: 50,000 URLs or 50 MB uncompressed per sitemap; beyond that, split and use a sitemap index.
- A sitemap is a discovery aid, not an indexing switch: well-linked pages get found even while it misbehaves.
“Sitemap could not be read” or “Couldn’t fetch” means Google tried to load your sitemap and failed — it got an error, was blocked, or couldn’t parse the file.
First open the sitemap URL in your browser. If it loads as clean XML, the cause is usually Google’s side or a new submission still pending — give it a few days. If it doesn’t load, fix the URL, the blocking rule or the XML error below.
The 2-minute first check
- Is it the exact URL you submitted?
- Test it with URL Inspection → Test live URL.
- New submission? Wait a few days, then resubmit once.
- 404? You submitted the wrong URL.
- Login, firewall or challenge page? Googlebot is blocked.
- Garbled or blank? The XML is broken.
| Symptom in the browser | Likely cause | Fix |
|---|---|---|
| 404 | Wrong sitemap URL submitted | Submit the URL your plugin generates |
| Login/challenge page | Firewall or bot protection blocks Googlebot | Whitelist verified search bots |
| Blank or garbled output | Broken XML, output before <?xml, cache plugin | Validate XML; exclude sitemap from caching |
| Loads perfectly | New submission or Google-side delay | Wait a few days, resubmit once |
The real causes
- Wrong URL. WordPress with Yoast uses /sitemap_index.xml; WordPress core uses /wp-sitemap.xml; Rank Math uses /sitemap_index.xml. Submitting /sitemap.xml by habit is the classic mistake.
- Blocked for Googlebot. A robots.txt rule, a security plugin, a firewall or bot-protection challenge that lets you in but not Google.
- Broken XML. Blank lines or PHP warnings before the <?xml declaration, unescaped ampersands, or a caching plugin serving a minified HTML version.
- Too big. A single sitemap may hold at most 50,000 URLs or 50 MB uncompressed. Split larger ones and use a sitemap index.
- Server errors or timeouts while Google fetched it — slow hosting, rate limiting, 5xx responses.
- A brand-new submission. On new sites the report often shows “Couldn’t fetch” for a while even when the file is fine. Many site owners see it flip to “Success” on its own.
Fixes that work
- Submit the exact URL your plugin generates, and delete stale submissions of old sitemap URLs.
- Exclude sitemaps from caching and minification, and whitelist Googlebot in your security or firewall settings.
- Validate the XML with any online XML sitemap validator; fix anything before the opening <?xml line.
- List the sitemap in robots.txt with a Sitemap: line, so every crawler — including Bing — finds it.
- Resubmit once after fixing. Repeated resubmits don’t speed anything up.
A sitemap is a discovery aid, not an indexing switch. Pages that are well linked internally get found even while the sitemap is misbehaving. If pages are found but still not indexed, the problem lies elsewhere — start with Crawled vs. Discovered.
Before you panic about “Couldn’t fetch,” open the URL yourself. If it loads cleanly for a logged-out visitor, you’re mostly waiting on Google. If it doesn’t, the fix is almost always one of the five causes above.
FAQ
Why does Search Console say “Couldn’t fetch” when my sitemap works?
On new submissions this status often appears temporarily. If the file loads for logged-out visitors and passes a live test, wait a few days. If it persists, check firewall or bot-protection rules that might treat Googlebot differently.
Does a sitemap error stop my site from being indexed?
No. Google also discovers pages through links. A working sitemap helps discovery, especially on new or large sites, but it isn’t required for indexing.
How many URLs can one sitemap contain?
Up to 50,000 URLs or 50 MB uncompressed. For more, split into several sitemaps and submit a sitemap index file.
Should I submit my sitemap to Bing too?
Yes. Submit it in Bing Webmaster Tools and add the Sitemap line to robots.txt. For instant updates on Bing, also use IndexNow.
Should sitemaps be in robots.txt?
Yes. Add a Sitemap: line with the full URL. Every major crawler, including Bing, reads it from there even without a manual submission.
Can I submit more than one sitemap?
Yes. You can submit several sitemaps or one sitemap index that references them all; Search Console lists each with its own status.