An HTML sitemap is more than a list of links stacked at the bottom of a page. It’s a structural component that reveals a website’s full hierarchy and, when properly maintained, becomes the most reliable shortcut to finding content without using the main menu or search bar.
RGAA criterion 12.1 and sitemaps: an accessibility requirement, not an ergonomic bonus
Under criterion 12.1 of the RGAA 4.1.2 standard, a website must provide at least two distinct navigation systems from among three options: a navigation menu, a sitemap, and a search engine. A sitemap is therefore not just a convenience feature, but one of the mechanisms specified by the standard to ensure access to content.
The standard checks three specific aspects of this page. Links must work, their labels must match the pages they point to, and the displayed hierarchy must reflect the site’s overall architecture. An outdated sitemap full of broken links or labels that no longer match the actual page titles does not meet the criterion.
The W3C reinforces this requirement by recommending consistent navigation options from page to page, alongside breadcrumbs and clear headings. An HTML sitemap on its own, without these additional signposts, is still useful but does not meet every navigation need.
To see a sitemap organized into topic-based categories on a site with a wide range of content, Animal Time’s sitemap is a good example of a clear hierarchy grouping sections and subsections.
HTML sitemap and XML sitemap: two files, two audiences
Confusion between these two formats persists, even among technical professionals. An XML sitemap is a file intended for search engine crawlers (Googlebot, Bingbot). It lists URLs along with metadata (last modified date, update frequency, relative priority). There’s no reason for human visitors to open this file: it appears as raw code, with no formatting or clickable links.
An HTML sitemap, by contrast, is a standard web page designed for visitors. It presents links organized into sections, often arranged hierarchically using nested lists. This is the page we recommend checking when the main menu isn’t enough to locate specific content.
A website can have a fully functional XML sitemap for Google and no HTML sitemap for its visitors. The reverse is also true. Each serves a different purpose, and one never replaces the other.
When a sitemap beats the menu and internal search
A website’s main menu rarely displays more than two levels of depth. On a site with several hundred pages, most content never appears in the menu. The search bar, meanwhile, assumes visitors know a relevant keyword, which isn’t always the case when they’re browsing without a specific goal.
A sitemap is especially useful in three situations:
- Exploratory browsing, when you want to discover the range of topics a site covers without entering a specific query. You can browse categories and find pages you didn’t know existed.
- Keyboard navigation or screen reader use, where a sitemap provides a linear list of links that’s easier to navigate than a dropdown menu with interactive submenus.
- Finding broken links: a sitemap that displays 404 errors immediately flags pages that have been deleted or moved, which the menu often conceals.
How to find and use the sitemap on any website
The sitemap page is usually found in the footer under a label such as “Sitemap” or “All pages”. On some sites, the link also appears on accessibility pages or in the legal notices.
If no link is visible, adding /plan-du-site or /sitemap to the end of the domain URL works in most cases. The complete absence of an HTML sitemap often indicates that the site has not undergone an accessibility audit.
Once you’re on the page, it’s easy to browse. Links are grouped by section, sometimes with indented sublists. Each link points to the corresponding page. Unlike an internal search engine, a sitemap doesn’t filter anything: it shows everything, making it easy to spot entire sections that regular visitors may never have explored.
Keeping a sitemap reliable: what to check
A sitemap loses its value if it isn’t kept up to date. Every page that’s created, renamed, or deleted should be reflected in the HTML sitemap. On popular CMS platforms (WordPress, Joomla, Drupal), plugins can generate this page automatically from the site hierarchy. Automatic generation doesn’t eliminate the need for regular checks.
What to check:
- No links lead to a 404 page or a redirect chain. A periodic crawl of the sitemap is enough to detect these issues.
- Link labels match the actual titles of the destination pages. A mismatch between a sitemap label and a page’s H1 title can confuse visitors and create an issue under the RGAA.
- The displayed hierarchy reflects the site’s actual structure. If categories have been merged or split, the sitemap should be updated accordingly.
- The sitemap page itself is accessible from every page on the site, via the footer or a persistent link.
A well-maintained sitemap remains one of the most reliable navigation tools on a website. It doesn’t depend on a search algorithm or a complex JavaScript interface. It provides a complete, flat, navigable overview that can withstand visual redesigns as long as the site hierarchy remains consistent.
