An HTML sitemap does not replace the main menu or the internal search engine. It serves a distinct function: to expose the entire structure of a site on a single page, without interaction or hovering. For an editorial site structured into several dozen sections, this comprehensive view resolves navigation issues that other interface components leave open.
HTML sitemap and XML sitemap: two files, two audiences
The confusion between HTML sitemap and XML sitemap remains common, even among technical profiles. The XML sitemap is intended for crawlers (Googlebot, Bingbot) and provides them with a list of URLs along with metadata on frequency and last modified date. The HTML sitemap, on the other hand, is designed for a human visitor looking for specific content without knowing the navigation path.
Confusing the two leads to optimizing indexing without addressing actual navigation difficulties. A properly maintained XML sitemap improves crawl coverage, but it offers no recourse to users who cannot find a section from the menu. In contrast, a well-structured HTML sitemap provides a complete alternative navigation path, readable by all user agents, both human and assistive.
We recommend maintaining both files in parallel, each serving its audience. On a site like Les Indispensables, whose editorial catalog covers various themes, exploring the Les Indispensables sitemap allows users to locate a section that a multi-level menu might have obscured in just a few seconds.
Freshness of metadata: a signal often poorly utilized
The lastmod tag in an XML sitemap should only be updated when the content of the page has actually changed. Artificially modifying this date in hopes of speeding up recrawling does not provide a reliable signal to search engines. Google has repeatedly stated that lastmod dates not correlated with an actual change eventually get ignored.
For an editorial site that regularly revises its content, consistency between the lastmod date and the last visible update on the page enhances the credibility of the signal. The HTML sitemap, however, does not need this metadata: it reflects the current structure as it exists at the time of consultation.
The classic trap is to regenerate the XML sitemap daily without touching the HTML sitemap. The result: crawlers receive a freshness signal, but the visitor encounters an outdated sitemap page where recent sections do not appear. Synchronizing both documents remains the only reliable approach.
Accessibility of the sitemap and the European Accessibility Act
The European Accessibility Act targets specific categories of digital products and services intended for European consumers: e-commerce, banking services, certain electronic communications. The mere existence of a showcase site does not automatically trigger compliance obligations.
A well-constructed HTML sitemap contributes to accessibility but is not sufficient to make a site compliant. The requirements cover the entire user journey:
- Complete keyboard navigation, without focus traps or excessive tabbing to reach content
- Compatibility with screen readers, which implies correct HTML semantics (ordered lists, consistent heading levels)
- Sufficient contrast between text and background, including on the sitemap page itself
- Content structure compliant with RGAA or WCAG criteria, depending on the applicable reference
For screen reader users, navigating a site page by page to understand its architecture requires disproportionate cognitive effort. The HTML sitemap offers them a comprehensive view of the structure in one place, without having to explore each section sequentially.
Keyboard navigators, whether they are individuals with motor disabilities or advanced users, find direct access to a specific section. We observe that this benefit is often underestimated: even on modest-sized sites, the time savings are tangible as soon as there are more than three levels of depth in the structure.
Content of the HTML sitemap: what to include and exclude
A sitemap is not a duplicate of the navigation menu. Its role is to present a comprehensive yet readable view of the entire site. Structuring pages (home, main sections, sub-sections) are systematically included. Utility pages such as legal notices, privacy policy, or terms and conditions also have their place, as they are often absent from the main menu.
In contrast, certain pages add no value in an HTML sitemap:
- Internal search results pages, which do not have stable content
- Redirect pages or technical duplicates generated by a CMS
- Pages protected by authentication, inaccessible to non-logged-in visitors
For dynamic sections (blog, news), we recommend listing categories or tags rather than each article individually. A sitemap displaying several hundred links loses its quick reference function. Readability takes precedence over raw completeness.
A properly maintained HTML sitemap remains one of the few components of a site that simultaneously serves accessibility, navigation, and internal linking. Neglecting it means depriving some visitors of structured access to all available content, regardless of the quality of the main menu.
