When a website contains dozens of pages, finding specific information can quickly become a chore. The sitemap, often relegated to the footer, offers a direct shortcut to every section. But it needs to be clear, logical and accessible to all types of visitors, including those who navigate with a keyboard or screen reader.
HTML sitemap and XML sitemap: two tools not to be confused
The term “sitemap” refers to two distinct things. The first is an HTML page, visible to visitors, that lists the site’s sections and internal links. The second is an XML file intended for search engines.
An XML sitemap does not replace a visible sitemap. This file is used only to notify crawlers of URLs. Google may not even download it, and submitting it guarantees neither that the listed pages will be crawled nor that they will be indexed.
One other technical detail: Google ignores the “priority” and “changefreq” fields in XML files. It only takes the “lastmod” value into account, provided it reflects an actual change to the content. Updating this date after a simple footer change sends a misleading signal. To see how a professional structures a navigation page, Com 2 Net’s sitemap is a good example of internal links grouped by topic.
An HTML sitemap, on the other hand, is designed for visitors. It lets them see a site’s full structure and reach any page in one or two clicks. It’s a navigation tool that complements the main menu and search bar.

Sitemap accessibility: keyboard navigation and screen readers
Have you ever tried navigating a website using only the Tab key? On a poorly designed sitemap, you have to reach every link one by one, with no landmarks or shortcuts. For someone using a screen reader, it’s like searching for a word in a book with no table of contents.
The WCAG 2.2 guidelines specify that a website must offer multiple ways to find a page: navigation, search or a sitemap. This requirement has taken on added importance since June 28, 2025, when the European Accessibility Act began applying to online commercial services for consumers (excluding microenterprises providing services).
An accessible sitemap is more than just a comprehensive list of links. WCAG 2.2 also covers keyboard access, a logical navigation order, descriptive page titles and consistent navigation. In practice, here’s what this means for sitemap design:
- Group links by section under H2 or H3 headings so screen reader users can jump from one group to another without going through every link
- Make sure every link has a descriptive label (no “click here” or “learn more”) and that the order in the HTML code matches the visual order
- Check that all links can be reached using the keyboard with the Tab key, and that focus is visible (with an outline or highlight) so users can see where they are
- Don’t use scripts that block keyboard navigation or hide sections by default without allowing users to expand them using the keyboard
A sitemap that follows these principles becomes a real safety net: when the menu isn’t enough or search returns too many results, the sitemap offers a structured, predictable overview.
Hierarchy and grouping: designing a clear sitemap
A sitemap that lists three hundred links with no clear structure is no help to anyone. Good design starts with the content hierarchy.
Each main section should have a visible heading (an H2 on the sitemap page). Under each heading, list the subpages in a logical order: from general to specific, or chronologically if that suits the content.
Limit the structure to three levels
Beyond three levels of nesting, the content becomes confusing to read, both visually and with a screen reader. If your site structure goes deeper, it’s often a sign that some pages should be grouped together or removed.
Here’s a practical example. A company website features services, case studies, a blog and corporate pages. The sitemap displays four clearly separated blocks. Under “Services,” each offering has its own link. Under “Blog,” articles are grouped by topic, not by date. This topic-based grouping lets visitors scan the page in seconds.
Use precise link labels
A label like “Page 1” or “Article from March 12” tells visitors nothing. Link text should describe the content of the destination page. “Annual maintenance pricing” is more useful than “Our prices.” This level of detail also helps with SEO, since search engines analyze the text of internal links.

Mobile sitemaps: adapt the experience without sacrificing structure
On a phone screen, a long list of links quickly becomes hard to read. Two adjustments can make all the difference.
First, use collapsible sections. Each main section displays its heading, and a tap expands the subpages. Visitors can go straight to the section they’re interested in without scrolling through the whole page. However, make sure these sections can also be expanded using the keyboard, not just by touch.
Second, make clickable areas larger. On mobile, links that are too small can lead to mistaps. Providing sufficiently large touch targets for each interactive element helps prevent accidental clicks.
- Test the sitemap with a physical keyboard connected to a phone or tablet to check that Tab navigation works
- Check that the sitemap displays correctly in both landscape and portrait mode
- Make sure the text remains readable without horizontal zooming and that the font size is large enough
A well-designed sitemap is no mere accessory. It’s a structured entry point that complements the menu and search, while making the site usable for visitors with a range of needs. Sometimes the most useful page on a website is the one we forget to take care of.



