A sitemap is one of the least visible elements of a website, yet it directly affects how easily visitors can find what they’re looking for.
When the main navigation fails, the menu doesn’t cover every section, or a user lands on a deep page with no clear way to find their bearings, the sitemap steps in. Its role goes beyond simply listing links: it presents the entire site architecture in one place.
HTML sitemap and XML sitemap: two different tools with distinct purposes
Most websites still confuse an HTML sitemap (intended for visitors) with an XML sitemap (intended for search engines). The former is a page that people can browse, organized by section and offering an overview of the site hierarchy. The latter is a technical file submitted to search engine crawlers.
An XML sitemap helps search engines discover URLs, but it does not guarantee that they will be crawled or indexed. Google Search Central also states that Google does not take the priority and changefreq fields into account. Only the lastmod date may have an effect, provided it reflects a genuine change to the page.
An HTML sitemap serves a different purpose: it helps visitors who have lost their way find a page without using the menu or search bar. A practical example of this approach can be found in the La Fermette De Marie sitemap, which displays all the sections in a structure that’s easy to scan at a glance.
Confusing the two means neglecting one or the other. A site can have a flawless XML sitemap while leaving visitors with no visible structural signposts.

Accessibility and keyboard navigation: the practical difference a sitemap makes
Screen reader users navigate a site linearly. Exploring every section, submenu, and interactive link to understand a site’s structure takes considerable effort. A sitemap removes this step by displaying the entire site hierarchy on a single page.
For people who navigate exclusively by keyboard (because of a motor disability or personal preference), the benefit is tangible. Instead of tabbing through every interactive element in a dropdown menu, they can go straight to the section they want from the sitemap.
Since June 28, 2025, the European Accessibility Act has applied to certain consumer-facing services, including e-commerce. Its scope depends on the service provided, and some exemptions apply, but the regulatory trend is clear. WCAG 2.2, published by the W3C on October 5, 2023, adds a criterion on focus visibility: an interactive element must not be obscured by other content when it receives keyboard focus.
A well-designed sitemap naturally meets this requirement: every link is visible and reachable by keyboard, with no overlapping content. A sitemap alone is not enough to make navigation accessible, but its absence makes navigation significantly harder for the users concerned.
HTML sitemap structure: the choices that matter
Not all sitemaps are equally useful. A flat list of hundreds of links with no hierarchy helps no one. How the content is organized determines how useful the page really is.
Pages to include and pages to leave out
A sitemap is not a duplicate of the navigation menu. It should provide a comprehensive yet readable overview. Include:
- Structural pages: the homepage, main sections, subsections, and category pages. These are the nodes in the site hierarchy that help visitors understand how the site is organized.
- High-value content pages: cornerstone articles, guides, and service pages. The aim is to make it easy to find content visitors are actively looking for.
- Legal and utility pages: legal notices, privacy policy, and contact page. Often buried in the footer, these deserve a place in the sitemap for the sake of transparency.
By contrast, internal search results pages, pagination pages, and filter URLs do not belong in an HTML sitemap. They make the page longer without adding any navigational value.
Visual hierarchy and grouping
Organizing pages by level (sections, then subsections, then pages) mirrors the site hierarchy. Using nested lists in native HTML allows screen readers to convey this structure. A sitemap built with tables or visual blocks that lack semantic structure loses this compatibility.
The number of visible levels also matters. Readability drops beyond three levels of nesting. For larger sites, grouping pages by topic rather than by technical depth makes the structure easier to understand.

Automatically generating or manually building a sitemap
Most CMS platforms offer plugins that can automatically generate an HTML sitemap. WordPress, for example, has several dedicated plugins. The advantage is clear: every newly published page appears without any manual intervention.
The drawback is that this approach lacks editorial filtering. A plugin generates a raw list of every published page, including those that are of no interest to visitors (tag pages, monthly archives, orphan pages). An automatically generated sitemap almost always needs manual filtering to remain useful.
Manual creation, on the other hand, gives you full control over which pages to include and how to organize them. It works well for smaller sites (a few dozen pages) where updates are manageable. For sites with more than a hundred pages, maintaining the sitemap manually becomes a disproportionate burden.
A hybrid approach often works best: generate the sitemap automatically while excluding unnecessary categories, then periodically check that the result is consistent.
Known limitations of sitemaps as a navigation tool
A sitemap does not replace a well-designed menu, an internal search engine, or contextual links between pages. It acts as a safety net, not as the primary navigation channel.
Data on how often visitors actually consult HTML sitemaps remains scarce in publicly available research. Few public studies measure actual visits to this page compared with other navigation methods. This lack of data makes it difficult to make definitive claims about its impact on conversions or time spent on the site.
What is documented, however, is accessibility: the WCAG guidelines and France’s RGAA accessibility framework explicitly recommend providing a sitemap as a supplementary navigation mechanism. A sitemap’s value lies more in helping specific user groups find their way than in delivering a measurable benefit across all site traffic.



