Sitemap discovered 0 URLs: why the list is empty
Google fetched the file but found no usable URLs. Check the root element, namespace, loc values, child files and whether the response is really XML.
Zero discovered URLs usually means zero parsed locations
A sitemap can be fetched successfully and still yield no URLs. In most cases Google did not find a usable loc element: the response was HTML, the XML used the wrong namespace, the file was empty, or an index listed child files that could not be read.
Open the exact URL and inspect the first few hundred bytes. If the document starts with a doctype and a head tag, the route is serving the website shell and the sitemap file never existed.
curl -sL https://example.com/sitemap.xml | head -c 300Check the three things parsers need
A page sitemap needs the sitemap namespace, a urlset root, and at least one url element with a loc. An index needs a sitemapindex root with sitemap entries pointing at child files.
- Root is urlset for pages or sitemapindex for a list of files.
- The xmlns attribute is the sitemap namespace, not a custom one.
- Each page entry has a loc with an absolute URL.
- An index lists child sitemaps, not page URLs.
- Child files are reachable and return XML.
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://example.com/about</loc></url>
</urlset>Empty after a framework deployment
Generated sitemaps can be empty when the build has no routes, when a data source returns nothing, or when the route renders before content is loaded. Fetch the file after a production build, not from a development server.
If the sitemap is generated from a database, confirm the query returns published rows and that the deployment ran the generation step. An index whose children are all empty will also report zero URLs.
What to do next
Fix the file, fetch it once, and confirm at least one loc is visible in the raw response. Resubmit the URL, then check the discovered count after the next read rather than continuously resubmitting.
Zero URLs is a parsing or generation problem, not a ranking signal. Once the list is populated, review the individual pages for indexability separately.
See what the page actually returns
A free audit catches HTML fallbacks, blocked assets and pages that cannot be indexed.
Run a free audit