“Sitemap could not be read” in Google Search Console

What the status means

This comes from the Sitemaps report, not the Pages report. In the list of sitemaps it appears as Couldn't fetch. Click the sitemap, and the details page says Sitemap could not be read. Both mean Google failed to get the file.

Don't confuse it with Has errors, where Google got the file and found problems inside it. Those are listed by name, such as Parsing error or Invalid date, and the fixes are specific.

Google's help says it retries a failed fetch for a few days and then stops, until you fix the problem and resubmit.

Is it a problem?

A sitemap helps Google find your pages, but it isn't required for indexing. Google finds most pages on a small, well-linked site through links. So check two things in Indexing → Pages before you worry:

Check the file first

Open the exact URL you submitted, in a private window, then check it with the tool below. A working sitemap meets all of these:

• It returns status 200 directly, with no login. Redirects aren't a good idea either.
• The content is XML (or plain text for a text sitemap), not an HTML page. A CMS or a single-page app can return its normal page or a “not found” template with status 200 instead of the file.
• The first characters are the XML declaration. A blank line or a PHP warning above it breaks parsing.
• The file isn't blocked. Paste your robots.txt into our robots.txt tester with the sitemap URL.
• It's within limits: 50 MB uncompressed and 50,000 URLs per file. Larger sites split into several files and list them in a sitemap index.

What Google's help lists as causes

When the file is fine, and the status stays

This is the case many site owners run into: the XML validates, the file opens, and the report still says Couldn't fetch.

Google's John Mueller and Martin Splitt discussed this in October 2026, as reported by Search Engine Journal. Mueller named host load, where Google is busy with other things or the server is struggling, and crawl demand: “the crawl demand is very often based on the perceived quality of a website.” He also said that sometimes Google just doesn't want the file.

So a valid file with this status isn't necessarily a sitemap problem. In that case:

1. Rule out the server. Check Crawl stats and your logs for errors or slow responses when Google visits.
2. Add the line to robots.txt: Sitemap: https://example.com/sitemap.xml. It gives Google a second way to find the file.
3. See whether pages get found anyway. If new pages are indexed through internal links, you've lost little.
4. Work on the site itself. If Google shows little demand for the site, internal linking, page quality and links from other sites will do more than resubmitting.

How to fix it by platform

WordPress

• The address depends on the plugin: Yoast uses /sitemap_index.xml, Rank Math uses /sitemap_index.xml too, and WordPress core uses /wp-sitemap.xml. Submit the one that actually works.
• A caching plugin can serve an old or broken copy, so clear the cache. Security plugins sometimes block .xml requests from bots.

Shopify, Wix and Squarespace

• These platforms generate /sitemap.xml automatically, and you can't edit it. Submit that exact address on your primary domain. A sitemap on an old or secondary domain usually redirects.

Next.js and headless sites

• app/sitemap.ts serves /sitemap.xml. Check that the build doesn't fail silently when the CMS is unavailable, and that the middleware doesn't redirect or rewrite the path.
• If the sitemap reads from a CMS, make sure it returns the production URLs and not the CMS hostname.

Cloudflare and firewalls

• Check the security log for the sitemap path. Bot rules can challenge the request, and Google gets a challenge page instead of XML.

Submit it correctly

• Put the file at the site root. Google's help reports URL not allowed when a sitemap lists URLs above its own folder or on another domain or protocol.
• Use absolute URLs inside the file and list only pages you want in Google's results: final URLs, without redirects, 404s or noindex pages.

After fixing

Open Indexing → Sitemaps and submit the URL again. Google's help says you should fix the issue and resubmit. Look at Last read: it's the last time Google fetched the file. A fresh date and a Success status mean the file is being read, and then all URLs are queued for crawling, which doesn't mean they'll be indexed.