Guides › Hosting, domain & email › Site down or error screens

Google Search Console Says 'Sitemap Couldn't Fetch': What to Check

You submitted a sitemap and the status says Couldn't fetch. Often it is only a delay, but check these causes.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.

This status often appears just after submitting a sitemap on a new site, and then changes by itself within hours or a couple of days. If it stays, work through the list.

Step 1: Open the sitemap yourself

Visit https://yourdomain.com/sitemap.xml in a private window. You should see an XML list of addresses. A 404, a login page or a redirect loop is the problem.

Step 2: Use the exact address

The sitemap address must match the version Google knows: https or http, and with or without www. Submit the one that really loads.

Step 3: Check that crawlers are allowed

Open https://yourdomain.com/robots.txt. It must not contain Disallow: / for everything. Also check that WordPress's Settings > Reading > Discourage search engines is not ticked.

Step 4: Check security tools

A firewall, CDN rule or security plugin may block Google's crawler. Check the access logs, and allow search engine bots.

Step 5: Check the file

The sitemap must be valid XML, under 50 MB and 50,000 addresses, and list addresses on the same domain.

Step 6: Wait and re-check

Give it a day or two, then look at the Pages report for crawling and indexing details. See our indexing guide.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-21.