A visitor arrives on a site, searches for specific information, and cannot find it within two clicks. They leave the page. This scenario repeats millions of times a day, and the cause is almost always the same: the absence of a readable sitemap. Before discussing design or content, the way pages are organized and linked to each other determines whether a user stays or leaves.
Sitemap and accessibility obligations: what has changed since 2025
Most articles on web navigation treat the sitemap as a mere practical tool. Since June 28, 2025, it has also become a regulatory issue. The European directive 2019/882, transposed in France by law n° 2023-171 of March 9, 2023, and decree n° 2023-931 of October 9, 2023, makes the accessibility of B2C digital services mandatory in sectors such as e-commerce, banking services, passenger transport, or telecommunications.
In practical terms, a well-structured sitemap facilitates compliance with these requirements. Screen reader users, for example, cannot navigate a complex menu in the same way a sighted visitor can with a mouse. The sitemap provides them with a complete view of the hierarchy in one place.
The RGAA 4.1.2 requires the relevant organizations to publish an accessibility statement, a multi-year accessibility plan (maximum three years), and an annual action plan. These three documents are directly linked to how the site’s structure and navigation paths are designed. A neglected sitemap can thus become a point of non-compliance during an audit.
Difference between HTML sitemap and XML sitemap for SEO
Have you ever noticed that the term “sitemap” is used to refer to two very different things? Confusion is common, and it has consequences on how navigation and SEO are approached.
The HTML sitemap is intended for human visitors. It is a page on the site, generally accessible from the footer, that lists all sections and subsections in the form of clickable links. Its role: to allow anyone to find a page without going through the main menu. This type of page can be found on the Com 2 Net sitemap, which illustrates a well-organized structure by readable sections.
The XML sitemap, on the other hand, is a technical file intended for search engines. Google and other indexing bots read it to discover pages to explore. This file is never displayed to visitors.
- The HTML sitemap helps users navigate and improves site accessibility for people with disabilities.
- The XML sitemap speeds up the indexing of new pages by search engines and signals recent updates.
- Both are complementary: removing one in favor of the other degrades either the user experience or the SEO.
A site that only has an XML sitemap without an HTML sitemap deprives its visitors of a safety net in case of difficult navigation. Conversely, an HTML sitemap without an XML sitemap slows down content discovery by Google.
Building a readable sitemap: concrete structural criteria
A sitemap that lists two hundred links haphazardly serves no one. Readability relies on a few simple principles that many sites overlook.
Hierarchy and navigation depth
No useful page should be more than three clicks away from the homepage. Each additional level reduces the likelihood that a visitor will reach the page. The sitemap should reflect this hierarchy: main sections at the first level, subsections at the second, specific pages at the third.
Why three levels and not four or five? Because each additional click represents a moment when the visitor may abandon the search. Search engines follow the same logic: a deeply buried page receives less “link juice” and will rank lower.
Thematic grouping versus alphabetical order
Sorting pages alphabetically seems logical, but it forces the visitor to already know the exact name of what they are looking for. Thematic grouping (services, products, resources, legal information) guides the search even when the visitor cannot precisely articulate their need.
The sitemap should replicate the logic of the main menu, not contradict it. If the menu categorizes sections by type of service, the sitemap should follow the same order. An inconsistency between the two disorients more than it helps.
Dynamic pages and evolving content in the sitemap
Sites with a blog, news section, or product catalog pose a specific problem. Should each blog post be listed in the HTML sitemap?
The answer depends on the volume. A blog with around twenty articles can display them all. An e-commerce site with thousands of product listings cannot. In this second case, the HTML sitemap lists categories and subcategories, not each individual product. The XML sitemap takes over to signal all URLs to search engines.
- For active blogs, listing article categories is sufficient in the HTML sitemap. Archives by date or tag remain in the XML sitemap.
- For product catalogs, display product families in the HTML sitemap and delegate the details to the XML sitemap.
- For seasonal or temporary pages (promotions, events), remove them from the HTML sitemap as soon as they expire to avoid dead links.
A sitemap that contains links to deleted or redirected pages undermines visitor trust and sends a bad signal to search engines. Regularly checking that each link in the sitemap leads to an active page is part of basic maintenance.
Sitemap and internal linking: two tools that reinforce each other
The sitemap does not replace internal linking, and vice versa. Internal linking involves placing contextual links within the content of pages to guide the visitor to complementary pages. The sitemap provides a structured overview.
When both work together, the visitor always has at least two paths to reach any page: the contextual path (via links in the content) and the structural path (via the sitemap). This redundancy reduces navigation dead ends.
Search engines also benefit from this dual structure. A link in the sitemap confirms the existence of a page. A contextual link in an article reinforces its thematic relevance. The combined signals improve the understanding of the hierarchy by indexing bots.
A regularly updated sitemap, consistent with the navigation menu and complemented by thoughtful internal linking, remains the most reliable way to ensure no content remains orphaned. The European regulation on accessibility further reinforces this necessity: what was once a good practice is gradually becoming a documented obligation.