You arrive at a website to find specific information, and after three clicks in a dropdown menu that is too deep, you give up. The sitemap solves this problem by exposing the entire structure on a single page. It must be well-constructed, up-to-date, and serve both visitors and search engines.
XML Sitemap and HTML Sitemap: two files, two distinct functions
The confusion between XML sitemap and HTML sitemap remains common, even among technical profiles. The XML sitemap is a file intended for Google or Bing crawlers. It lists the URLs with metadata (last modified date, update frequency) to guide the crawl.
The HTML sitemap, on the other hand, is a web page readable by humans. It displays the site structure in the form of clickable links, organized by categories and subcategories. The two files do not replace each other: XML feeds indexing, HTML improves navigation.
On a site with a few dozen pages, the XML sitemap is often sufficient for SEO. However, as soon as the structure exceeds three levels of depth, an HTML sitemap becomes a valuable shortcut for users looking for a buried page. You can also observe how the Eklectik sitemap structures its categories to provide direct access to each section without going through the main menu.
Sitemap and web accessibility: what the European Accessibility Act changes concretely
Since June 28, 2025, the European Accessibility Act (EAA) applies to digital services sold to consumers in the European Union. The expected compliance aligns with the EN 301 549 standard, which is based on WCAG 2.1 level AA.
The HTML sitemap takes on a regulatory dimension here. For a screen reader user, navigating a site page by page represents a considerable cognitive effort. The sitemap provides an overview of the structure in one place, without tabbing through each interactive element.
The EAA also requires the publication of an accessibility statement and a user feedback mechanism. Having an up-to-date sitemap facilitates the audit: it ensures that each listed page is actually accessible via keyboard and compatible with assistive technologies.
Manual tests that automation cannot replace
Automated tools detect markup errors or insufficient contrasts. They do not capture the real experience of navigating with a keyboard or a screen reader. Keyboard testing and testing with a screen reader remain essential manual checks to assess the accessibility of a sitemap.
You navigate the sitemap using the Tab key, checking that each link is reachable and that the reading order corresponds to the visual hierarchy. If a link is skipped or if the focus disappears, the sitemap does not fulfill its function for the concerned users.
Building an HTML sitemap that truly serves navigation
A sitemap that reproduces the main menu word for word adds no value. Its interest lies in structured completeness: it shows pages that the menu does not display (deep pages, thematic landing pages, archives).
Pages to include and pages to exclude
- Structural pages (home, categories, subcategories) and main editorial content deserve to be included, organized by theme rather than in chronological order.
- Utility pages (legal notices, privacy policy, general terms and conditions) can appear in a separate section at the bottom of the sitemap, without cluttering the main hierarchy.
- Internal search results pages, duplicate filter pages, and pagination pages do not belong in an HTML sitemap. They create noise and dilute readability.
- For large blogs, articles should be grouped by category or year rather than listing each post individually.
Updating and consistency with the XML sitemap
An outdated HTML sitemap is worse than no sitemap at all: it generates broken links and degrades user trust. Every addition or removal of a page must be reflected simultaneously in both the HTML sitemap and the XML sitemap.
On a CMS like WordPress, plugins automatically generate the HTML sitemap from the structure. Feedback varies on this point: some plugins poorly handle custom content types or complex taxonomies. It is recommended to manually check the output after each major site update.
SEO impact of a well-structured sitemap on Google indexing
Google crawls a site by following internal links. When a page is orphaned (no internal links pointing to it), the bot cannot find it unless it appears in the XML sitemap. The HTML sitemap adds a layer of internal linking that enhances the discoverability of all pages.
This linking has a direct effect on the crawl budget. On a site with several hundred pages, an HTML sitemap reduces crawl depth by bringing each URL within two clicks of the homepage. The bot accesses more quickly the recent or updated content.
- Placing the link to the sitemap in the footer of all pages ensures it is accessible from any point on the site.
- Using descriptive anchors in the sitemap (no “click here”) helps Google understand the content of each target page.
- Structuring the sitemap with H2 or H3 titles by category allows search engines to better interpret the thematic hierarchy of the site.
The sitemap does not replace a well-thought-out navigation architecture from the design stage. It complements it by serving as a safety net for pages that, structurally, receive few internal links. A site with a clear structure from the outset benefits modestly from the HTML sitemap. A site with a deep structure or scattered content gains significantly more visibility on search engines.