An HTML sitemap is still the only component of a website that displays the entire site hierarchy on a single page. For users who already know the domain they’re visiting, it provides a direct shortcut to the resource they’re looking for, without having to navigate dropdown menus or use a search bar whose results depend on the site’s internal algorithm. Understanding how it is structured makes it far more useful than simply scanning it visually.
Tab order and semantic structure of an HTML sitemap
A properly marked-up sitemap uses nested lists (ul/li lists ordered by hierarchical level). Each nesting level represents a tier in the site hierarchy: main sections, subsections, and individual pages. This structure is not merely decorative. It determines how screen readers present the information and how keyboard navigation moves from one link to the next.
When the markup is clean, the Tab key follows the logical order of the site hierarchy. Keyboard users can reach the desired subsection in just a few keystrokes, without having to move through every interactive element in the header or footer. If the sitemap uses heading tags (h2, h3) to separate major sections, screen readers let users jump directly from one group of links to another.
WCAG 2.2’s “Multiple Ways” criterion requires websites to offer several ways to locate a page (navigation, search, and a sitemap). An HTML sitemap meets this requirement as long as every link has a unique, descriptive label. A generic label such as “Learn more” repeated ten times makes the sitemap unusable for anyone navigating by link list.
HTML sitemap and XML sitemap: two distinct uses for navigation and indexing
These two formats are often confused. An HTML sitemap is a standard web page for human visitors that lists internal links in a hierarchical structure. An XML sitemap is a technical file intended for crawlers. Google follows links in an HTML sitemap just as it does on any other page, but XML remains the recommended format for notifying search engines of the URLs to crawl.
In practice, a small website with a few dozen pages benefits directly from an HTML sitemap: every page is accessible with one click from a single URL.
On a large website, the HTML sitemap serves as a navigation aid alongside the XML sitemap, which manages crawl priorities and update frequencies. For a practical example of this approach, The Infos du Geek sitemap displays its categories and articles in an easy-to-follow hierarchy without relying on the main menu.
There are therefore two distinct paths: visitors looking for a specific page use the HTML sitemap, while Googlebot uses the XML file to decide which URLs to crawl first. Keeping both up to date prevents broken links for users and indexing errors for search engines.
Use the sitemap to shorten the navigation journey
Most visitors reach a sitemap through the footer, or sometimes via a well-designed 404 page. Its effectiveness depends on how clearly the hierarchy is presented. Three practices make pages easier to find:
- Group links by business category rather than content type (articles, product pages, news). Visitors look for “billing” or “API,” not “blog post number 47.”
- Limit the visible hierarchy to three levels. Beyond that, the directory-like layout creates a wall of links that discourages visual scanning and slows down keyboard navigation.
- Use the browser’s built-in search function (Ctrl+F) on the sitemap page. This is still the fastest way to find a keyword in a long list of links, and it works without relying on the site’s internal search engine.
A well-structured sitemap makes internal search almost unnecessary on medium-sized websites. It displays the full range of content without algorithmic filtering or result limits.
Dynamic pages and evolving sections
Frequently updated sections (blogs, news, product catalogs) create a maintenance challenge. A manually generated sitemap becomes outdated as soon as an article is published or removed. Automatic generation through the CMS solves this problem, but introduces a risk: technical pages (tag pages, date archives, pagination pages) may be included, making the sitemap harder to read.
Filtering these pages in the sitemap template is a step that is often overlooked. Excluding date archives and tag pages reduces clutter and focuses attention on valuable content. Visitors browsing the sitemap aren’t looking for the “tag: performance” page; they’re looking for the “performance indicators” category and its related articles.
European Accessibility Act and the requirement for an accessible end-to-end journey
Since June 28, 2025, the European Accessibility Act has applied to certain online services, including e-commerce services aimed at consumers. Some microenterprises are exempt, but the scope of the Act is broad.
A sitemap can contribute to partial compliance. On its own, however, it is not enough: the entire journey, from search to payment, must be accessible. Testing the sitemap without checking that destination pages have a logical tab order, visible focus indicators, and a way to exit interactive elements leaves regulatory gaps.
We recommend auditing the sitemap alongside the critical pages in the conversion funnel. An accessible link in the sitemap that leads to a product page that cannot be used with a keyboard does not meet any accessibility requirements.
An HTML sitemap is no relic of the 2000s. It is a technical component whose effectiveness depends on semantic markup, filtering out unnecessary pages, and consistency with the rest of the user journey. On a well-maintained website, it remains the shortest path between visitors and the information they’re looking for.
