The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A zero under “Discovered pages” means Search Console has not counted any page URLs parsed from that submitted sitemap index and its child sitemaps. It does not tell you by itself why the count is zero, or whether those pages are indexed. First check the sitemap row’s status and details; then validate the index and each child sitemap, and check page indexing separately.
What “0 discovered pages” does—and does not—mean
The Sitemaps report’s “Discovered pages” count is based on page URLs Google parsed from the submitted sitemap. For an index, the count covers URLs in its child sitemaps, with duplicate URLs counted once. It is not a count of indexed pages. A URL can be included in the sitemap but not indexed, and a zero in this report does not prove that Google has indexed zero pages on your site. Google does not guarantee that every URL listed in a sitemap will be crawled or indexed. Google’s Sitemaps report documentation and sitemap guidance explain the distinction.
Check the sitemap row before changing files
In Search Console, open Sitemaps for the property you expect to contain the submission. Confirm the displayed sitemap URL, its type, the latest status, the “Submitted” and “Last read” dates, and any details shown when you open the row. Google displays the exact URL submitted and does not follow redirects for that report entry. The report lists sitemaps submitted through Search Console or its API; a sitemap Google found through another route may not appear as a submitted entry. Google documents how the report works.
Make sure the property matches the sitemap’s protocol and host—for example, the correct HTTP or HTTPS and www or non-www version. If you submitted the file in a different property, you may be looking at the wrong report.
#1 Best Overall
Choose the next check from the status
| Status | What it indicates | Next step |
|---|---|---|
| Couldn’t fetch | Google could not retrieve the sitemap during the reported attempt. Documented possible causes include a robots.txt block, a wrong URL or 404, server unavailability, an unresolved manual action, or low crawl demand; the status alone does not identify which applies. | Open the error details, then use URL Inspection’s live test on the sitemap URL. Check whether crawling is allowed and whether “Page fetch” succeeds. A sitemap loading in your own browser does not establish that Google can fetch it. See Google’s fetch-error guidance. |
| Has errors | Google fetched the sitemap but encountered one or more problems. The issue may concern a child URL, format, XML syntax, scope, a limit, or another parsing error. | Expand the error details and follow the named error to the index or child file. Google may queue URLs it could parse even when other parts have errors. Review the reported error details. |
| Success | Google loaded and processed the sitemap without errors. A zero still means the report has not counted page URLs from the index and its children; it is not an indexing status. | Inspect which child sitemap files the index lists, then verify that those files are accessible and contain parseable page URLs. Google’s report documentation. |
Validate the index and every child sitemap
A sitemap index is a list of sitemap files, not a list of pages. Google’s documented structure uses a sitemapindex root with sitemap entries and loc values for the child sitemap locations. The sitemap namespace is http://www.sitemaps.org/schemas/sitemap/0.9. Each entry should identify a sitemap file, not another sitemap index: nested indexes are a documented error. Google’s large-sitemap documentation describes the index format and limits; its report guidance covers errors.
- Check each
locvalue. It should be a complete URL, not an incomplete path. Open each child sitemap URL and confirm it can be fetched. - Check location rules. Referenced sitemaps must be hosted on the same site as the index unless cross-site submission is configured, and must be in the same directory or a lower directory in the site hierarchy. Google’s documentation explains these constraints.
- Inspect the child files’ contents. Look for an empty URL set, invalid URLs, malformed XML, an incorrect namespace, an unsupported format, or compression errors. These are documented issues to investigate, not a diagnosis of your particular sitemap. Google lists sitemap report errors.
Google’s documented limits are up to 50,000 loc entries in a sitemap index and up to 500 sitemap index files submitted per site in a Search Console account; those figures appear in documentation last updated December 10, 2025. Check the current limits and format requirements if either limit could apply.
Retest after fixing the specific problem
- Correct the issue identified in Search Console—such as a blocked or incorrect URL, an inaccessible child file, an invalid index entry, or a malformed sitemap.
- Use URL Inspection’s live test on the sitemap URL to check that crawling is allowed and the page fetch succeeds.
- Return to Search Console → Sitemaps and resubmit the corrected sitemap when appropriate, particularly after a failed fetch or significant change.
- Recheck the row after Google processes it. Google retries failed fetches for a period, but may stop if the file remains unavailable or has critical errors. Processing and crawling can take time. Submission is only a hint: it does not guarantee Google will download the file or crawl its URLs. Google states this explicitly.
Check whether pages are indexed in a separate report
To investigate indexing, use the Page indexing report or URL Inspection on representative important pages. Page indexing reports crawl and indexing outcomes; the Sitemaps report’s “Discovered pages” value counts URLs parsed from sitemap content. The Page indexing report can also be filtered to a specific sitemap. If it shows pages as not indexed, investigate the page-level status there rather than treating the sitemap count as the explanation. Google explains the sitemap report and how sitemap discovery relates to crawling and indexing.
Quick Recap
Best Value
Rank #4
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.
