Sitemap errors in Search Console, explained

The top-level status describes the latest request, not the history of the sitemap. Expand the row before changing XML. Success means Google fetched and read the file without errors; it does not mean every URL was crawled or indexed. A Has errors status means Google fetched the file but some entries could not be parsed. Couldn't fetch means the file was not retrieved at all. A temporary processing error usually points at Google's side of the pipeline rather than your XML.

A fetch failure means Google could not download the file. Check the exact URL from the report, not a URL you remember. Common causes include a wrong path that returns 404, a robots.txt rule that blocks the sitemap, an unresolved manual action, a server that returns a 5xx error, a login or firewall that rejects Googlebot, and a redirect on the submitted address.

Test the URL in URL Inspection with a live test: crawl allowed should be yes and page fetch should be successful. Then repair the cause. Google retries a failed sitemap for a few days and eventually stops; after fixing the problem, resubmit the sitemap to start a new request. Resubmitting the same broken URL without a fix only repeats the same result.

Search Console can report a temporary processing error when its own systems hit a problem while handling the sitemap; the Sitemaps report may label the same condition Temporary error. The usual advice is to wait; Google generally retries later, and resubmission is only worth trying if the message is still there after several hours. This is not the same as a parse error. If the detail view says the sitemap could not be read, work through the fetch causes above. If it says the sitemap can be read but has errors, fix the named entries or syntax.

This message appears in URL Inspection under Discovery, not as a sitemap failure. It means Google could not identify a sitemap that refers to the inspected page. That can happen because the page is not in a submitted sitemap, the sitemap uses a different version of the URL (http versus https, www versus non-www, a trailing slash), Google has not processed the latest sitemap yet, or the page was discovered through links first. Reporting can also lag behind processing, so the discovery line may not update immediately.

If URL Inspection says the URL is on Google and the sitemap was read after you added the page, this notice is usually safe to ignore. If the page is not indexed, confirm the exact URL appears in the file, check the Sitemaps report, and request indexing only for the pages that matter.

Google ignores priority and changefreq. It may use lastmod when the value is consistently accurate, so do not bump it on every deploy. A successful read only queues discovered URLs; crawling and indexing remain Google's decisions. Use the Page indexing report and URL Inspection to check the URLs themselves.