A sitemap lists all the pages on a website on a single HTML page. It should make it possible to find information in seconds. In practice, many sitemaps are little more than flat lists of vague links, and their real usefulness depends on factors most visitors never check.
The W3C recommends offering multiple ways to access content (a menu, internal search, and a sitemap) because each serves a different need. Determining which works best for different visitor profiles means comparing these three paths against concrete criteria.
Sitemap, menu, and internal search: what each does better than the others
Visitors generally have three navigation tools available when they arrive on a website. Each is best suited to a different purpose, and confusing them means looking in the wrong place.
| Criterion | HTML sitemap | Main menu | Internal search |
|---|---|---|---|
| Type of need | Overview and browsing without a specific query | Quick access to main sections | Specific query using a known keyword |
| Number of visible pages | All indexed pages, sometimes several hundred | Limited to first- and second-level categories | Varies depending on the quality of the search engine |
| Usefulness for a first-time visitor | High if the hierarchy is clear, low if the list is flat | Moderate (depends on how labels are worded) | Low if the visitor is unfamiliar with the site’s terminology |
| Keyboard accessibility | Good if focus is visible on every link | Depends on the component (dropdown menus are sometimes inaccessible) | Generally good |
| Deep or orphaned pages | Directly accessible | Often missing | Found only if well indexed by the internal search engine |
A sitemap is especially useful when visitors are unsure exactly what they are looking for or want to see the full range of available content. The Expertise Entreprise sitemap illustrates this principle: each section is grouped by topic and given a descriptive label, making it easy to find a page without knowing the exact term to search for.

Keyboard accessibility and visible focus: the test no one does
A sitemap can contain dozens of links. If a visitor navigates using a keyboard (the Tab key), each link needs a visible focus indicator so they can tell where they are on the page. Without one, navigating a list of links by keyboard is like searching in the dark.
The check takes less than a minute. Open the sitemap, put your hands on the keyboard, and press Tab. Two observations are enough to assess its quality:
- Is the active link surrounded by a visible outline, or does the cursor seem to disappear between items? If there is no outline, keyboard users lose their place in the navigation
- Does the tab order follow the page’s visual layout, or does focus jump between sections without any clear logic?
- Can groups of links (by category or topic) be identified using the keyboard, for example through section headings that organize the list?
This test reveals whether the sitemap is a genuine navigation tool or merely a technical artifact. A sitemap that is inaccessible by keyboard excludes visitors who use assistive technologies, as well as those who prefer using a keyboard out of habit.
Sitemap hierarchy and labels: the two factors that speed up searches
Having a sitemap does not guarantee that it helps visitors find anything. Two elements determine how effective it really is.
Grouping by section instead of using a flat list
A sitemap that displays every page in a single alphabetical list forces visitors to read every label. Clearly grouped sections cut search time because visitors can first rule out irrelevant categories before browsing the remaining links.
The sitemap’s hierarchy should reflect the website’s actual organization. If a “Services” section contains three subcategories in the menu, the sitemap should mirror that structure. Any mismatch between the sitemap and the menu creates confusion.
Descriptive labels instead of file names
A link labeled “page-2024-03” tells visitors nothing. A link labeled “2024 Accounting Support Rates” lets them decide in a second whether to click. A link label should describe the content of the destination page, not its technical location.
This rule may seem obvious, but many automatically generated sitemaps use URL slugs or page titles truncated by a CMS. Checking the labels after automatic generation prevents this problem.

Testing a sitemap with first-time visitors: a simple protocol
The W3C recommends offering multiple navigation paths. But how can you tell whether a sitemap works for visitors who are unfamiliar with the website? A simple test can provide concrete answers.
Ask three people who have never visited the website to find a specific page (for example, a contact page or a particular product page). Give them three instructions in sequence: first use the menu, then internal search, and finally the sitemap. Time each attempt.
The results generally show that the menu is enough for top-level pages, while internal search is better for specific queries. The sitemap stands out in one particular case: when visitors are looking for a deep page but do not know its exact name.
- If the sitemap takes longer than the menu to find main pages, its hierarchy is probably too dense or poorly organized
- If the sitemap takes longer than internal search to find a deep page, its labels are not precise enough
- If a keyboard user cannot reach the target link in fewer than about twenty tab presses, the sitemap is too long and lacks intermediate structure
This protocol requires neither a budget nor specialized tools. It provides enough data to decide whether the sitemap needs restructuring or whether efforts should focus on the menu or internal search engine.
A page accessible through the sitemap can still be isolated if no contextual links point to it from other content. A sitemap is a shortcut, not a substitute for internal linking. Pages found through the sitemap but never linked to elsewhere on the website point to a structural problem that goes beyond the sitemap itself.



