A visitor arrives at an e-commerce site with a specific idea in mind, but the main menu only shows five generic categories. They scroll, go back, hesitate, and then leave the page. This scenario repeats every day on thousands of sites where the navigation structure relies solely on the main menu, without a sitemap page to provide an overview.
HTML Sitemap and XML Sitemap: Two Tools, Two Distinct Functions
The visible sitemap for visitors (an HTML page listing sections and subpages) is often confused with the XML sitemap intended for search engines. Both share the same name but serve opposite needs.
The HTML sitemap serves human visitors. It displays a readable hierarchy of all accessible pages, organized by theme or category. A user lost in a three-level menu can go directly to it to find the desired page without going through the traditional navigation.
The XML sitemap, on the other hand, is a technical file that crawlers read to discover URLs. It helps signal the existence of pages, but, as several specialized resources remind us, an XML sitemap does not guarantee indexing or ranking of a page. It does not replace a solid internal linking structure that gives pages their context and hierarchical relationships.
On the Bla Bla Bla sitemap, for example, we observe a clear thematic organization that allows browsing all content without relying solely on the navigation menu.
Confusing the two risks neglecting one in favor of the other. A site can have a perfectly configured XML sitemap and still leave its visitors without guidance when they are looking for a specific page.
Navigation Structure: What a Sitemap Fixes When the Menu Is Not Enough
A well-designed main menu covers the most common paths. But as soon as a site exceeds a few dozen pages, some content becomes hard to access. Terms and conditions pages, old blog articles, specific subcategories: anything that does not fit into the five or six entries of the menu risks disappearing from the user journey.
The HTML sitemap comes in precisely at this point. It functions like a book index: it is not consulted first, but it becomes the solution when the table of contents is not sufficient.
Concrete Case: A Showcase Site with Niche Services
Let’s take a consulting firm that offers about ten services spread across three areas. The menu displays the three areas, but the individual services are only accessible after two clicks. A visitor who knows the exact name of the service they are looking for saves time by going through the sitemap, where all pages appear grouped and hierarchized.
The sitemap reduces the number of clicks to deep pages. It is a structural shortcut, not a substitute for the menu, but a complement that compensates for its limitations.
Impact on Internal Linking and SEO
Every link present in the HTML sitemap is an additional internal link. For pages that are poorly linked from the rest of the content, this page acts as a safety net: it distributes context and internal authority to URLs that lack them. Search engines follow these links like any others, which enhances the discoverability of orphan pages.
Building a Readable Sitemap: Sorting Criteria and Updates
A poorly organized sitemap becomes a mere lengthy list that no one consults. To fulfill its function, a few concrete principles must be respected.
- Group pages by logical category (services, products, resources, legal pages) rather than by chronological order of creation, which makes no sense to the visitor.
- Limit the display depth to two or three levels of hierarchy. Beyond that, the page becomes as complex as the menu it is supposed to simplify.
- Use link titles identical to the actual titles of the target pages. A different label creates confusion and harms the coherence of internal linking.
- Remove links to deindexed pages, redirects, or outdated content. A sitemap that points to 404 errors degrades visitor trust and sends a bad signal to crawlers.
Maintenance is the weak point of most sitemaps. It is created at launch and then forgotten. Every new page published should be added to it, and every deleted page should be removed from it. CMSs like WordPress allow for automatic generation of this page via dedicated plugins, but regular manual checks remain necessary to ensure that the result stays coherent.
Sitemap Accessibility: Regulatory Obligation and Real Use
Since June 28, 2025, the European Accessibility Act applies to certain digital services aimed at consumers, including e-commerce. For the affected sites, offering a sitemap provides an additional way to find a page, but it does not replace the accessibility of menus and navigation paths.
The WCAG criteria related to navigation stipulate that a site must offer at least two means of locating a page: the menu, internal search, sitemap, or contextual links. Providing an accessible sitemap (compatible with screen readers, structured with semantic HTML lists) allows ticking off one of these means without major development effort.
- Use list tags (
ul,li) rather than paragraphs or tables to structure the sitemap. - Add ARIA navigation attributes to the main container so that assistive technologies can identify the area.
- Ensure that each link is keyboard accessible, with a visible focus on each interactive element.
The directive provides an exception for certain microservice businesses, but the regulatory trend pushes towards generalization. Anticipating sitemap accessibility is more cost-effective than correcting it under pressure, especially for sites with several hundred pages.
A well-designed sitemap does not alone transform the navigation experience. It functions like a net: most visitors will never see it, but those who need it, whether lost, in a hurry, or using assistive technology, find exactly what they are looking for.
