// SEO plans from €35/hour or €395/month// from €35/hr · €395/mo Free SEO checker[email protected]+31 6 4555 9353
Free SEO audit
search console

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
sitemapsreport
sitemap_index.xml   Index   Success
post-sitemap.xml    Sitemap Success
page-sitemap.xml    Sitemap Success
old-sitemap.xml     Sitemap Couldn't fetch
// quick answer
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.

it tells you

If Google could read the file

Status, last read date and how many pages it found.

it does not tell you

If pages are indexed

Use the Page indexing report for that.

New to sitemaps? Read robots.txt and sitemaps first.

Every column explained

ColumnWhat it meansWatch for
Sitemap URLThe address you submittedGoogle does not follow redirects here
TypeSitemap or sitemap indexIndex files list other sitemaps
SubmittedWhen you submitted itNot when Google read it
Last readWhen Google last fetched itAn old date can mean no recent re-read
StatusSuccess, Has errors or Couldn’t fetchSee the next section
Discovered pagesURLs Google found in the fileCompare with your real page count
Discovered videosVideo entries found, if anyOnly for video sitemaps
The redirect note matters: if your sitemap URL redirects, for example from http to https, submit the final URL, not the redirecting one.

The three statuses

StatusMeaningWhat to do
SuccessGoogle read the file with no problemsNothing, but still check page counts
Has errorsGoogle read it but found problems; some URLs may be skippedOpen the report details and fix the listed errors
Couldn’t fetchGoogle could not retrieve the fileCheck 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

file size50 MBuncompressed
URLs per sitemap50,000maximum
sitemaps per index50,000maximum
shown in report1,000submitted sitemaps

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.

remove in reportOnly deletes the row from your list
delete the fileStops Google reading it, returns 404
edit robots.txtRemoves any Sitemap: line pointing to it

Read the report step by step

1
open

Go to Sitemaps

Indexing, then Sitemaps. If the list is empty you have not submitted any. See Search Console setup.

pick property
2
scan

Check every status

Any row that is not Success needs a look.

SuccessHas errorsCouldn’t fetch
3
compare

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.

real countdiscovered
4
open details

Click the row

The detail view lists errors and examples. Fix the cause, not just the symptom.

read errors
5
follow up

Check indexing

Open the Page indexing report and filter by sitemap to see what happened to submitted URLs.

filter by sitemap

Notes for WordPress sites

  • Use the plugin’s sitemap. Yoast and most SEO plugins create /sitemap_index.xml automatically. See Yoast SEO settings.
  • One sitemap system. Do not run a plugin sitemap and the core wp-sitemap.xml together 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

SymptomLikely cause (my own diagnosis)Fix
Couldn’t fetchWrong URL, 404, 5xx, blocked or redirectedOpen the URL yourself, fix the response, resubmit
Has errorsInvalid XML or bad URLsValidate the XML and correct entries
Success but pages not indexedQuality or other indexing reasonsUse the Page indexing report
Discovered pages is 0Empty file or wrong sitemap typeCheck the file content
Last read is oldGoogle has not re-read itMake 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

mistake 1

Submitting a redirecting URL

Google does not follow redirects here.

Submit the final URL.
mistake 2

Listing noindex pages

Mixed signals waste crawl effort.

Remove them from the file.
mistake 3

Believing Success means indexed

It only means the file was read.

Check page indexing.
mistake 4

Using Remove to stop Google

It only removes the row.

Delete the file as well.
mistake 5

Exceeding limits

Files over 50 MB or 50,000 URLs fail.

Split into several sitemaps.
mistake 6

Wrong property

An http property may show no data.

Use the https or domain property.

Related guides

faq

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.

sources

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.

Scroll to Top