An HTML sitemap does not serve the same function as a navigation menu. The menu selects a few priority paths (rarely more than seven entries) to guide a visitor exploring. The sitemap, on the other hand, is a comprehensive map of the architecture: it is aimed at those who already know what they are looking for and want to access it directly. Confusing the two means ignoring a lever of findability directly correlated to conversion.
Architecture of an HTML sitemap and its role in indexing
The HTML sitemap is a human-readable document, distinct from the XML sitemap intended for crawlers. The XML declares URLs with metadata (priority, update frequency). The HTML, on the other hand, organizes these URLs as clickable links grouped by category, theme, or type of content.
This distinction has a direct technical consequence: a well-structured HTML sitemap creates internal links to every important page, which reduces crawl depth. Pages buried more than three clicks from the homepage are often under-indexed. The sitemap brings these pages back to one click from the root.
We observe that a site whose HTML sitemap covers all service or editorial content pages significantly improves internal linking without resorting to complex navigation widgets. This is precisely the logic behind the Raconte-moi sitemap, which references all episodes and categories of the catalog in a single hierarchical view.
Raconte-moi sitemap: structure and navigation paths
Raconte-moi is an editorial platform organized by major historical themes (Antiquity, Middle Ages, explorations, sciences). Each theme gathers audio and textual episodes. The sitemap exposes this complete structure, where the main menu only presents first-level categories.
Findability of buried episodes
A catalog that exceeds several dozen episodes poses a classic findability problem. A visitor looking for a specific episode on Archimedes or Hokusai will not browse through the pagination of each category. The sitemap offers them direct access, like an alphabetical or thematic index in a printed work.
This mechanism is particularly useful for older content. Episodes published several months ago gradually disappear from homepages and recent feeds. The sitemap ensures that they remain accessible in one click, maintaining their potential for organic discovery.
Thematic navigation versus chronological navigation
Two classification logics coexist on most editorial sites:
- Chronological navigation (from most recent to oldest), suited for regular visitors who follow publications.
- Thematic navigation (by subject, era, or format), suited for occasional visitors arriving via a search engine with a specific intent.
- The hybrid sitemap, which combines both by displaying thematic categories with, under each, episodes listed in a readable order.
Raconte-moi exploits this third option. The sitemap groups episodes by collection (travels and explorations, sciences, etc.) while maintaining a clear visual hierarchy between categories and individual contents.
Using an HTML sitemap to improve user journey
A sitemap is only useful if it is accessible. We recommend linking it from the footer of all pages, which is the most common convention. Placing it only in a submenu or an “about” page drastically reduces its usage.
Automatic updating is another often-overlooked technical point. A static sitemap, hand-coded, becomes obsolete as soon as a new page is published. CMSs like WordPress allow for dynamic generation of the HTML sitemap, in sync with the XML sitemap.
Criteria for an effective HTML sitemap
Not all sitemaps are created equal. Here are the elements that distinguish a functional sitemap from a simple list of URLs:
- A grouping by category or theme, with explicit titles (no technical slugs or numerical identifiers).
- Complete page titles, not raw URLs: the visitor should understand the content of the page before clicking.
- An absence of orphan pages or broken redirects, verifiable via a sitemap validation tool.
- A controlled loading time: on a catalog of several hundred pages, pagination or grouping by section avoids an overly heavy document.
The Raconte-moi sitemap meets these criteria by displaying the full title of each episode under its associated collection, allowing for quick reading without ambiguity about the destination content.
Difference between menu, sitemap, and semantic cocoon
The semantic cocoon, popularized in French SEO, organizes pages into thematic silos connected by contextual internal linking. The HTML sitemap, however, does not create a semantic hierarchy: it lists and connects, without weighing the thematic proximity between two pages.
Both approaches are complementary. The cocoon structures deep linking (parent page to child pages of the same subject). The sitemap offers a cross-sectional shortcut that bypasses the cocoon hierarchy to reach any page directly.
The navigation menu, the third piece of the puzzle, is limited to the most frequent paths. On Raconte-moi, the menu provides access to major categories and the homepage. The sitemap takes over for the rest of the catalog.
An editorial site that only has a menu and an XML sitemap, without an HTML sitemap, leaves part of its content in a gray area: visible to bots but difficult to find for readers. Adding an HTML sitemap corrects this imbalance without altering the existing architecture, in a single page that serves both impatient users and search engines.
