How to Fix “Sitemap Couldn't Fetch” in Search Console

First: Is It Just New?

A freshly submitted sitemap sometimes shows "Couldn't fetch" even though nothing is wrong, and later changes to "Success". If the file loads correctly in a browser and passes the checks below, wait a few days before changing anything. Resubmitting repeatedly doesn't speed it up.

Check 1: Does the URL Load?

Open the exact URL you submitted in a private browser window:

• 404 Not Found: wrong path or file name. Check for sitemap.xml vs sitemap_index.xml, or a plugin that moved it.
• 403 Forbidden or a login page: the file isn't public.
• Server error (5xx): the server or generator script failed; check hosting logs.
• Redirect: the URL forwards somewhere else. Submit the final URL instead, and make sure it's on the same property.

From a terminal, curl -I shows the status and headers:

curl -I https://example.com/sitemap.xml
# HTTP/2 200
# content-type: application/xml

Check 2: Is It Blocked by robots.txt?

Open https://example.com/robots.txt and look for a Disallow rule that matches the sitemap path, for example Disallow: /*.xml or a blanket Disallow: /. Use Search Console's robots.txt report to see how Google reads the file. Remove or narrow the rule, then resubmit.

Check 3: Is a Firewall or CDN Blocking Google?

Security services can block or challenge automated requests, including Googlebot. Symptoms: the sitemap loads in your browser but Google can't fetch it. Look for:

• Bot-fight or "under attack" modes on your CDN
• Country blocks or rate limits
• Web application firewall rules that challenge XML or unknown user agents
• Hosting-level bot protection

Check your firewall logs for blocked Googlebot requests, and allow verified search engine crawlers. Use Search Console's URL Inspection → Test live URL on the sitemap URL to see what Google receives.

Check 4: Is the XML Valid?

Google expects a well-formed sitemap. Problems that break parsing:

A stray PHP warning or a byte-order mark printed before <?xml is a classic cause on self-hosted sites, because the file looks fine in some browsers but isn't valid XML.

Check 5: Is It on the Right Property?

A sitemap URL must belong to the property you submitted it in. Submitting https://example.com/sitemap.xml to a property for https://www.example.com/ can fail, because those are different URL prefixes. A Domain property avoids this mismatch.

Check 6: Are the URLs Inside Correct?

If Google reads the sitemap but reports errors, look at the URLs: are they on the same host, using the right protocol, and canonical? Listing http:// URLs on an https:// site, or URLs on a different subdomain, causes warnings or ignored entries. XML sitemap best practices covers what belongs in the file.

Rebuilding a Clean Sitemap

If your sitemap is generated by an old plugin or script and keeps breaking, replacing it with a clean, static file can be the quickest fix while you investigate. The XML sitemap generator can crawl your public site, or build from a list of URLs you paste, and produces valid XML with absolute, deduplicated URLs, splitting large lists into multiple files with an index. Upload it to your site root, confirm it loads, and resubmit using the steps in how to submit a sitemap to Google Search Console.

After Fixing

1. Open the sitemap URL in a browser to confirm it loads as XML.
2. Remove the old entry in Search Console if the URL changed, and submit the correct one.
3. Wait for the next fetch. "Last read" updates when Google tries again.

Summary

Confirm the URL returns 200 with valid XML, isn't blocked by robots.txt or a firewall, and belongs to the right property. If everything checks out and the sitemap is new, give Google time to fetch it.