No sitemap was discovered through the supported origin checks
ShipReady found neither an HTTP 200 /sitemap.xml response nor a supported Sitemap: declaration in an answered HTTP 200 robots.txt response.
Why it matters
A sitemap is one discovery signal an origin may publish. This bounded absence finding does not show what a search engine has discovered, crawled, or indexed through other signals.
How ShipReady detects it
What it inspects
After a successfully fetched content-serving page, ShipReady probes /robots.txt and /sitemap.xml with redirects enabled. It reads the first supported Sitemap: directive, case-insensitively, from an HTTP 200 robots.txt response.
What triggers a finding
The rule triggers when /sitemap.xml has an answered non-200 response, robots.txt was answered, and that HTTP 200 robots.txt response has no supported Sitemap: declaration. A declared alternate sitemap suppresses the finding.
What the evidence shows
ShipReady did not observe an HTTP 200 default sitemap or a supported sitemap declaration in the paired origin probes.
Limits of this check
An unanswered robots.txt probe suppresses this absence finding because ShipReady cannot rule out a declaration. Network failures and rate-limit or unavailable responses are inconclusive. ShipReady does not search all paths, validate an alternate sitemap here, query search engines, or establish discovery or indexing results.
How to fix it
Choose an intended sitemap location
Publish a sitemap at /sitemap.xml or declare its intended alternate URL with a supported Sitemap: line in robots.txt.
Verify the deployed discovery path
Request both deployed files and confirm the chosen sitemap path is available from the intended origin.
How to verify the change
Inspect the deployed files
Check the final response for /sitemap.xml and, if an alternate path is used, the robots.txt Sitemap: declaration.
Expected: The deployment exposes the intended sitemap through the default path or an explicit robots.txt declaration.