You open the Sitemaps report in Google Search Console and the status next to your sitemap is 'Couldn't fetch' in red. Click into it and the details say 'Sitemap could not be read'. Or the error listed for it is 'General HTTP error', or 'HTTP error' with a number.
Google's help puts it plainly: 'Couldn't fetch' means the sitemap could not be fetched for some reason. Google never got the file, so it has not read any of the URLs inside it. That is different from 'Has errors', which means the file was fetched but some of it could not be used. The good news is that the causes are a short, well-defined list, and you can check each one in a few minutes.
Google's Sitemaps report uses three statuses, and the one you see tells you where to look.
- 'Success': the sitemap was loaded and processed with no errors, and its URLs were queued for crawling.
- 'Has errors': the sitemap was fetched but has one or more errors. URLs that could be parsed are still queued. The details page shows 'Sitemap can be read, but has errors' and lists them.
- 'Couldn't fetch': Google couldn't retrieve the file itself. The details page shows 'Sitemap could not be read'.
- Google keeps trying to fetch and process a failed sitemap for a few days before it stops. A status you saw minutes after submitting may change on its own, but check the causes below rather than just waiting.
Step one: test the sitemap URL the way Google sees it
Before guessing, do the test Google itself recommends. It answers most of the questions below in one go.
- Open the exact sitemap URL you submitted in a private or incognito browser window. You should see XML (a list of <loc> addresses), not a normal web page, a login page or an error.
- In Search Console, paste the sitemap URL into the URL Inspection bar at the top and choose 'Test live URL'.
- Check that 'Crawl allowed?' says 'Yes' and 'Page fetch' says 'Successful'. If either one fails, the reason shown there is your cause.
- If both pass but the report still says 'Couldn't fetch', submit the sitemap again in the Sitemaps report and give it a few days.
Cause 1: The sitemap URL is wrong (404)
This is the most common cause on new sites. Google's help lists it directly: the URL provided for the sitemap is wrong, which shows up as an HTTP 404 (not found).
Typical slips are a typo, '/sitemap.xml' when your site actually publishes '/sitemap_index.xml' or '/sitemap-index.xml', or an address on http when the site runs on https, or without 'www' when the site uses it. Find the real address by opening it in a browser, or by looking for a 'Sitemap:' line in yoursite.com/robots.txt. Then submit that exact final address, the one the browser ends up on, in the 'Add a new sitemap' box.
If the address opens your normal HTML sitemap page for visitors rather than an XML file, it is the wrong file. Google's Search Relations team has said an XML sitemap is a file made for crawlers, while an HTML sitemap is for people; submit the XML one.
Cause 2: robots.txt blocks the sitemap
Google respects robots.txt when fetching sitemaps. Google's help lists 'The sitemap is blocked by your robots.txt file' as a fetch error, and the fix is to remove the rule that blocks it. A blanket 'Disallow: /' left over from when the site was being built is the usual culprit, or a rule that blocks a folder the sitemap lives in.
- Open yoursite.com/robots.txt. It must sit at the root of the site.
- Look for 'Disallow' lines that match the sitemap's path, and remove or narrow them.
- While you are there, add a line such as 'Sitemap: https://www.example.com/sitemap.xml'. Google says the sitemap URL in robots.txt must be fully qualified; it won't guess http, https or www variants.
- Check the result in Search Console's robots.txt report, then run the live URL Inspection test again.
Cause 3: Server errors, firewalls and 'General HTTP error'
Google's help says other errors, such as the server being unavailable, can also stop it from retrieving a sitemap, and some of these are temporary. If the server was down for a moment, the next attempt may simply work.
If it keeps happening, something is answering Google with an error instead of the file. 'HTTP error' with a code means a 400-level response; Google's fix is to confirm the URL and resubmit. 'General HTTP error' covers other HTTP errors.
- A security plugin, firewall or bot-protection service is blocking Googlebot or challenging it with a check page. Look at its logs or blocked-requests list.
- The sitemap sits behind a login, a 'coming soon' or maintenance mode, or password protection on a staging site.
- The sitemap is generated on the fly and times out on a large site. Split it into smaller files.
- Your host is having problems. Your server's access logs show what status code Googlebot received.
Cause 4: The file isn't valid, or it's too big
These usually show as 'Has errors' rather than 'Couldn't fetch', but they stop Google using the sitemap all the same. Google's help names each one, so match the wording in your report.
- 'Sitemap file size error' or too many URLs: Google's limit is 50MB uncompressed or 50,000 URLs per sitemap. Split it and list the parts in a sitemap index file.
- 'Parsing error': special characters such as an ampersand in a URL are not escaped. 'Unsupported format' or 'Incorrect namespace': the XML header or namespace is wrong.
- 'Missing XML tag' or 'Invalid XML: too many tags': a required tag is missing or repeated. The error gives a line number to look at.
- 'URL not allowed': URLs in a sitemap must be at or below the sitemap's location, on the same domain and protocol. 'Path mismatch' means 'www' usage differs between the sitemap and its URLs.
- 'Compression error': recompress the file, for example with gzip, upload it and resubmit.
- The file must be UTF-8 encoded and use full, absolute URLs. Google also accepts RSS or Atom feeds and plain .txt files with one URL per line.
Cause 5: A manual action, or low crawl demand
Two less obvious reasons are on Google's list. First, sitemaps are not read when a site has an unresolved manual action. Check the Manual actions report in Search Console, fix the issue and request review, then resubmit the sitemap.
Second, Google lists low crawl demand for the sitemap as a cause. It ties crawl demand to content quality: sites with more useful, original content generally get crawled more. On a brand-new site with a handful of pages, this can simply take time.
Prevent it next time
A sitemap is a hint, not a guarantee. Google says so in its own documentation. Getting it to 'Success' makes sure Google can find your pages; it doesn't make them rank.
- After any redesign, migration or plugin change, open the sitemap URL and run a live URL Inspection test.
- Keep a 'Sitemap:' line in robots.txt pointing at the current sitemap, with the full https address.
- Only list canonical URLs you want in Google, with the same domain, protocol and 'www' as the sitemap.
- When you change the sitemap's address, remove the old one from the report: open its details page, click the more options button and choose 'Remove sitemap'.
- Check the Sitemaps report every few weeks, not only when traffic drops.
If you'd rather not deal with this yourself
The checks above are what to do now, and most sitemap errors are fixed in minutes once you know which one you have. If you want a website where this is handled for you, OneSol builds small-business websites with you on the Max plan ($1 for the first month, then $29/month): your own domain connected, CRM and SEO set up, and we keep it running.