A sitemap serves a specific purpose: to provide an overview of all accessible pages, grouped by topic or hierarchy. The question is not whether to create one, but what sets a genuinely useful sitemap apart from a simple list of links that nobody uses. Several technical and usability criteria distinguish the two.
HTML sitemap and XML sitemap: what each format brings to navigation
These two formats are often confused. Their roles complement each other, but they serve different audiences.
| Criterion | HTML sitemap | XML sitemap |
|---|---|---|
| Primary audience | Human visitors | Search engine crawlers |
| Location | Page accessible from the footer or menu | File hosted at the server root |
| Content | Clickable links organized by section | Raw URLs with metadata (last modified date, priority) |
| Direct impact on user navigation | Yes: shortcut to any page | No: invisible to visitors |
| SEO impact | Indirect (internal linking, accessibility) | Direct (facilitates crawling and indexing) |
A site that offers only an XML sitemap, with no dedicated HTML page, deprives visitors of a useful way to find their bearings. Conversely, an HTML sitemap without an XML sitemap makes it harder for search engines to discover new pages. The two formats work together; neither replaces the other.
For a concrete example of a page that brings together all the sections of a real estate website, the Loge Toi sitemap is a good illustration of this approach to organizing content into clearly labeled categories.
WCAG criteria and keyboard navigation: what a sitemap cannot compensate for on its own
Accessibility standards (WCAG) require that users have multiple ways to locate a page on a website. A sitemap is one of them, but it cannot be the only one. Internal search, the main menu, and breadcrumbs are the other expected routes.
One point rarely mentioned in navigation guides is consistency of order. WCAG criterion 3.2.3 requires repeated navigation mechanisms to appear in the same relative order from one page to another. A menu that changes its layout across different sections of a site can make it harder for users to find their way, even if a sitemap is available.
Common obstacles for keyboard users
WCAG 2.2 introduces a Level AA requirement: an element with keyboard focus must not be obscured by fixed content. Sticky headers, cookie banners, and overlaid chat windows are the most common causes of this problem.
A sitemap that is keyboard-accessible is not enough if the rest of the navigation blocks users from moving through the site. Manual testing is still necessary to check that focus is visible and every link can be reached without a mouse.
- Check that keyboard focus is visible on every sitemap link (with a distinct outline or color change)
- Make sure no fixed banner (cookie notice, sticky header) covers the active link when tabbing through the page
- Check that the tab order follows the page’s visual layout, from top to bottom and left to right
Building an effective sitemap: hierarchy, depth, and updates
A sitemap that lists dozens of pages without grouping them simply recreates the problem it is meant to solve. Readability depends on three design choices.
How deep the displayed site structure goes
Displaying every level of the site structure creates clutter. Limiting the display to two or three levels deep lets visitors scan the structure without getting lost. Lower-level pages remain accessible from their parent sections.
A content site with several hundred articles gains nothing by listing them all in its sitemap. Grouping them by category and displaying only the subcategories is enough to help visitors find their way.
Excluding pages that do not help with navigation
Legal notices, privacy policies, and terms and conditions do not belong in a sitemap intended for navigation. They are already listed in the footer. Including them makes the sitemap harder to scan for visitors looking for a content section.
Similarly, internal search results pages, pagination pages, and rarely used tag pages add clutter without providing any benefit.
Update frequency
An outdated sitemap is worse than no sitemap at all. Broken links or removed sections frustrate visitors and send a negative signal to search engines. Popular CMS platforms (WordPress, Drupal) offer plugins that automatically regenerate the HTML sitemap whenever a page is published or deleted.
Measurable signals: how to tell whether your sitemap is doing its job
A well-designed sitemap produces measurable effects in analytics data.
- The exit rate from the sitemap page should be low: if visitors leave the site from this page, they have not found what they were looking for
- The number of pages viewed per session after visitors use the sitemap should be higher than the site average
- Deep pages that receive traffic only through the sitemap point to an internal linking problem elsewhere in the navigation
- 404 errors caused by clicks on the sitemap reveal a mismatch between published content and the sitemap page
These metrics help distinguish a decorative sitemap from a genuine navigation tool. The most useful sitemap is one visitors should almost never need to use, because the main navigation already works well. Its value becomes clear when the usual routes fail.
