A sitemap is a page that lists all the accessible URLs of a website, organized by categories or hierarchical levels. This page serves as a reference for visitors looking for specific information and as a technical signal for search engines exploring the structure. Understanding how a sitemap works, and especially what distinguishes its different forms, allows for concrete benefits in daily navigation.
HTML Sitemap and XML Sitemap: Two Distinct Navigation Logics
The term “sitemap” encompasses two technical realities that must be separated from the outset. The HTML sitemap is a classic web page, readable by a human, that presents internal links in the form of a structured list. The XML sitemap, on the other hand, is a file intended for indexing bots like Googlebot or Bingbot.
The XML file signals to search engines the important URLs to explore. It must exclude redirected, erroneous, duplicated, or noindex pages. Its value depends entirely on its maintenance: after a redesign, content removal, or structural change, an outdated XML sitemap sends bad signals to crawlers.
The HTML sitemap, on the other hand, serves as a navigation tool for visitors. When a main menu is insufficient (a site with several hundred pages, an extensive product catalog, a thematic portal), the HTML sitemap provides an overview that traditional navigation cannot offer. A concrete example of this approach can be found on the Esceri sitemap, which organizes its content into categories that are directly readable from a dedicated page.
HTML Sitemap: What Makes a Navigation Page Truly Useful
Creating an HTML sitemap is not just about automatically generating a list of links. Most sitemaps generated by CMS extensions produce flat lists, without logical grouping, sometimes stretching to several hundred lines. This type of page helps no one.
A useful sitemap is based on three concrete principles:
- Grouping by theme or section, not in chronological order. The visitor is looking for a category, not a publication date.
- A clear visual hierarchy between levels of depth: main sections appear first, sub-pages are indented or grouped under their parent section.
- Explicit link titles that describe the content of the target page, not generic labels like “Page 1” or “Learn more”.
This last point directly relates to good accessibility practices. Assistive technologies (screen readers, keyboard navigation) use link text to help users understand the destination without visual context. A sitemap with vague anchors becomes unusable for these profiles.
Accessibility and Sitemap: A Regulatory Requirement Since 2025
Since June 28, 2025, the European Accessibility Act applies to several sectors: e-commerce, banking services, transportation, telecommunications, digital books. The navigation of a concerned site must be keyboard usable, compatible with assistive technologies, and structured in a comprehensible manner.
The WCAG 2.2 recommends providing multiple means to find a page: main navigation, search function, and sitemap. The sitemap alone is not sufficient to meet this criterion. The standard also requires mechanisms to bypass repetitive blocks, such as a “Skip to content” link or clearly identified HTML regions with appropriate ARIA attributes.
For a commercial site or online service subject to this regulation, the HTML sitemap shifts from being an optional complement to an expected component in the navigation architecture. Not offering it does not constitute an infringement in itself, but its absence reduces navigation options and complicates overall compliance.
Structure and Site Architecture: The Sitemap as a Diagnostic Tool
The HTML sitemap has an often-overlooked use: it serves as a mirror to the actual structure. When a site manager generates or manually updates their sitemap, they visualize the depth of each page, imbalances between sections, and orphaned content (pages accessible only by their direct URL, without internal links).
Orphaned content is invisible to search engines if no internal link points to it. The sitemap, by listing all pages, can reveal these dead ends. This diagnosis is particularly valuable after a redesign or migration, when old pages lose their incoming links without anyone noticing.
Updating the sitemap after each structural change (adding sections, deleting pages, merging categories) ensures that the document remains reliable. An outdated sitemap gives a false image of the structure and can lead visitors to 404 errors.
Checks to Conduct After a Redesign
- Check that each URL listed in the sitemap returns an HTTP 200 code, not a redirect or an error.
- Verify the consistency between the HTML sitemap and the XML sitemap: both should reflect the same indexable pages.
- Ensure that the canonical URLs declared in the source code match the URLs present in the sitemap.
This verification work, often postponed, prevents the sitemap from becoming a stagnant document that loses all utility over the months. A maintained sitemap after each evolution of the site remains a reliable navigation tool, for both visitors and indexing engines.
