A zero in Google Search Console’s sitemap report means Google has counted no page URLs from the sitemap index and its child sitemaps. It does not, by itself, mean those pages are not indexed—or reveal why no URLs were counted. Check the report status first, then verify that Google can fetch and parse the index and its child sitemap files.
What “Discovered pages: 0” means
In the Sitemaps report, “Discovered pages” counts page URLs Google parsed from the submitted sitemap. For a sitemap index, the count covers URLs in its child sitemaps, with duplicate URLs counted once. It is a sitemap-content count, not an index-status count. Google’s Sitemaps report documentation and Page indexing report documentation describe these as separate reports.
As an Amazon Associate I earn from qualifying purchases.
A zero therefore does not establish whether Google has crawled or indexed the pages. A page may be indexed even if it is absent from this sitemap count; conversely, a URL parsed from a sitemap is not guaranteed to be crawled or indexed.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Start with the sitemap row and its status
- In Search Console, open Indexing > Sitemaps in the property for the site.
- Confirm the displayed sitemap URL is the current sitemap index. Check the property’s protocol and host—such as HTTPS versus HTTP and www versus non-www—and make sure you are viewing the property where the sitemap was submitted.
- Review the sitemap type, Submitted and Last read dates, latest status, and any details shown when you open the row.
The report lists sitemaps submitted through the report or Search Console API. Google may discover a sitemap through robots.txt or another route without listing it as a report submission. The report shows the exact submitted URL; redirects are not followed for that entry. Google explains the report and its submission behavior here.
#1 Best Overall
“Couldn’t fetch”
This status points to a retrieval problem, not proof that the child files contain no URLs. Google lists possible causes including a sitemap blocked by robots.txt, an unresolved manual action, an incorrect URL or 404 response, server unavailability, and low crawl demand. Open the row’s error details to see what Search Console reports for your sitemap.
“Has errors”
Google fetched the sitemap but encountered one or more problems. Expand the error details and identify whether they concern a child sitemap, XML syntax or format, URL scope, a size or entry limit, or another parsing issue. Google may still queue URLs it could parse, so this status does not necessarily mean every URL was ignored.
Rank #2
“Success” with zero discovered pages
Success means Google loaded and processed the sitemap without errors; it does not mean the file yielded page URLs. Check which child files the index lists and whether those files contain valid page URL entries. The count still does not say whether those pages are indexed.
Recommended Free Tools
Test whether Google can fetch the sitemap
Use URL Inspection’s live test on the sitemap URL. Check that crawling is allowed and that Page fetch succeeds. A file opening in your own browser does not establish that Google can retrieve it. Google’s URL Inspection documentation explains the live test.
If the live test fails, use the reported result to investigate access restrictions, the sitemap address, or server availability. If the index fetch succeeds, continue by checking its child sitemap URLs: a readable index can still point to missing or invalid files.
Validate the index and each child sitemap
Check the index structure
A sitemap index must use a sitemapindex root, contain sitemap entries, and use loc values to identify the sitemap files. The sitemap namespace is http://www.sitemaps.org/schemas/sitemap/0.9. Each listed child should be a sitemap file, not another sitemap index; nested indexes are an explicit error. Google’s large-sitemap guidance documents the index structure and limits, while its Sitemaps report help describes reported errors.
Check every child location
Each loc should be a complete, correct URL, and Google must be able to fetch the referenced file. Google’s rules generally require referenced sitemaps to be on the same site as the index and in the same directory or a lower directory in the site hierarchy, unless cross-site submission is configured. Incomplete locations, incorrect paths, and inaccessible child files can prevent URLs from being counted. See Google’s rules for sitemap indexes and cross-site submission.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Inspect child file contents
- Confirm each child sitemap contains page URL entries rather than being empty.
- Check for malformed XML, an unsupported format, invalid URLs, or an incorrect namespace.
- If a child sitemap is compressed, verify that the file is validly compressed and can be processed.
- Compare the child URLs with the site’s actual URL structure and the directory constraints that apply.
Google documents empty sitemaps, XML parsing problems, unsupported formats, compression errors, and URL-scope problems among issues to investigate. Review its list of Sitemaps report errors.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Resubmit after fixing a confirmed problem
Correct the specific fetch or parsing issue before resubmitting. Resubmission is appropriate when the sitemap failed or a significant change needs processing. Google retries failed fetches for a period, but may eventually stop if the sitemap remains unavailable or has critical errors. Check the report again after Google has had time to process it; submission does not guarantee that Google will download the file or crawl its URLs. Google describes sitemap submission as a hint, not a guarantee.
Check page indexing separately
To find out what happened to particular pages, use the Page indexing report or inspect representative URLs with URL Inspection. The Page indexing report can be filtered to a specific sitemap and reports indexing outcomes; the Sitemaps report’s discovered count records URLs parsed from sitemap content. Check the page-level result rather than treating a zero sitemap count as an indexing verdict. Google does not guarantee that every URL listed in a sitemap will be crawled or indexed. Page indexing report details and Google’s sitemap guidance explain the distinction.
Quick Recap
Quick diagnosis by failure point
- Wrong property or missing report entry: verify the exact property and whether the sitemap was submitted through the report or API.
- Index cannot be fetched: check the live test, access rules, URL, and server response.
- Index fetches, but child files fail: verify each listed URL, its accessibility, and its site and directory scope.
- Files fetch, but parse no pages: inspect for an empty child, invalid or unsupported XML, a nested index, or malformed URL entries.
- Sitemap count is zero, but indexing is the concern: check the Page indexing report or individual URLs; the two reports answer different questions.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
