A sitemap is a useful list, with limits

An XML sitemap lists addresses that a publisher wants a crawler to discover. It can help expose pages that are difficult to reach through ordinary links, but it does not replace useful navigation. Listing an address does not guarantee that a search engine will crawl or index it.

For a small static site, compare three views: the files in a trusted release inventory, the addresses in the sitemap, and the destinations reachable through internal HTML links. Disagreements can reveal an omitted page, an outdated address, or a page with no incoming navigation. They can also reflect an intentional choice, so record the intended indexing role.

Make a careful comparison

• Check that each listed address uses the intended HTTPS origin.
• Request listed destinations and inspect their response statuses.
• Compare the list with index-eligible release pages.
• Review unexpected omissions in the context of page purpose.
• Keep an observation timestamp and the exact list used for the comparison.

Recognise incomplete evidence

A crawl that stops at a page limit cannot establish that every page has been seen. Likewise, a sitemap can be incomplete or stale. To call a page orphaned, you need a sufficiently complete inventory and link graph rather than merely failing to discover it on a short crawl. Be explicit when coverage is unknown, and avoid reporting a confident absence from an incomplete sample.