Parsed sitemap contains no supported URL or nested sitemap entries
ShipReady fetched and parsed the selected sitemap but found no supported URL entries or nested sitemap entries within its bounded inspection.
Why it matters
A sitemap that parses without entries is a deployment signal to review. The observation does not determine which URLs search engines already know or whether they will discover pages through links or other sources.
How ShipReady detects it
What it inspects
ShipReady selects the first supported Sitemap: URL from crawl-captured robots.txt, or falls back to /sitemap.xml. It makes one bounded, redirect-following request and parses accepted XML through its hardened parser.
What triggers a finding
The rule triggers when a successfully read sitemap has an accepted urlset or sitemapindex root but no supported URL entries and no nested sitemap entries within the scanner's capped entry inspection.
What the evidence shows
The selected sitemap parsed as a supported sitemap root and yielded no supported URL or nested-sitemap entries to ShipReady's bounded parser.
Limits of this check
Absent, unavailable, unsafe, oversized, truncated, empty-body, and SPA-catchall responses do not create this finding. ShipReady uses the first supported robots declaration and does not fetch nested sitemaps, inspect every possible sitemap path, or establish crawler discovery or index status.
How to fix it
Review the sitemap generator and source data
Confirm the selected sitemap is generated from the intended public routes and that it emits usable URL or nested-sitemap entries.
Deploy and inspect the selected sitemap
After deployment, request the same selected sitemap URL and inspect the emitted document.
How to verify the change
Verify the selected sitemap entries
Inspect the final selected sitemap and confirm it contains the intended URL entries or sitemap-index entries.
Expected: The selected sitemap parses and contains the intended supported entries.