Skip to content

Flotsam & Catsam

Our opinion and nothing more

How to Easily Navigate a Website’s Sections Using Its Sitemap

An HTML sitemap serves as a supplementary navigation index alongside menus and internal search. The W3C recommends providing…

Femme consultant un plan de site imprimé pour naviguer facilement entre les rubriques d'un site web
5 min read

An HTML sitemap works as a supplementary navigation index alongside menus and internal search. The W3C recommends offering multiple ways to find information on a website, and a sitemap is one of them, along with breadcrumbs and a search bar. Its value lies in its ability to display the complete site hierarchy on a single screen—something neither the main menu nor the footer can really do.

HTML sitemap accessibility: keyboard navigation and assistive technologies

A poorly designed HTML sitemap becomes an obstacle rather than a shortcut. When the page is just a raw list of several hundred links with no logical grouping, screen reader users have to navigate through every item sequentially. This is worse than conventional menu navigation.

For a sitemap to genuinely help people who navigate by keyboard or use assistive technology, each group of links must be introduced by a section heading (h2 or h3 tags). Screen readers use these headings to provide a page outline. JAWS or NVDA users can then jump straight to the “Blog,” “Catalog,” or “Contact” section without having to go through all the preceding links.

Three technical principles make an HTML sitemap usable by everyone:

  • Group links by section under descriptive headings, and limit each group to around twenty entries to keep the page readable without excessive scrolling.
  • Use nested HTML lists (ul > li > ul) rather than tables or generic blocks, since user agents automatically announce the nesting level and number of items.
  • Assign an aria-label attribute or a navigation role to the sitemap area so assistive technologies identify the page as a global navigation point, in line with WCAG 2.4.5 criteria on multiple ways to locate content.

A sitemap that follows these rules does not need to be exhaustive. It is better to show the main sections and their first-level subcategories than to list every article or product page.

Man analyzing the hierarchical structure of a sitemap on a large desktop screen

HTML sitemap and XML sitemap: two different formats for two different purposes

An HTML sitemap is for visitors; an XML file is for crawlers. This distinction may seem well established, but confusion persists on many websites where the “sitemap” page actually links to a raw XML file that is unreadable to humans.

We often see websites remove their HTML sitemap in favor of an XML sitemap alone, on the assumption that Google will index every page. Yet Google describes an XML sitemap as an additional way to discover URLs, not as a guarantee of crawling or indexing.

A post published on the Google Help forum in October 2026 describes an XML sitemap that was successfully processed and URLs that were discovered but not indexed. Discovering a URL and indexing it are two separate steps.

On the Ludivine Passion sitemap, sections are presented as clickable links organized by category, allowing visitors to find the section they are looking for in seconds without relying on the main menu.

For XML sitemaps, Google recommends listing only canonical URLs that you want to appear in search results. The lastmod tag is useful only if it reflects an actual content change. Google ignores the priority and changefreq fields. A well-maintained XML sitemap does not replace a well-structured HTML sitemap: each serves a different purpose.

Section structure in a sitemap: hierarchy and useful depth

The temptation to show everything in a sitemap results in endless pages where no one can find anything. The most practical rule for depth is to limit the display to two levels of navigation: the main sections and their direct subcategories.

An e-commerce site with thousands of product pages has no reason to list them all in its HTML sitemap. However, showing “Clothing > Dresses / Trousers / Jackets” followed by “Accessories > Bags / Jewelry / Belts” is enough to guide a visitor who has lost their way. If someone is looking for a specific product, internal search is more effective than a sitemap.

For a blog or editorial website, grouping by topic is more useful than grouping chronologically. A sitemap organized by category (“Tutorials,” “News,” “Buying Guides”) with the five to ten most recent articles in each category provides a useful starting point. A sitemap is not an exhaustive directory but an index focused on key sections.

Young person exploring a sitemap in a café with an open laptop

User journey: when and why to consult a sitemap

An HTML sitemap is not a visitor’s first port of call. It comes into play after a navigation attempt fails: the menu does not include the section they are looking for, internal search returns too many results, or the 404 error page offers no relevant redirect.

It is precisely in these situations, when the usual path breaks down, that a sitemap proves its value. A link to the sitemap in the footer and on the 404 page covers the two most common scenarios. Placing it only in the footer, as most websites do, overlooks the fact that the visitor most likely to need it is the one who has just landed on a page that does not exist.

The W3C emphasizes the importance of multiple paths to information. A sitemap serves as a navigation safety net. Visitors who arrive from a search engine on a deep page of the site can return to the main sections without going back to the homepage.

  • From the footer: always available, whatever page the visitor is viewing; useful for regular visitors who know the sitemap exists.
  • From the 404 page: helps visitors who have lost their way, with a clear link to the sitemap so they can find the section they want.
  • From the breadcrumbs: on some websites, a “All sections” link at the start of the breadcrumb trail leads directly to the sitemap, providing a discreet but effective shortcut.

An HTML sitemap that is well placed within the site architecture and structured with headings that assistive technologies can use remains one of the simplest navigation tools to implement. It requires little maintenance if limited to the main sections, and its usefulness is most apparent when all other navigation options have failed.

How to Easily Navigate a Website’s Sections Using Its Sitemap