A sitemap lists all the pages on a website on a single page. Its purpose may seem simple, but most sitemaps published online serve neither visitors nor search engines because they reflect the company’s internal organizational chart rather than the way users navigate. Creating a clear sitemap means starting with visitors’ actual journeys, not the technical site structure.
XML sitemap and HTML sitemap: two distinct functions
Confusion between these two formats explains why so many sitemaps are ineffective. An XML sitemap is a file intended for crawlers. It helps Google or Bing discover URLs, but visitors never consult it.
An HTML sitemap, on the other hand, is a visible page that visitors can browse. It shows how content is connected, which an XML file does not. Google notes that a well-linked site makes its pages easier to discover, but this linking comes first and foremost from visible internal links, not from the XML sitemap alone.
| Criterion | XML sitemap | HTML sitemap |
|---|---|---|
| Audience | Search engine crawlers | Human visitors |
| Location | File at the server root | Page accessible from the footer |
| Content | List of raw URLs with metadata | Links organized by topic or category |
| Navigation impact | None for users | A fallback when the menu isn’t enough |
| SEO impact | Helps discover isolated URLs | Strengthens visible internal linking |
A practical example of a well-structured HTML sitemap: the Le Pavé Numérique sitemap groups pages into easy-to-understand categories, using clear labels rather than technical URLs.

Orphan pages: the problem a sitemap reveals
A page included in an XML sitemap but with no internal links from the menu, footer, or contextual content remains practically invisible to visitors browsing the site normally. These orphan pages are a common blind spot.
Before building an HTML sitemap, take inventory of all your pages. For each one, note how a visitor can access it: the main menu, a submenu, a link in an article, or the footer. A page with no internal path to it doesn’t exist for your visitors, even if it appears in search results.
- List every published page and identify its entry point (menu, contextual link, footer)
- Find pages accessible only through a direct URL or the XML sitemap
- For each orphan page, decide whether to add it to the HTML sitemap, link to it from existing content, or remove it if it no longer serves a purpose
- Make sure the sitemap itself is accessible through a permanent link, typically in the footer
This inventory is the foundation of a useful sitemap. Without it, you’ll publish a list of links that repeats the same gaps as your main navigation.
Test a sitemap with real visitors
A sitemap may seem logical to the team that built it yet remain incomprehensible to an outside visitor. The problem often comes down to wording: labels use the company’s internal jargon instead of the terms users actually use.
The “find the page” test
Choose an important page on your site, such as a pricing page or contact form. Ask someone unfamiliar with your site to find it using only the sitemap. If they hesitate over which label to click, your wording is the problem.
This test requires neither software nor a budget. Three to five people are enough to identify ambiguous labels. The W3C also recommends offering multiple ways to find a page, including internal search or a sitemap, precisely because a single navigation path doesn’t work for everyone.
Keyboard and assistive technology checks
Keyboard navigation reveals obstacles that a visual check won’t catch. The W3C recommends making links clearly identifiable when they receive keyboard focus and using structural headings. A sitemap that can’t be navigated by keyboard excludes some visitors.
Browse your sitemap using only the Tab key. Each link should have a visible focus indicator, and the tab order should follow the visual logic of the page. If focus jumps between sections without a clear pattern, the sitemap’s HTML structure needs revisiting.

Navigation structure and sitemap: how they work together
A sitemap doesn’t replace consistent navigation across your pages. It complements it. Recurring navigation elements (the main menu, breadcrumbs, and footer links) should stay in the same place and in the same order on every page.
The sitemap acts as a safety net when these familiar cues aren’t enough. A visitor who lands on a deep page through a search engine may not immediately understand how the site is organized. Breadcrumbs show where they are; the sitemap shows them the whole picture.
- Use the same labels in the main menu and sitemap to avoid confusion
- Add breadcrumbs to every page to show its position in the site structure
- Link to the sitemap from the footer, which is accessible on every page
A useful sitemap reflects the actual navigation structure, not an alphabetical list of every published URL. Group pages by topic or user journey rather than by technical content type.
An HTML sitemap remains a fallback tool. If visitors have to rely on it regularly to find what they’re looking for, the problem lies with your main navigation, not the sitemap itself.



