A visitor arrives at an e-commerce site to find a product page they viewed the day before. The main menu offers eight categories, each with subcategories. After three unsuccessful clicks, they leave the page. A link to an HTML sitemap would have saved them this frustration by displaying the entire site structure on a single page.
HTML sitemap and XML sitemap: two tools that serve different purposes
The sitemap intended for visitors (an HTML page listing categories and subcategories) is often confused with the sitemap.xml file intended for search engine crawlers. Google clearly distinguishes between the two: the XML sitemap helps search engines crawl a site, while the HTML sitemap supports human navigation.
Submitting an XML file to Search Console does not remove the need to provide an HTML sitemap. Including a URL in an XML sitemap guarantees neither that it will be crawled nor that it will be indexed. Internal links, page structure and the HTML sitemap remain separate ways to guide visitors and crawlers.
For a concrete example of a page that organizes its sections clearly, the Entrevue Web sitemap gives you a good idea of what a clear, up-to-date site structure can look like.
How to spot problems with an HTML sitemap
Before you can fix anything, you first need to identify the signs of a poorly designed sitemap. The same issues crop up on sites of all sizes.
Signs of an unusable sitemap
- The page lists hundreds of URLs with no category groupings. On an e-commerce site, visitors are faced with a wall of links and no idea where to start.
- Link labels use technical slugs (“/cat-2/sub-7/item-443”) instead of clear, descriptive names. Visitors cannot tell what they will find behind each link.
- The sitemap is out of date: links lead to deleted or redirected pages. Every 404 error encountered through the sitemap undermines visitors’ trust.
- The sitemap link moves around from page to page or disappears from certain sections. RGAA (criterion 12.1) requires that the feature leading to the sitemap be available in the same location across all relevant pages.
If two of these issues are present, the sitemap is not doing its job. It becomes a technical artifact that nobody uses.

Structure a sitemap that works for visitors and screen reader users
An HTML sitemap does not need to list every URL on the site. For an e-commerce site, organizing it by main categories is enough: visitors can then navigate to product pages from those categories. The goal is to provide a clear starting point rather than an exhaustive list.
Visual and semantic hierarchy
Structure the sitemap with nested lists (ul/li) that mirror the site’s actual hierarchy. Each level of depth corresponds to a level of nesting. Screen reader users benefit directly from this structure: they can navigate the entire hierarchy without having to explore each section individually.
Link labels should match page titles as they appear in the main navigation. Don’t rephrase or abbreviate them. Visitors who spotted “Buying guides” in the menu should find exactly the same label in the sitemap.
Pages to include and exclude
Include key structural pages: the homepage, categories, subcategories and service pages (contact, legal notices, privacy policy). Exclude pages that do not help visitors navigate the site: internal search results, automatically generated tag pages and pagination pages.
For dynamic sections such as a blog, listing article categories rather than every article individually keeps the sitemap manageable. Otherwise, a blog with three years of archives would produce an unreadable sitemap page.
Sitemaps and RGAA compliance: a practical accessibility requirement
A sitemap is not just an ergonomic bonus. RGAA 4.1.2, under criterion 12.1, requires a site to provide at least two of three navigation systems: a navigation menu, a search engine and a sitemap.
For a brochure site without a search engine, the sitemap becomes the second required navigation system. Keyboard users (people with motor disabilities and advanced users) can access any section directly without tabbing through every interactive element that comes before their destination.
Compliance is not just a matter of having a page titled “Sitemap.” The link must appear consistently in the same place from one page to another. A link in the footer on the homepage that is missing from interior pages does not meet the RGAA consistency requirement.

Automatically generating or manually building a sitemap
On a CMS such as WordPress, plugins can generate an HTML sitemap from the existing site structure. This saves time, but the quality of the result depends entirely on how well the site structure has been organized beforehand.
A site with poorly named categories or orphaned pages that have never been removed will produce an automatic sitemap that exposes all these problems. Automatic generation works well when the site architecture is already clean. Otherwise, a manually built sitemap lets you filter what deserves to be included.
The choice also depends on how often the site is updated. A site that publishes daily is better off automating sitemap generation, so a page created on Monday is not missing from the sitemap on Tuesday. A brochure site updated twice a year can use a static sitemap, checked with each update.
The HTML sitemap remains one of the few navigation features that benefits hurried visitors, users of assistive technologies and search engines alike. It takes little time to create when the site structure is well organized, and its absence costs visitors clicks.



