Reference guide · search-console · Published 2026-08-15 · 3 min read
Interpreting the Search Console Sitemaps report
Learn to read Google Search Console's Sitemaps report, status meanings, page counts, and how to fix submission errors.
- ·Reading the table
- ·Interpreting statuses
- ·Fixing problems
The Search Console Sitemaps report is a small but dense table that tells you whether Google accepted the sitemaps you submitted and, roughly, how visible each one is. It does not replace the Pages report, and it does not tell you whether pages are ranking. Its value is narrower: confirming your sitemaps are submitted and valid, and surfacing errors that would otherwise silently stop Google from discovering some URLs.
Reading the table
Under Sitemaps, Google lists the sitemaps you submitted together with any sitemaps found in your robots.txt. The columns you need are:
| Column | What it means |
|---|---|
| Sitemap | The URL of the sitemap, and any index it points to |
| Submitted on | When you or a redirect caused Google to process it |
| Status | Whether Google read it successfully |
| Discovered pages | URLs Google saw from this sitemap |
| Errors (old names) | Rows with a "Couldn't fetch" and similar historical statuses |
The key one is Discovered pages: the number of URLs Google actually came across via that sitemap. A mismatch between the expected URL count and the discovered count is your main signal that something is wrong.
Interpreting statuses
The useful status is "Success", meaning Google downloaded and parsed the file. The historical failure statuses include:
- "Couldn't fetch": Google could not download the sitemap at all, often a network, DNS, or access error. Note that a returning "Success" after an earlier "Couldn't fetch" still means the final state is fine.
- The file returns a server error, is unreachable, or has a redirect Google will not follow.
- The general "Error" bucket covers sitemaps Google parsed but judged invalid.
Rather than memorising the labels, focus on the two outcomes: did Google get the file, and did the file contain usable URLs. A sitemap can be "Success" yet feed few discovered pages if it lists very few URLs, is compressed improperly, or the URLs it lists are flagged in the Pages report.
Fixing problems
When a sitemap shows an error or far fewer discovered pages than expected, work through:
- Re-fetch the sitemap with a tool such as
curlto confirm it returns a reachable, valid XML file with the right URLs. - Check the XML validates and that any nested index only references sitemaps, not HTML pages. Confirm the last-modified and priority values follow the sitemap XML rules.
- Confirm the file is truly processed: resubmit it if you changed its contents, because Search Console does not refetch a submitted sitemap endlessly.
- After Google confirms each sitemap is valid, move to the Pages report to see whether the discovered pages actually indexed, since sitemap submission and indexing are separate steps. See indexing basics and how to submit a sitemap for the initial flow.
The Sitemaps report is a health check on your discovery channels, not a ranking report. Read it together with the Pages report, and judge success by whether the pages you care about are both discoverable and indexed.