A sitemap brings together all the pages on a domain in a structured list. Reading that list without a method is like browsing a phone book page by page: the time you waste quickly outweighs the benefits. To explore a sitemap efficiently, you need to understand how it is organized, what signals it provides, and which tools can filter its entries to pinpoint the exact resource you’re looking for.
HTML sitemap and XML sitemap: what each format reveals
A website may offer two types of sitemaps. Confusing them is like looking for a book in the wrong section.
| Criterion | HTML sitemap | XML sitemap |
|---|---|---|
| Primary audience | Human visitors | Crawlers (Googlebot, Bingbot) |
| Typical access | Link in the footer or menu | File at the domain root (/sitemap.xml) |
| URL organization | By category or topic, with readable titles | Raw list of URLs, sometimes without a hierarchy |
| Available metadata | None (titles and links only) | Last modified date (lastmod), sometimes priority and frequency |
| Usefulness for finding a resource | Quick navigation to a specific section | Finding orphaned URLs or hidden sections |
The HTML version is the most direct starting point for visitors. It displays easy-to-understand labels, often grouped by section. On the official Le Patrimoscope sitemap, each topic category appears alongside its subpages, making it possible to identify the relevant section in seconds without browsing the entire site structure.
An XML sitemap, on the other hand, is not designed for people to read. It is intended for search engines. An XML sitemap helps search engines discover URLs but does not guarantee their indexing: it supplements internal links, but does not replace them. Google explains this in its sitemap documentation.
Filter sitemap URLs: keyboard shortcuts and search operators
A large HTML sitemap can contain hundreds of links. Reading it line by line is counterproductive. Two techniques can help you find what you need faster.
Search the page with Ctrl+F
The Ctrl+F shortcut (or Cmd+F on Mac) opens a search field in your browser. Enter a keyword related to what you’re looking for (for example, “heritage”, “guide” or “taxation”) and the browser highlights every occurrence on the page. Press Enter to move from one result to the next.
Ctrl+F works on HTML sitemaps just as it does on any web page. When you open an XML sitemap in your browser, the same shortcut can find URL fragments (“/blog/”, “/resources/”, “/2025/”) to isolate a section or time period.
The site: operator in Google
When the sitemap isn’t enough, the site:domain.com keyword command searches Google’s index for results from a single domain. You’ll see indexed pages containing your term, ranked by relevance. This approach can uncover pages missing from the HTML sitemap, especially if the site’s list hasn’t been updated.
- site:example.com “practical guide” returns only pages on the domain containing that exact phrase
- site:example.com filetype:pdf targets PDF documents hosted on the domain, which are often missing from the HTML sitemap
- site:example.com inurl:resources limits results to URLs containing the “resources” directory
Freshness signals in an XML sitemap: lastmod, changefreq and priority
Opening a sitemap.xml file in your browser displays a list of URLs accompanied by metadata. Not all of it is equally reliable.
The lastmod field indicates the date a page was actually last modified. Bing uses it to decide which URLs to revisit first. An updated date signals that content has been reviewed recently, which can help guide your choice when several pages cover the same topic.
The changefreq and priority fields, by contrast, are largely ignored by search engines. Bing says it does not take these two tags into account. Google takes the same position. Only the lastmod date provides a usable signal for assessing a resource’s freshness from a sitemap.
A common pitfall: some CMS platforms regenerate the sitemap with every publication and update all lastmod dates, even for pages that haven’t changed. When all the dates are identical, the signal loses its value. Check whether the dates actually vary from one URL to another before relying on them.
Pages missing from the sitemap: robots.txt and orphaned URLs
A sitemap, whether HTML or XML, does not always list every page on a domain. Two common scenarios explain why pages may be missing.
A URL blocked in the robots.txt file may still be known to search engines if other pages link to it. robots.txt controls crawling, not deindexing. The search engine knows the address but cannot read the content. In practice, the page may appear in search results with a title and URL but no snippet, making it difficult to find through the sitemap.
Orphaned URLs, on the other hand, have no internal links pointing to them. They exist on the server but remain invisible in both the site’s navigation and its HTML sitemap. Google’s site: operator can sometimes surface them if they were indexed through another route (an external link or an old sitemap).
- Check the robots.txt file (available at domain.com/robots.txt) to identify blocked directories
- Compare the number of pages in the XML sitemap with the number of results returned by site:domain.com
- A significant difference between these two figures may indicate pages missing from the sitemap or active blocking directives
You can explore a sitemap more precisely by combining the HTML sitemap, Ctrl+F filtering, site: queries and an XML sitemap check. The lastmod date remains the only reliable technical indicator of freshness. The most effective habit is to compare the sitemap with the search engine’s actual index to find what’s missing.
