Most websites offer a main menu, an internal search engine and sometimes a breadcrumb trail. The sitemap, however, remains a separate page: an organized list of all accessible URLs, presented as a hierarchy. It serves two purposes. For visitors, it provides an overview of the site’s architecture on a single screen.
For search engines, it makes it easier to discover pages that may not have enough internal links pointing to them. WCAG 2.2 Success Criterion 2.4.5 also requires that each page can be found by more than one method, and a sitemap provides one of these alternative routes.
HTML sitemap and XML sitemap: two formats, two functions
Confusion between these two formats persists. An HTML sitemap is a standard web page, readable by people, that lists sections and subpages with clickable links. An XML sitemap is a technical file intended for search engine crawlers, submitted through Search Console or referenced in the robots.txt file.
Neither replaces the other. The XML format helps search engines discover URLs, but submitting a URL in a sitemap guarantees neither crawling nor indexing. Google makes this clear in its documentation: a sitemap is a signal, not an instruction. The HTML format, on the other hand, serves visitors looking for a page without knowing the exact route through the menus.
Browsing the Mister Tendance sitemap illustrates this approach: each section is listed with its subcategories, making it possible to find a specific section in seconds without going through the main menu.
HTML sitemap structure: what actually helps visitors navigate
A sitemap is more than a raw export of every URL on a website. The pages worth listing are those that structure the information: main sections, subsections and high-value content pages. Technical pages (filter results, pagination pages, legal notices) make the sitemap harder to read without providing useful signposts.
Visual organization matters just as much as content. A clear hierarchy, with indentation levels or topic-based groupings, lets visitors scan the page like a table of contents. Three principles make a sitemap genuinely useful:
- A logical hierarchical structure that mirrors the menu structure but is more comprehensive, including deeper pages not shown in the menu
- Clear link labels that match or closely resemble page titles, so visitors know exactly where they will land when they click
- Regular updates to reflect added and removed content; otherwise, the sitemap may lead to 404 errors
An outdated sitemap is worse than no sitemap at all. It frustrates visitors and sends search engines conflicting signals about which pages are actually active.
What an XML sitemap doesn’t do for users
An XML sitemap contains optional fields such as lastmod, priority and changefreq. In practice, Google does not take the priority and changefreq fields into account. The lastmod date is only useful if it reflects a genuine change to the content. Updating every date with each deployment makes them meaningless.
These technical details are invisible to visitors. An XML sitemap does not generate a page they can browse. This is precisely where the HTML sitemap remains useful: it turns the technical architecture into a practical navigation tool.
An HTML sitemap remains the only format that serves both search engines and visitors. XML only meets half the need.
Accessibility and sitemaps: an underrated tool for keyboard navigation
Screen reader users navigate a website sequentially. Exploring each section to understand the site hierarchy takes time and requires considerable cognitive effort. A sitemap provides an overview of the site hierarchy in one place, without requiring visitors to go through every interactive menu item.
Keyboard users, whether they have a motor disability or are advanced users, can use it as a direct shortcut to a specific section. Instead of tabbing through dozens of navigation items, a single link in the sitemap takes them to their destination.
WCAG 2.2 does not explicitly require a sitemap, but Success Criterion 2.4.5 calls for multiple ways to locate a page within a set of pages. A sitemap meets this requirement alongside the internal search engine and navigation menu.
When a sitemap isn’t enough: known limitations
On a website with several thousand pages, the HTML sitemap itself becomes difficult to navigate. Once it contains more than a few hundred links, the page becomes harder to read and its navigation benefits are lost. Some websites address this by splitting the sitemap by category or section, but this approach adds clicks and undermines the benefit of seeing the whole structure at a glance.
For dynamic content (blog posts, frequently updated product pages), manual sitemap maintenance quickly becomes unrealistic. CMS platforms offer plugins that generate this page automatically, but quality varies. An automatic generator that lists URLs without following the section hierarchy produces a flat document that offers little value to visitors.
The question of granularity remains open: should every blog post be listed, or just the categories? The answer depends on content volume and visitor behavior—two factors that analytics tools can measure, but that generic recommendations cannot resolve.
A sitemap remains a navigation aid, not a substitute for well-designed menus. Its real value can be measured by how many visitors actually use it to reach a page—a metric that is rarely tracked but easy to configure in an event-tracking tool.
