Sitemaps Report: Statuses and Errors

By Amit Patel

The Sitemaps report tells you whether Google successfully fetched and parsed your XML sitemap, when it last did so, and how many URLs it discovered from it. It is a small report with an outsized reassurance value: a green “Success” status confirms Google can read your map of the site, while any error means Google may be missing a chunk of your URLs. The key thing to understand is what it does — and does not — promise about indexing.

What the Report Tells You

For each submitted sitemap it shows the type, the last read date, the processing status, and the count of URLs discovered — confirming Google can access and parse the file.

Submit your sitemap here once and Google re-reads it on its own schedule; the “last read” date tells you when. If that date is stale or the status is an error, Google is not getting your latest URLs from the sitemap, which slows discovery of new and updated pages. Pair this with your XML sitemap setup so the file it reads is complete and canonical.

Statuses and What They Mean

“Success” means the sitemap was fetched and parsed cleanly. “Has errors” means it was read but contains problems. “Couldn’t fetch” means Google could not retrieve the file at all — the most urgent status.

“Couldn’t fetch” usually points at a wrong URL, a server error, or a robots.txt rule blocking the sitemap path. “Has errors” means the file loaded but individual entries or formatting failed validation. Only “Success” confirms the whole file processed — and even then, discovery is not indexing.

Common Errors and Fixes

The usual problems: an unreachable sitemap URL, invalid XML, URLs that don’t match the property, oversized files, or entries pointing to non-canonical or redirecting pages.

Keep each sitemap under the 50,000-URL / 50MB limit and split larger sites into a sitemap index. List only canonical, indexable, 200-status URLs — entries that redirect create redirect statuses, and URLs from a different domain or protocol are rejected. Fix the generator so the file is clean, resubmit, and confirm the status returns to Success. Google’s sitemap guidelines specify the exact format and limits.

“Discovered” Is Not “Indexed”

The URL count in this report is how many URLs Google found in the sitemap — not how many it indexed. A sitemap can process perfectly while many of its URLs remain unindexed for quality or duplicate reasons.

This is the most common misreading: people see “500 discovered” and assume 500 indexed. To know what is actually indexed, go to the Page indexing report, which you can filter by sitemap. A healthy sitemap status plus a low indexed count means your indexing problem is about page quality or duplication, not the sitemap — the sitemap is doing its job.

Frequently Asked Questions

The Bottom Line

The Sitemaps report answers one question well: can Google read your sitemap? Keep the status on Success with a clean, canonical file, and then look to the Page indexing report for what actually got indexed. Understanding that boundary — discovery here, indexing there — saves a lot of misdirected effort, and the rest of the Search Console cluster covers both sides.