What do sitemap errors in Google Search Console mean and how do I fix them?
Sitemap errors in Google Search Console mean either that Google could not download the file at all (Couldn't fetch, shown on the details page as Sitemap could not be read) or that it downloaded it but could not parse part of it (Has errors). Fetch failures usually come from a wrong URL, a robots.txt rule, a server error or a firewall answering Googlebot; parsing errors come from broken XML, bad dates, wrong URLs or files over 50,000 URLs or 50 MB. Test the sitemap URL from outside with curl, fix the cause, then resubmit.
The Sitemaps report in Search Console is short on words: a status, a count and sometimes an error name. Behind each status is a specific failure that you can reproduce from your own terminal in a minute. This guide maps each message Google documents to its cause, shows how to test it from outside, and lists the fix.
On this page
- What do the sitemap statuses in Search Console mean?
- Why does Search Console say Couldn't fetch or Sitemap could not be read?
- How do I test a sitemap from outside?
- What do the Has errors messages mean and how do I fix them?
- What are the sitemap size limits and format rules?
- Do AI crawlers use sitemaps too?
What do the sitemap statuses in Search Console mean?
Each sitemap you submit gets one status, for the last time Google requested it:
- Success: the sitemap was fetched and processed without errors, and all its URLs are queued for crawling.
- Has errors (also shown as Sitemap had X errors): the file was fetched, but parts of it could not be parsed. URLs that parsed correctly are still queued.
- Couldn't fetch: Google could not retrieve the file itself. When you open the sitemap, the details page says Sitemap could not be read. In French Search Console the same message reads Impossible de lire le sitemap, and the top-level status reads Impossible de récupérer le sitemap.
If a fetch or parse fails, Google keeps trying for a few days and then stops requesting that sitemap, so a broken sitemap does not fix itself. Two more details explain many confusing reports: the report only lists sitemaps submitted through the report or the API, not ones found in robots.txt, and it only shows sitemaps for the current property, so check that you are in the right http or https and www or non-www property.
Why does Search Console say Couldn't fetch or Sitemap could not be read?
Google lists these documented causes for a fetch failure:
- The sitemap is blocked by robots.txt. Google respects robots.txt when fetching sitemaps, so a rule such as
Disallow: /sitemapstops it. - The URL is wrong and returns 404. A different path, a missing
www, orhttpinstead ofhttpsare the usual mistakes. - A general error such as the server being unavailable. Some of these are temporary.
- The site has an unresolved manual action. Sitemaps are not read until it is fixed.
- Low crawl demand for the sitemap.
One cause Google does not name separately shows up as a general or HTTP error: a firewall, CDN or bot protection that answers Googlebot with a 403, a 429 or a challenge page while your browser gets the file. A login requirement in front of the file does the same. To confirm the failure from Google's side, paste the sitemap URL into the URL Inspection tool, run a live test and check that Crawl allowed is Yes and Page fetch is Successful.
How do I test a sitemap from outside?
Run these four checks from any machine. Replace example.com with your domain.
# 1. Status, redirects and content type
curl -sIL https://example.com/sitemap.xml | grep -iE '^(HTTP|location|content-type)'
# 2. The same file requested with Googlebot's user agent
curl -s -o /dev/null -w "%{http_code} %{content_type} %{size_download}\n" \
-A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \
https://example.com/sitemap.xml
# 3. Rules and Sitemap lines in robots.txt
curl -s https://example.com/robots.txt | grep -iE '^(user-agent|disallow|allow|sitemap)'
# 4. Well-formed XML and number of URLs
curl -s https://example.com/sitemap.xml -o sitemap.xml
xmllint --noout sitemap.xml && grep -o '<loc>' sitemap.xml | wc -l What to look for: the final status must be 200. A chain of redirects means you submitted an address that is not the final one; Search Console shows the exact URL you submitted and does not follow redirects for it, so submit the final URL. A content type of text/html together with an HTML body means the server sent a page, often a 404 page or the home page, instead of the file. If check 2 returns 403, 429 or 503 while check 1 returns 200, a firewall rule is treating crawlers differently. Some servers answer HEAD requests differently from GET, which is why check 2 uses a normal request.
Your test comes from your own IP address, so it shows how your rules treat the user agent. Rules based on IP ranges can still treat the real Googlebot differently. Google publishes its crawler IP ranges and supports reverse DNS verification, so an allow rule can match the real crawler instead of the user agent string.
What do the Has errors messages mean and how do I fix them?
When the file is fetched but cannot be fully parsed, the details page names the error. The ones you are most likely to see:
- Parsing error: the XML could not be parsed, often because of an unescaped character in a URL. Write
&as&, and escape',",<and>as well. - Unsupported format: the header or namespace is wrong. A sitemap must start with the XML declaration and use the namespace
http://www.sitemaps.org/schemas/sitemap/0.9, with straight quotes. - Invalid date:
lastmodmust use W3C Datetime, such as2026-11-17or2026-11-17T09:30:00+00:00. If you include a time, include a time zone. - URL not allowed: listed URLs are above the sitemap's folder or on another domain or protocol. Path mismatch is the same problem with
www: the sitemap and its URLs must agree. - Too many URLs or Sitemap file size error: more than 50,000 URLs or more than 50 MB uncompressed. Split the file and list the parts in a sitemap index.
- Compression error: the gzip file is damaged. Recompress it, upload it and resubmit.
- Empty sitemap: the file contains no URLs. Check the generator that writes it.
- Leading whitespace: only a warning. Remove anything before the XML declaration.
- URLs not followed or URLs not accessible: the file is fine, but listed URLs redirect too often or cannot be crawled. List only final, absolute URLs.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/products?color=blue&size=m</loc>
<lastmod>2026-11-17</lastmod>
</url>
<url>
<loc>https://example.com/about</loc>
<lastmod>2026-11-10T09:30:00+00:00</lastmod>
</url>
</urlset> What are the sitemap size limits and format rules?
The sitemaps.org protocol and Google's documentation set the same limits: no more than 50,000 URLs and no more than 50 MB uncompressed per sitemap file. A sitemap index may list up to 50,000 sitemaps and has the same size limit, and Google reports Too many sitemaps when an index exceeds it. Indexes cannot point to other indexes. The file must be UTF-8 encoded, every value must be entity-escaped, and Google asks for fully qualified, absolute URLs.
Google also says it ignores priority and changefreq, and uses lastmod only when it is consistently and verifiably accurate, so set it to the date the content last changed in a meaningful way. Under the sitemaps.org protocol, a sitemap at https://example.com/blog/sitemap.xml may only list URLs under /blog/, which is why Google recommends placing sitemaps at the site root. A large site splits its URLs into several files and submits one index:
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.com/sitemap-pages.xml</loc>
<lastmod>2026-11-17</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/sitemap-blog.xml.gz</loc>
<lastmod>2026-11-15</lastmod>
</sitemap>
</sitemapindex> Also add one line with the full URL to robots.txt, for example Sitemap: https://example.com/sitemap.xml. It can go anywhere in the file, and any crawler that reads robots.txt can find your sitemap from it, not only the ones you submit to.
Do AI crawlers use sitemaps too?
For Google, indirectly yes. Sitemaps help Google discover URLs for its Search index, and Google says its AI Overviews and AI Mode draw on that index: a page must be indexed and eligible for a snippet to appear as a supporting link. A sitemap error that slows indexing can therefore also delay a page's appearance in Google's AI features.
For other answer engines, it is not documented. The crawler documentation of OpenAI, Anthropic and Perplexity does not say whether their crawlers read sitemaps, so do not count on a sitemap to get a page into ChatGPT, Claude or Perplexity. Internal links and an open robots.txt and firewall matter more there. Keeping a working sitemap and a Sitemap: line in robots.txt costs nothing and serves any crawler that does use them.
The full AISeeWhy report reads the sitemaps declared in robots.txt or found at /sitemap.xml and flags a sitemap that cannot be fetched or cannot be parsed, with a fix guide for each case: sitemap unreachable and sitemap unreadable.
Fixes for this problem
- Broken links in llms.txt: 2
- No sitemap found
- Sitemap cannot be fetched (status 403)
- Sitemap cannot be read
Next steps
- robots.txt tester and checker for AI crawlers
- AI crawler IP check
- See an example full report
- AI crawler monitoring
- Plans and prices
Crawlers in this article
Frequently asked questions
What does Impossible de lire le sitemap mean?
It is the French Search Console text for Sitemap could not be read. It appears on the details page when Google could not fetch the file at all. Check the URL, robots.txt, the server's status code and your firewall, fix the cause and resubmit.
How long after a fix will Google re-read my sitemap?
Google says it tries to crawl a sitemap as soon as you submit it, so resubmit after the fix. After a successful read, it recrawls the sitemap on its own schedule, independent of the rest of the site.
Why is my sitemap not listed in the Sitemaps report?
The report shows only sitemaps submitted through the report or the API, and only for the current property. A sitemap found through robots.txt can be used by Google without appearing there. Submit it to see its status.
Does a sitemap error remove my pages from Google?
Not by itself. Google says it remembers what it learned from earlier successful reads, and a later failure does not make it forget. New and changed pages may be found more slowly until the sitemap works again.
Will deleting and resubmitting the sitemap clear the error?
Only if the cause is fixed. Removing a sitemap from the report does not make Google forget it or its URLs, and a resubmitted sitemap that still fails gets the same error.
Sources
- Google Search Console Help: Sitemaps report
- Google Search Console Help: Rapport sur les sitemaps (French)
- Google Search Central: Build and submit a sitemap
- Sitemaps.org: Sitemaps XML format
- Google: Verify requests from Google crawlers and fetchers
- Google: Google's common crawlers
- Google Search Central: AI features and your website
- OpenAI: Overview of OpenAI crawlers
- Anthropic: Does Anthropic crawl data from the web, and how can site owners block the crawler?
- Perplexity: Perplexity crawlers