What it means
A sitemap gives crawlers a list to consult alongside the links they find on your pages. It can be useful when a business publishes many products, launches a new section, or has important pages that are difficult to reach through navigation. Good internal links still help people and crawlers find their way.
An XML sitemap can list individual addresses. A sitemap index instead points to other sitemap files, which lets a publisher organize a larger collection. Website platforms often generate these files automatically, but the business still needs to decide which pages belong in the published collection.
Discovery is only one step. A crawler may know an address but receive a refusal, find that the page moved, or decide not to index it. Google explicitly describes sitemap submission as a discovery aid rather than a guarantee that every listed item will be crawled or indexed.
Hypothetical example: a found file with a missing product
A fictional shop launches a new service page. Its sitemap request succeeds, but the page is absent because the publishing plugin has not refreshed the list. BLURSOR can report that it found a sitemap without having established that this particular service URL appears inside it. The next useful check is the list itself.
How BLURSOR measures it
In the report: Sitemap
BLURSOR first requests /sitemap.xml. If that response is not classified as present and usable robots.txt declarations are available, the checker can try a declared sitemap location. The report identifies whether the selected resource came from the standard path or that declaration.
The current format detector looks for opening and closing urlset or sitemapindex elements in the retained text. This is a limited format check, not complete XML validation. The report also keeps the response status, resolved address, and capture-limit qualification. It does not walk the entire sitemap collection or verify every listed page.
What to do next
- Ask your website team where the maintained sitemap is published and which system updates it.
- Check that important new public URLs appear in the appropriate sitemap and have useful internal links.
- Investigate a challenge, refusal, or unexpected HTML response as a delivery problem before editing sitemap entries.
What it cannot tell you
- A found result does not prove coverage of the submitted page or every sitemap on the site.
- A capture limit or failed request leaves evidence incomplete; it does not establish that the whole file is empty or malformed.
Sources and further reading
The definitions below describe the underlying concepts. The measurement section describes BLURSOR’s own checks.