
An XML sitemap lists a site’s URLs, but that list says nothing about the actual state of the pages it contains. Some URLs may return an error, others may have no internal links pointing to them, and still others may display outdated content despite a recent last-modified date. To explore a sitemap effectively, treat it as an inventory of candidates to check, not a directory of working pages.
XML sitemap: what the file doesn’t reveal about your pages
The Sitemap protocol allows a maximum of 50,000 URLs or 50 MB uncompressed per file. Sites that exceed these limits use a sitemap index—a file that points to several secondary sitemaps. This segmentation offers a first clue for exploration: each subfile generally groups a type of content (articles, product pages, categories), making it possible to examine coherent sets rather than a single list.
Google explains that including a URL in a sitemap does not guarantee that it will be indexed. The file signals that a page exists, not that it is high-quality or relevant. To see how a site organizes its content, browsing Passez l’info’s sitemap offers a good example of how a sitemap index groups URLs by section.
Two sitemap tags are often misunderstood. Google ignores the priority tag: it affects neither crawl order nor rankings. The same goes for the changefreq tag. These declarative metadata therefore have no value for prioritizing which pages to examine first.

Cross-check the sitemap against internal links and inspection reports
The most productive way to explore a sitemap is to compare it with two other sources: the site’s internal linking structure and Search Console data. This triangulation reveals discrepancies that are never apparent from reading the XML file alone.
Find orphan pages in the sitemap
A URL that appears in the sitemap but is absent from the internal linking structure presents a real problem. Crawlers may discover it through the XML file, but visitors have no navigation path to reach it. This type of orphan page is unlikely to attract traffic, even if it is indexed.
To identify these cases, compare the sitemap URL list with a site crawl (using Screaming Frog, Sitebulb, or any other crawling tool). URLs that appear in the sitemap but have no internal links pointing to them warrant a closer look: either they should be linked from the site structure, or they no longer belong in the file.
Check the actual status using URL Inspection
Google Search Console’s Sitemaps report shows the number of URLs discovered and any errors encountered. This report provides an overview, but inspecting a URL individually is the only way to find out its exact status: indexed, discovered but not indexed, excluded because of a canonical tag pointing elsewhere, or blocked by the robots.txt file.
In practice, starting with URLs flagged as problematic in the Sitemaps report helps focus your efforts on specific cases. There’s little value in inspecting a random URL in a sitemap containing several thousand pages.
The lastmod tag: a useful signal, with one condition
Google says the lastmod tag can help it schedule new crawls, provided that the date reflects a significant change to the page’s content, structured data, or links. A simple footer update or automatic site rebuild does not justify changing the date.
On many CMS platforms, the lastmod date is updated every time a page is saved, even for a comma correction. This behavior dilutes the signal. Sites whose lastmod tags are consistently accurate and verifiable send a more reliable signal to crawlers.
To make use of this information during a manual review, sort the sitemap URLs by lastmod date to identify two interesting cases:
- Pages with very old dates (several years ago) that have apparently never been updated, which may indicate outdated content that needs to be reviewed or removed
- Pages whose dates change very frequently even though their visible content does not, indicating a CMS configuration issue
- Recently updated pages that Search Console shows as not yet indexed, which warrant individual inspection to understand what’s preventing indexing
Sitemap and IndexNow: distinguishing discovery from indexing on Bing
The IndexNow protocol lets you notify Bing and other participating search engines that a URL has been added, changed, or deleted. A receipt response confirms that the notification was received, but it does not guarantee crawling or indexing.
The sitemap remains the source-of-truth inventory for these search engines. IndexNow serves as a complementary real-time notification system. When exploring a sitemap, this distinction matters: a URL may appear in the file and have been submitted via IndexNow, yet still not show up in search results. Bing Webmaster Tools provides a URL status report similar to Google’s, which can help you check these cases.

A practical method for sorting sitemap URLs
Systematically exploring a sitemap means not reading the file line by line. The most effective approach follows a specific order:
- Download the sitemap (or sitemap index) and import the URLs into a spreadsheet or crawling tool to get an overview by content type
- Cross-check these URLs against internal link data from a crawl: identify orphan pages, pages with only one incoming link, and the most heavily linked pages
- Compare the list with Search Console (or Bing Webmaster Tools) reports to identify URLs that are not indexed, are excluded, or have errors
- Check that lastmod tags are consistent by comparing the dates shown with actual content changes
Cross-referencing the sitemap, internal linking structure, and inspection reports turns a simple XML file into a diagnostic tool. Pages that appear in the sitemap, have strong internal links, and are confirmed as indexed are the ones that genuinely contribute to the site’s visibility. The others need corrective action or should be removed from the file.
A clean sitemap, where every URL corresponds to an accessible, canonical page linked to the rest of the site, sends a clear signal to search engines. By contrast, a file bloated with dead or orphaned URLs diverts crawlers’ attention to pages that offer no value to visitors.