On most websites, the sitemap exists somewhere, often relegated to the footer, rarely consulted by visitors. Search engines use it to index content, but from the user’s perspective, this page remains a blind spot. Its usefulness is not limited to SEO: it can concretely change the way a user finds information, especially when the main menu is no longer sufficient.
Keyboard Navigation and Screen Readers: What the Sitemap Changes
Dropdown menus, mega-menus, and dynamic filters regularly pose problems for people navigating via keyboard or using a screen reader. A submenu that opens on mouse hover becomes inaccessible without a pointer. A faceted filter that reloads the page without warning the screen reader disorients the user.
The HTML sitemap offers a direct alternative. It presents all pages as static links, organized by category. A keyboard user can navigate the entire structure using the Tab key, without relying on complex interactions.
The WCAG 2.2 recommendations emphasize providing multiple ways to access the same page: main menu, search bar, breadcrumb trail, and sitemap. The latter does not replace any of the others but complements them by offering a comprehensive and predictable view. For a site whose structure often evolves, it serves as a safety net that ensures no section becomes orphaned from the perspective of human navigation.
By consulting the Aura Blog sitemap, one can observe how a structure of varied content can remain readable thanks to clear thematic grouping, without resorting to dynamic filters.
European Accessibility Act and Navigation Obligations: The Framework Tightens
Since June 28, 2025, the European Accessibility Act strengthens the obligations applicable to certain digital services in the European Union, particularly e-commerce. The relevant journeys must allow keyboard navigation, the use of screen readers, and comprehensible access to search, filtering, and ordering functions.
A sitemap alone is not enough to make a site compliant. The requirements cover the entire user journey: forms, payment processes, catalog consultation. However, the sitemap helps provide a clear access route to a site’s content and services, which accessibility audits evaluate as a positive criterion.
Automated Tests and Manual Tests: Two Distinct Checks
Automated audit tools (Lighthouse, axe, WAVE) detect markup errors, insufficient contrasts, and images without alt attributes. They do not verify whether a real user can navigate from one page to another without getting lost.
Recent recommendations advocate combining these tests with manual trials using a keyboard and a screen reader. A properly structured sitemap facilitates these manual checks: it ensures that each section of the site remains reachable by at least two distinct paths.
- The main menu provides access to top-level categories but not always to buried sub-pages.
- The search bar assumes that the user already knows the exact term to search for.
- The sitemap lists all pages without requiring prior knowledge, making it a neutral starting point for exploring an unknown site.
HTML Sitemap vs. XML Sitemap: Two Audiences, Two Functions
The confusion between these two formats persists. The XML sitemap is a technical file intended for indexing robots. It contains raw URLs, sometimes accompanied by metadata (last modified date, for example). No human visitor has any interest in consulting it.
The HTML sitemap is a standard web page designed for internet users. Its value lies in the readability of the organization it offers, not in technical completeness. A good HTML sitemap groups content by theme or type, with understandable headings. A poor HTML sitemap merely lists hundreds of URLs without hierarchy, which amounts to reproducing an XML file in the browser.
The distinction has practical consequences. An e-commerce site with thousands of product listings has no interest in displaying all of them in an HTML sitemap. However, displaying main categories, help pages, terms and conditions, and contact pages in a structured HTML sitemap allows a disoriented visitor to find their way in seconds.
When the Sitemap Reveals Flaws in a Structure
Building an HTML sitemap forces one to look at the structure as a whole. This exercise highlights problems that daily navigation masks.
Important pages buried three or four clicks from the homepage become immediately apparent when searched for in a sitemap. Content duplicates become visible when noticing that two different URLs lead to nearly identical pages. Entire sections, created during a previous redesign and never deleted, stand out as dead branches.
The sitemap then functions as a diagnostic tool. For an editorial manager or webmaster, consulting it regularly allows them to spot:
- Orphan pages, accessible only by their direct URL and absent from any menu.
- Naming inconsistencies between categories (a “Help” section and a “Support” section covering the same scope).
- Outdated content that remains indexed without providing value to visitors.
Keeping a sitemap updated amounts to continuously auditing the structure, without mobilizing external tools or specialized providers. The page itself becomes a faithful reflection of what the site actually offers, not what it was supposed to offer at the time of its initial design.
A site with an updated and readable sitemap sends a simple signal: its structure has been designed so that every piece of content remains findable. This is a criterion that neither algorithms nor human visitors directly penalize, but that both reward with shorter navigation times and lower bounce rates on deep pages.
