A sitemap gathers all the pages of a web domain in a hierarchical list format. On an online magazine that publishes varied content (news, thematic files, practical sheets), this page becomes a direct navigation tool, much faster than a search bar when the exact term to type is not known.
Accessibility of the sitemap: what WCAG 2.2 changes concretely
Competitors approach web navigation in general terms, but none link the sitemap to the recent criteria of WCAG 2.2. These updates impose specific constraints that transform the sitemap page from a simple index into a regulatory accessibility mechanism.
Three points deserve particular attention. First, the size of clickable targets: each link in the sitemap must be large enough and spaced adequately to remain usable on mobile and by people with motor difficulties. Next, keyboard-only navigation: the focus (the active element) must remain visible at all times, even when a fixed header or sticky menu covers part of the page.
The third criterion concerns semantic structure. The headings, lists, and navigation areas of the sitemap must be properly marked up so that screen readers can create a logical map of the domain. A sitemap that uses simple paragraphs instead of ordered lists loses all utility for an assistive technology user.
By exploring the sitemap of L’Annonceur, one observes an organization by sections that facilitates this type of assisted reading, with each section identifiable without having to scroll through the entire page.
Structure of an editorial sitemap: comparative table of formats
Not all sitemaps are created equal. An e-commerce site, a personal blog, and an online magazine have different classification needs. The table below compares three common formats.
| Format | Organization | Main Use | Limit |
|---|---|---|---|
| Alphabetical list | Pages listed from A to Z | Showcase sites with few pages | Unusable beyond a few dozen entries |
| Category tree | Sections then subsections | Magazines, editorial sites | Requires a coherent nomenclature |
| XML Sitemap (technical) | File intended for indexing bots | SEO, crawling by Google | Not readable by a human visitor |
For a media outlet like L’Annonceur, the category tree remains the most effective format because it reproduces the editorial logic of the site. Visitors find the same sections as in the main menu, but with all pages visible at once.
Saving time on a sitemap: navigation shortcuts in the browser
Faced with a page that lists hundreds of links, the most useful reflex is the integrated search in the browser. On most desktop browsers, the shortcut Ctrl+F (or Cmd+F on Mac) opens a search field in the page. By typing a keyword related to the sought topic, the browser highlights each occurrence and allows jumping from one to another.
This method works better than an internal search bar in a specific case: when the visitor does not know the exact title of the article but remembers a term related to the topic. The in-page search scans all visible titles, including those buried in subcategories.
On mobile, the operation differs
Most mobile browsers offer a “Search in page” function accessible via the context menu (three dots or share icon). The display remains less comfortable than on a wide screen, but the time saved compared to manual scrolling is significant on a large sitemap.
- On Chrome Android: three dots menu, then “Search in page”
- On Safari iOS: address bar, then “Search in this page” at the bottom of the suggestions
- On Firefox mobile: three dots menu, then “Search in page”
HTML sitemap and SEO: two readings of the same page
A common confusion mixes the HTML sitemap (the page visible to visitors) and the XML sitemap (the technical file read by Google bots). Both coexist on most sites, but they do not serve the same purpose.
The XML sitemap sends search engines the list of URLs to explore, with metadata such as the last modified date or update frequency. The HTML sitemap, on the other hand, is aimed at humans. It presents the pages with their editorial titles, grouped by theme.
Complementarity for internal linking
The HTML sitemap generates an internal link to each page of the domain. For an editorial site that publishes regularly, this means that even older articles retain at least one active internal link, that of the sitemap. This minimal linking helps indexing bots rediscover content that may have disappeared from the main navigation menus.
However, an HTML sitemap does not replace contextual linking between articles. Links placed in the body of a text, within a thematically relevant paragraph, convey a stronger relevance signal than a generic link in a list.
When to use the sitemap instead of the menu or search
The sitemap is not a permanent substitute for the navigation menu. It addresses specific situations where other tools show their limits.
- The user is looking for content whose exact section is unknown: the sitemap allows for visually scanning all categories in a few seconds
- The main menu only shows the latest publications or top-level sections, hiding subcategories
- The internal search bar returns too many results or none, because the entered term does not match the exact title of the article
- The user wants to get a general idea of the site’s editorial coverage before subscribing or returning regularly
The sitemap functions like a table of contents in a book. It is not consulted at every reading, but it becomes valuable as soon as linear navigation is no longer sufficient. On an online magazine that covers multiple sectors, this overview remains the most reliable way to check that a topic has been addressed, without relying on the relevance of an internal search algorithm.