Sitemaps Report in Search Console
The Sitemaps report shows which sitemaps you have submitted, when Google last read them and whether they worked. This guide explains every column and status, the size limits, how to submit and remove a sitemap, and how to fix “Couldn’t fetch” and “Has errors”.
- Every column explained
- 3 statuses
- Size limits
- Fix guide
sitemap_index.xml Index Success post-sitemap.xml Sitemap Success page-sitemap.xml Sitemap Success old-sitemap.xml Sitemap Couldn't fetch
Open Search Console, then Indexing, then Sitemaps. Each row shows the sitemap URL, type, submitted date, last read date, status and discovered pages. The statuses are Success, Has errors and Couldn’t fetch. Limits per sitemap are 50 MB uncompressed and 50,000 URLs. A submitted sitemap helps discovery; it does not guarantee indexing.
What the Sitemaps report shows
A sitemap is a file listing the URLs you want Google to know about. The Sitemaps report in Search Console tells you which sitemaps Google has received for a property and how Google processed each one. It is a discovery tool: it tells Google where your pages are, but indexing still depends on quality and other signals.
If Google could read the file
Status, last read date and how many pages it found.
New to sitemaps? Read robots.txt and sitemaps first.
Every column explained
| Column | What it means | Watch for |
|---|---|---|
| Sitemap URL | The address you submitted | Google does not follow redirects here |
| Type | Sitemap or sitemap index | Index files list other sitemaps |
| Submitted | When you submitted it | Not when Google read it |
| Last read | When Google last fetched it | An old date can mean no recent re-read |
| Status | Success, Has errors or Couldn’t fetch | See the next section |
| Discovered pages | URLs Google found in the file | Compare with your real page count |
| Discovered videos | Video entries found, if any | Only for video sitemaps |
The three statuses
| Status | Meaning | What to do |
|---|---|---|
| Success | Google read the file with no problems | Nothing, but still check page counts |
| Has errors | Google read it but found problems; some URLs may be skipped | Open the report details and fix the listed errors |
| Couldn’t fetch | Google could not retrieve the file | Check the URL, access and server response |
For a failed fetch, Google says it retries for a few days. After you fix the cause, you do not always need to resubmit, but resubmitting is harmless (my own note).
Size limits
If you exceed 50,000 URLs, split the list into several sitemaps and list them in a sitemap index. Most WordPress SEO plugins already split by type and size.
How to submit a sitemap
- Open Search Console and choose the right property.
- Go to Indexing, then Sitemaps.
- Type the sitemap path (for example
sitemap_index.xml) under “Add a new sitemap”. - Click Submit.
You can also reference the sitemap in robots.txt with a Sitemap: line. The complete walk-through is in submit a sitemap to Google.
Removing a sitemap
Use the Remove option only to take a file out of the report. Google says removing it does not stop Google from using URLs it already found, and if the file is still on your server and referenced elsewhere, Google may still read it. To stop using a sitemap, remove it from your site or robots.txt as well.
Read the report step by step
Go to Sitemaps
Indexing, then Sitemaps. If the list is empty you have not submitted any. See Search Console setup.
Check every status
Any row that is not Success needs a look.
Compare discovered pages
The number should be close to how many pages you want indexed. A big gap suggests missing URLs or noindex pages in the file.
Click the row
The detail view lists errors and examples. Fix the cause, not just the symptom.
Check indexing
Open the Page indexing report and filter by sitemap to see what happened to submitted URLs.
Notes for WordPress sites
- Use the plugin’s sitemap. Yoast and most SEO plugins create
/sitemap_index.xmlautomatically. See Yoast SEO settings. - One sitemap system. Do not run a plugin sitemap and the core
wp-sitemap.xmltogether without need (my own advice). - Keep noindex URLs out. Pages set to noindex should not be listed. Most plugins handle this.
- Caching and security. A firewall or cache may block or break the file. Open it in a browser to check.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| Couldn’t fetch | Wrong URL, 404, 5xx, blocked or redirected | Open the URL yourself, fix the response, resubmit |
| Has errors | Invalid XML or bad URLs | Validate the XML and correct entries |
| Success but pages not indexed | Quality or other indexing reasons | Use the Page indexing report |
| Discovered pages is 0 | Empty file or wrong sitemap type | Check the file content |
| Last read is old | Google has not re-read it | Make sure it is reachable and updated |
If the file returns a server error see server error 5xx. For specific URL problems read discovered, currently not indexed and crawled, currently not indexed.
Checklist
File
- Opens in a browser with 200
- Valid XML
- Under 50 MB and 50,000 URLs
- Uses the final https URL
Content
- Only canonical, indexable URLs
- No noindex or redirected URLs
- No 404 URLs
- Matches your real page count
Search Console
- Right property chosen
- Status is Success
- Last read is recent
- Discovered pages looks right
Maintenance
- Check monthly
- Remove old sitemaps properly
- Update after site moves
- Reference it in robots.txt
What Google’s page does not say
Google does not say how often it re-reads a sitemap beyond the failed-fetch retry window, does not promise that submitted URLs will be indexed and gives no ranking benefit for submitting one. The report shows only a limited number of submitted sitemaps (1,000), so very large setups should use a sitemap index.
Key terms
- Sitemap
- A file listing URLs for search engines.
- Sitemap index
- A file listing other sitemap files.
- Discovered pages
- URLs Google found in the sitemap.
- Property
- A site registered in Search Console.
Common mistakes
Submitting a redirecting URL
Google does not follow redirects here.
Listing noindex pages
Mixed signals waste crawl effort.
Believing Success means indexed
It only means the file was read.
Using Remove to stop Google
It only removes the row.
Exceeding limits
Files over 50 MB or 50,000 URLs fail.
Wrong property
An http property may show no data.
Related guides
Sitemaps report questions
Where is the Sitemaps report?
In Search Console under Indexing, then Sitemaps.
What do the three statuses mean?
Success means the file was read; Has errors means problems were found; Couldn’t fetch means Google could not retrieve it.
What are the size limits?
50 MB uncompressed and 50,000 URLs per sitemap, and 50,000 sitemaps per index file.
Does Google follow redirects for the sitemap URL?
No. Submit the final URL.
Does removing a sitemap delete my pages from Google?
No. It only removes it from the report.
How long does Google keep retrying a failed fetch?
Google says it retries for a few days.
Does submitting a sitemap improve rankings?
No. It helps discovery only.
Why are fewer pages discovered than I have?
Some may be excluded, noindexed or missing from the file. Compare with your real page list.
Columns, statuses, limits and removal behaviour come from those pages. The step-by-step reading routine, WordPress notes, troubleshooting table and checklists are my own.