An HTML sitemap is more than a page listing links. It is a navigation component in its own right, presenting a complete overview of a website’s structure, independently of the main menu or search bar. Its role becomes crucial when pages are more than three levels deep or the internal linking structure has dead ends.
HTML sitemaps and the WCAG criterion for multiple ways to navigate
The W3C recommends providing multiple ways to reach a page, such as the main navigation, search, breadcrumbs, and a sitemap. This principle of providing multiple ways to access content is reflected in the WCAG criteria. A well-designed menu is not enough if visitors are unfamiliar with the terminology used in section labels.
A sitemap solves this problem by displaying the complete hierarchy. Screen reader users can move through the page linearly and find a section without tabbing through every interactive element in the header, mega menu, and footer. Keyboard users benefit in much the same way: they can go straight to the page they need without navigating through the interactive components that come first.
For example, the Belle et Épanouie sitemap presents all categories and subpages in a clear hierarchy, making it easy to find specific content without relying on the main navigation menu.
Since June 28, 2025, the European Accessibility Act has introduced new accessibility requirements for certain digital products and services offered to EU consumers, including e-commerce (with exceptions for microenterprises providing services). Accessible navigation is now a regulatory requirement, not just a matter of convenience. An HTML sitemap directly supports compliance by complementing existing navigation paths.

How to structure an effective sitemap: pages to include and exclude
A sitemap is not a duplicate of the menu. It should provide a comprehensive yet hierarchical overview. Confusing these two roles results either in a page that is too sparse (a copy of the main menu) or one that is impossible to navigate (an unstructured list of several hundred URLs).
Key pages and functional pages
Pages to include as standard:
- Key pages: the homepage, top-level sections, and subsections with their own content (product categories, editorial topics)
- Content with strong search value: blog posts, product pages, and service pages that serve as organic entry points to the site
- Legal and utility pages (legal notices, privacy policy, contact page). These are often missing from the menu, but belong in the sitemap because visitors may look for them from time to time
Pages to exclude: internal search results, pagination pages, parameterized filter pages, and redirects. Including them obscures useful information and makes the sitemap harder to read.
Handling dynamic sections
A blog or news section presents a specific challenge. Listing every article individually makes the sitemap unusable once the number of posts reaches more than a few dozen. The cleanest technical solution is to list the main categories and tags rather than every article. Visitors can go to a category and browse its content using pagination or the category’s built-in sorting options.
HTML sitemap and XML sitemap: two components, two purposes
Many projects still confuse an HTML sitemap (intended for visitors) with an XML sitemap (intended for search engine crawlers). Their scope and purpose are entirely different.
An XML sitemap helps search engines discover pages, but does not guarantee that they will be crawled or indexed. Google treats it as one signal among many. An XML sitemap containing URLs that return 404 errors or pages blocked by robots.txt has no positive effect.
An HTML sitemap, by contrast, is intended for people. Its value lies in making the hierarchy easy to understand, not in technical completeness. We recommend maintaining both, but never generating one from the other without filtering. An XML sitemap may contain technical canonical URLs that should be excluded from the HTML sitemap. Conversely, the HTML sitemap may group content under labels that do not exist as separate URLs in the XML sitemap.

Consistent navigation: a sitemap cannot make up for a broken menu
A sitemap helps visitors find their way only when it complements a predictable interface. If the main menu’s structure or labels change from page to page, the sitemap will not fix the underlying problem. The W3C emphasizes the consistent placement, style, and labeling of navigation elements across pages.
In practice, three conditions must be met for a sitemap to do its job:
- The sitemap uses the same wording as the main menu and breadcrumbs—there should be no differences in phrasing between the three components
- The hierarchy shown in the sitemap reflects the site’s actual depth: if a page is accessible within two clicks from the homepage, it should appear at the second level of the sitemap, not the fourth
- The sitemap page is accessible from the footer or a permanent utility section, rather than hidden behind an occasional contextual link
A sitemap that is published and then forgotten during two years of gradual redesign becomes a trap. Visitors who use it encounter broken links or outdated labels. Sitemap maintenance should follow the same schedule as main menu maintenance: any change to the site structure must be reflected in both.
A sitemap remains one of the few components that gives disoriented visitors, users of assistive technologies, and internal teams auditing the site structure a complete architectural overview. Its value depends entirely on keeping it up to date and consistent with the rest of the navigation interface.



