- 'Couldn't fetch' means Google could not download or read the sitemap file, so it cannot use the URLs inside it.
- For a brand-new submission it often just means Google has not fetched the file yet: wait a few days before changing anything.
- The most common real causes are a wrong URL, a 404 or 5xx, a robots.txt block, a redirect, or bot protection stopping Googlebot.
- Test the exact sitemap URL in a browser and with the free sitemap validator, then resubmit in Search Console.
- Add a Sitemap: line to robots.txt so Google can find the file even when a submission fails.
What does 'Couldn't fetch' mean?
'Couldn't fetch' (also shown as 'Sitemap could not be read') means Google could not download or read your sitemap file. Google tried to request the sitemap URL and did not get a valid sitemap back, so it cannot use the URLs inside it. For a brand-new submission it often just means Google has not fetched the file yet. Google's Sitemaps report help explains the status and the errors behind it, and its build-a-sitemap doc covers the format Google expects.
The status is about the sitemap file, not about every page in it. A sitemap can be fetched and still contain URLs that are not indexed. If the file is fine but a page is missing, check that page's crawl and indexing status instead. Our XML sitemap guide covers the format, limits and submission in more detail.
Why does Search Console say my sitemap couldn't be fetched?
Google could not get a valid sitemap from the URL you submitted, and the cause is usually one of the items in the table below. Work down the list from the most common to the least common.
Causes of 'Couldn't fetch' and how to fix each one
| Cause | Fix |
|---|---|
| Wrong URL or typo | Copy the exact public sitemap URL from a browser and submit that, including the correct domain and file name. |
| 404 or 5xx on the sitemap URL | Make the file return 200. Fix the route or server error, or restore the file at the submitted address. |
| robots.txt blocking the sitemap | Remove any rule that blocks the sitemap path, then resubmit. Test it with the robots.txt tester. |
| Sitemap URL redirects | Submit the final URL that returns 200 directly, not a URL that redirects to it. |
| Sitemap on a different host than the property | Submit a sitemap on the same host as the verified property, or verify the host that serves the sitemap. |
| Login, firewall or CDN bot protection blocking Googlebot | Allow verified Googlebot through the login, WAF and CDN rules so the file is publicly reachable. |
| Invalid XML or HTML served instead of XML | Serve valid XML with the correct content type. A login page or error page returned as HTML is not a sitemap. |
| gzip or encoding problems | Serve a valid gzip file or plain XML with correct encoding, and check the file opens cleanly after decompression. |
| File over 50 MB or 50,000 URLs | Split the file into smaller sitemaps and list them in a sitemap index. |
| A newly submitted sitemap not processed yet | Wait a few days. New submissions can show 'Couldn't fetch' before Google has fetched the file. |
How do I fix it step by step?
Test the exact sitemap URL, fix whatever stops Google from reading it, then resubmit and wait.
-
Open the sitemap URL in a browser
Paste the exact URL you submitted into a browser. You should see XML, not a login page, an error page or a redirect to another address. If you see HTML, the server is not serving a sitemap.
-
Check the response with the free tools
Run the URL through the free sitemap validator to check the XML and limits, and the indexability checker to see the HTTP status and any redirects.
-
Check robots.txt
Open
/robots.txtand confirm no rule blocks the sitemap path. Test the exact path with the robots.txt tester. Our robots.txt guide explains the syntax. -
Add a Sitemap: line to robots.txt
Add the absolute sitemap address outside the crawler groups, for example
Sitemap: https://example.com/sitemap.xml. This gives Google a second way to find the file. -
Resubmit in Search Console and wait
Open the Sitemaps report, remove the failing entry if needed, and submit the final URL again. Then wait. Google recrawls sitemaps on its own schedule, and a new submission can take days to process.
Is 'Couldn't fetch' always a real error?
No. A newly submitted sitemap can show 'Couldn't fetch' for days before Google has fetched it. If the URL opens in a browser, returns 200, is valid XML and is not blocked by robots.txt, the status is often just a timing issue. Give it a few days and check the report again before you change anything. Only treat it as a real error when the file itself is unreachable, returns an error, redirects, or is not valid XML.
How do I submit a sitemap to Bing?
Bing has its own index, so submit the same sitemap in Bing Webmaster Tools as well. Verify the site, open Sitemaps and submit the public sitemap or index URL. Bing also reads the Sitemap: line in robots.txt. For faster discovery of new and changed URLs, use IndexNow alongside the sitemap. Our Bing Webmaster Tools guide covers verification and the reports.
Check the sitemap before you resubmitValidate the XML, limits and URL responses for any sitemap in one run, free.
Check a sitemapQuestions and answers
Sitemap couldn't fetch questions
What does 'Couldn't fetch' mean for a sitemap in Google Search Console?
It means Google could not download or read the sitemap file, so it cannot use the URLs inside it. For a brand-new submission it often just means Google has not fetched the file yet. Check that the URL opens in a browser, returns 200 and is valid XML before you change anything.
Why does Search Console say 'Sitemap could not be read'?
'Sitemap could not be read' is the same problem as 'Couldn't fetch': Google could not get a valid sitemap from the URL. The usual causes are a wrong URL, a 404 or 5xx, a robots.txt block, a redirect, bot protection blocking Googlebot, or invalid XML.
How long does it take Google to fetch a new sitemap?
A newly submitted sitemap can show 'Couldn't fetch' for days before Google fetches it. If the file is reachable, returns 200 and is valid XML, wait a few days and check the Sitemaps report again rather than resubmitting repeatedly.
Should I add my sitemap to robots.txt?
Yes. Add a Sitemap: line with the absolute sitemap address outside the crawler groups. It gives Google a second way to find the file and does not replace submitting it in Search Console.
How do I submit a sitemap to Bing?
Verify the site in Bing Webmaster Tools, open Sitemaps and submit the same public sitemap or index URL. Bing also reads the Sitemap: line in robots.txt. Use IndexNow alongside the sitemap to notify Bing about new and changed URLs.
Sources
- Sitemaps report — Search Console Help, on the Sitemaps report, statuses and fetch errors
- Build and submit a sitemap — Google Search Central, on sitemap format, limits and submission
