An HTML sitemap, an XML sitemap, and a site structure serve three distinct functions. A well-structured site map remains a navigation tool for human visitors, while the XML sitemap acts as a discovery signal for indexing bots. The site structure, on the other hand, pertains to upstream design: it is the logical schema that organizes the pages among themselves. Confusing these three layers leads to poorly directed technical choices and less readable navigation.
HTML Sitemap, XML Sitemap, Site Structure: Three Layers Not to Confuse
The HTML sitemap is a visible page, accessible from the footer or the menu. It lists the sections and subsections in a hierarchical order, allowing a visitor to find the page they are looking for in just a few seconds. It is not a duplicate of the main menu: its purpose is to provide a comprehensive view of the content.
The XML sitemap, on the other hand, is a technical file submitted to search engines. Google treats it as a URL discovery signal, not as an indexing directive. Pages missing from the XML sitemap but linked by strong internal links can still be crawled and indexed. Conversely, a URL present in the XML but orphaned from any internal link is unlikely to be valued.
Confusing the HTML sitemap with the XML sitemap is akin to assuming that a tool meant for bots replaces a tool meant for humans. A concrete example: on the sitemap of Bertrand Barré, each section appears in an ordered list that reflects the business logic of the site, not a raw export of all URLs. It is this distinction that makes the page useful for a visitor.
Keyboard Navigation and Accessibility: What the WCAG 2.2 Standards Change
Most web navigation guides treat accessibility as a checkbox. Publishing a sitemap would be enough to make the content accessible. The standards published by W3C in October 2023 (WCAG 2.2) show that the reality is more demanding.
Focus Visibility and Keyboard Interactions
The WCAG 2.2 adds criteria for keyboard focus visibility and proposes alternatives to drag-and-drop interactions. A sitemap page can be perfectly structured in semantic HTML and still be difficult to navigate via keyboard if the focus is not visible or if the tab order does not follow the visual hierarchy.
For screen reader users, the sitemap provides a comprehensive view of the site structure in one place, without navigating page by page. People with motor disabilities find direct access to a specific section, without having to tab through all the interactive elements that precede their destination.
Regulatory Obligations Since June 2025
Since June 28, 2025, the European Accessibility Act (directive 2019/882) applies to part of the private sector: certain online commerce, banking, transport, and telecommunications services. For these organizations, navigation is no longer just a user experience issue; it is a legal compliance issue.
A compliant HTML sitemap must therefore go beyond a simple list of links. It must respect the hierarchy of title tags, provide sufficient contrast, and ensure that each link is reachable and identifiable via keyboard.
Structuring a Sitemap That Truly Serves Navigation
Three common mistakes often occur in sitemaps published online:
- Listing all URLs on the site without distinction, including pagination pages, empty tags, or monthly blog archives, which drowns useful information in noise
- Reproducing the main navigation menu exactly, making the page redundant and without added value for the visitor who did not find what they were looking for via the menu
- Omitting dynamic content (blog posts, product sheets) that often represents the majority of the site’s pages and the main reason a visitor consults the sitemap
A useful sitemap reflects business logic, not technical structure. If a service site offers three main services, these three services should appear as first-level entries, even if they technically share the same template.
Pages to Include and Pages to Exclude
Structural pages (home, sections, subsections, service pages) and editorial content (articles, guides, case studies) deserve to be included. Utility pages (legal notices, privacy policy, terms and conditions) can appear at the end of the list, visually separated.
On the other hand, internal search results pages, filter pages, and URLs with parameters do not belong in an HTML sitemap. They do not help the visitor and dilute readability.
Internal Links and Sitemap: Complementary, Not Interchangeable
An HTML sitemap does not replace a coherent internal linking structure. Google uses internal links to understand the relationships between pages and distribute authority. The sitemap, on the other hand, serves as a safety net: it captures lost visitors and offers an alternative path to content.
Contextual internal links remain the primary lever for navigation and SEO. Every important page should be accessible within three clicks from the homepage, via links placed in the body text or in the menus. The sitemap comes into play when this architecture shows its limits, for example, on a site with several hundred pages.
- On a site with fewer than fifty pages, the HTML sitemap primarily serves an accessibility and compliance function
- On a site with several hundred pages, it becomes a full-fledged navigation tool, provided it groups content by clear categories
- In both cases, the sitemap update must follow the content update: a deleted page that remains listed in the sitemap generates a 404 error and undermines visitor trust
An outdated sitemap is worse than having no sitemap at all. Automatic generation via a CMS can solve this problem, but it requires regular manual checks to exclude pages that should not be listed.
The issue of web navigation is gradually shifting from comfort to regulatory compliance. With the enforcement of the European Accessibility Act, the organizations concerned have a concrete reason to review the structure of their sitemap, beyond SEO optimization or user experience.
