What the status means
The Sitemaps report (Indexing > Sitemaps) shows one of three statuses for each sitemap (Google Sitemaps report help):
| Status | Google's meaning | Urgent? |
|---|---|---|
| Success | Fetched and read with no errors. All URLs are queued for crawling | No |
| Has errors | Fetched, but with one or more errors. URLs that parse fine are still queued | Fix soon |
| Couldn't fetch | Could not be fetched for some reason | Check now |
"Couldn't fetch" does not mean your pages are out of Google. Google also finds pages through links. But a sitemap that never loads cannot help Google find new or updated pages.
Check 1: open the sitemap URL yourself
Click the sitemap in the report and copy the exact URL Google tried. Paste it into a private browser window.
- It loads as XML: go to Check 2.
- 404 page: the URL is wrong. Find the real one (see the table below) and submit that.
- Your homepage or a login page: a redirect or a password wall is in the way.
- Blank page or error: your server or SEO plugin is failing to build it.
Common sitemap URLs by platform:
| Platform | Usual sitemap URL |
|---|---|
| WordPress (core) | /wp-sitemap.xml |
| WordPress with Yoast or Rank Math | /sitemap_index.xml |
| Shopify | /sitemap.xml |
| Wix | /sitemap.xml |
| Squarespace | /sitemap.xml |
| Webflow | /sitemap.xml (after you turn on the auto sitemap) |
Check 2: run the live test in URL Inspection
This is Google's own recommended check (Google):
- Paste the sitemap URL into the URL Inspection bar at the top of Search Console.
- Click Test live URL.
- Open Page availability.
- You want Crawl allowed? = Yes and Page fetch = Successful.
If "Crawl allowed?" says No, robots.txt blocks it (Check 3). If "Page fetch" fails, look at the error: server error, not found, or redirect error.
Check 3: robots.txt and firewalls
Open yoursite.com/robots.txt. Look for a Disallow: rule that matches the sitemap path, like Disallow: /sitemap or Disallow: /*.xml. Remove it.
Then check your security plugin, firewall or CDN. Some bot-protection rules show a challenge page to Googlebot. You see XML, Google sees a block. If the live test fails but the file loads for you, this is the most likely cause. Check that the blocked requests are really from Google with Google's verifying Googlebot guide, then allow them.
Check 4: wrong property or wrong version
A sitemap must belong to the property you submit it in (Google). These do not match:
- Sitemap on
http://but property ishttps:// - Sitemap on
www.but property is the non-www URL-prefix property - Sitemap on a different domain, like an old domain or a staging site
Fix: submit the sitemap in the matching property, or use a Domain property, which covers every protocol and subdomain.
Check 5: the file itself
- Size: at most 50 MB uncompressed and 50,000 URLs per sitemap file. Bigger sites need a sitemap index that lists several sitemaps.
- Format: valid XML with the right namespace. A stray space or PHP warning printed before
<?xmlbreaks the whole file. This is common after a plugin update. - Speed: a sitemap built on the fly for a huge store can time out. Ask your developer or plugin to cache it.
- Redirects: submit the final URL. If /sitemap.xml redirects to /sitemap_index.xml, submit /sitemap_index.xml.
Check 6: the file is fine, but the status stays
Sometimes every test passes and the report still says "Couldn't fetch". Google lists low crawl demand and manual actions among the possible causes (Google). What to do:
- Check Security & Manual Actions > Manual actions. It should say "No issues detected".
- If the live test passes, remove the sitemap from the report and submit it again.
- Wait a few days. A sitemap that was just submitted can show this status until Google gets to it.
- Make sure the
Sitemap:line in robots.txt uses the same full URL.
Worked example (fictional site). brightsmile-dental.com moved from Wix to WordPress and submitted /sitemap.xml. Search Console showed "Couldn't fetch". In a browser, /sitemap.xml redirected to /sitemap_index.xml, the Yoast sitemap. The live test of /sitemap_index.xml passed: crawl allowed, page fetch successful. The team removed the old entry, submitted /sitemap_index.xml, and updated the Sitemap: line in robots.txt. The next morning the report showed Success with 64 discovered pages.After you fix it
- Resubmit in Indexing > Sitemaps. Google rechecks submitted sitemaps on its own, but a resubmit speeds things up after a big change.
- Keep only sitemaps you use. Remove old ones from the report so they do not hide real errors.
- Check the Discovered pages count matches what you expect.
How to use this with an AI assistant
Connect SEOmatic at https://seomatic.ai/mcp and ask: "Use gsc_insights sitemaps on mysite.com and list every sitemap with errors, warnings or a fetch problem. Then run check_site and tell me whether robots.txt or a redirect blocks the sitemap." Sign in with connect_seomatic for the Search Console part; check_site is free.