You’re looking for a specific page on a website. You click through three menus, land on an empty section, then go back. This happens as soon as a site has more than a dozen pages and its structure lacks clear signposts. A website map, also called a sitemap, is designed to prevent this kind of aimless browsing: it lists the available pages and how they’re organized, for both visitors and search engines.
Breadcrumbs, menus and search: three signposts that make navigation easier
Even before consulting a sitemap, we use navigation cues without thinking about it. The W3C also recommends providing at least two ways to find a page, such as a menu and a search box, or a menu and a sitemap.
Breadcrumbs (the small links at the top of a page, such as Home > Category > Subcategory) show where you are in the site hierarchy. On a site with dozens of pages, they’re the quickest way to go back up one level without returning to the main menu.
The menu, meanwhile, gives you the big picture. A horizontal menu works well for a small site with five or six sections. As the number of pages grows, a sidebar menu or mega menu becomes easier to navigate. The right choice depends on the complexity of the site, not on a universal rule.
The search box is still the most direct shortcut when you know what you’re looking for. Combined with a sitemap, it covers both scenarios: targeted searches and free browsing. To see what a sitemap looks like in practice, take a look at the Nos libertés sitemap, which lists its pages hierarchically.
HTML sitemap or XML sitemap: two files with different purposes
It’s easy to confuse the two. The term “sitemap” refers to two very different things, and mixing them up can make the concept harder to understand.
The HTML sitemap, for visitors
This is a page on the site, written in HTML, that displays an organized list of all accessible pages. It contains clickable links grouped by section or topic. Its purpose is straightforward: when the menu isn’t enough or you’re not sure what to search for, this page gives you an overview.
You’ll often find it in the footer under the heading “Sitemap.” On larger sites, such as product catalogs and institutional websites, it may be divided into sections to keep it easy to read.
The XML sitemap, for search engines
The sitemap.xml file isn’t displayed to visitors. It’s a technical XML file that gives Google or Bing bots a list of URLs to crawl, along with metadata such as the date each page was last modified and how often it’s updated. A valid XML sitemap doesn’t guarantee that every listed page will be indexed, but it does help search engines discover them faster.
You can access it by adding /sitemap.xml to the website address. The file is rarely useful to human visitors as is, but it’s a good way to quickly check how many pages a site lists.
How to check a website’s structure without technical tools
You don’t always need a crawler or SEO software to understand how a site is organized. In most cases, a few simple checks are all it takes.
- Check the footer: most sites place links there to their HTML sitemap, legal notices and contact page. It’s the first place to look.
- Try the /sitemap.xml URL: add this path to the website address to find either the XML file or a sitemap index if the site uses multiple sitemaps (for example, one per language or content type).
- Follow the breadcrumbs back up: on any page deeper in the site, click each breadcrumb level to trace the site hierarchy and understand how the content is organized.
- Run a “site:” search on Google: the query site:mysite.com displays indexed pages. It’s not a sitemap in the strict sense, but it gives you an idea of the site’s size and the structure visible to the search engine.
When a sitemap isn’t enough: testing how pages are actually organized
A sitemap can exist without making navigation easy. It lists the pages, but says nothing about the logic behind how they’re grouped. If categories have ambiguous names or the same content appears in two different sections, visitors will still be unsure where to look.
Methods such as card sorting can help determine whether visitors group content in the same way as the team that designed the site. A group of participants is asked to sort page titles by topic, and the results are compared with the existing site hierarchy. Any differences reveal poorly named sections or misplaced pages.
Tree testing goes a step further: participants are shown the site hierarchy on its own, without any design or menu, and asked to find specific information. If most of them fail, the problem lies in the structure, not the page layout.
Both techniques work just as well for a brochure website as for a catalog with hundreds of pages. The volume of content affects the complexity, but the principle remains the same: a page should be where visitors expect to find it.
Accessibility and keyboard navigation: an often-overlooked aspect
Finding your way around a site doesn’t rely solely on sight and a mouse. The W3C recommends making links and buttons visually identifiable, ensuring that the keyboard tab order follows the logical reading order, and keeping navigation consistent from page to page.
Visitors who navigate by keyboard move through interactive elements using the Tab key. If the HTML sitemap is well structured, with links grouped by section, it remains easy to navigate. By contrast, a disorganized sitemap is just as cumbersome to navigate with a keyboard as with a mouse.
Section headings also play a role: screen readers let users jump from heading to heading to scan a page quickly. A sitemap without hierarchical headings loses this benefit.
A sitemap’s readability depends as much on its content as on its technical structure. A complete but poorly organized file can be just as frustrating as having no sitemap at all.
