A sitemap is not just an XML file placed at the root of a server. It is a structural document that exposes the complete hierarchy of pages, their relationships, and their relative weight in the architecture. When well-designed, it speeds up crawling by indexing bots and reduces the number of clicks needed for a visitor to reach any page.
XML Sitemap and HTML Sitemap: Two Distinct Navigation Logics
The XML sitemap is aimed at crawlers. It lists URLs, optionally associates a last modified date, and indicates the existence of pages that internal linking alone does not reveal. Google ignores the priority and changefreq values: only the lastmod tag retains interest, provided it reflects a real change in content.
The HTML sitemap, on the other hand, is aimed at visitors. It takes the form of a page accessible from the footer, organized by sections. Its role is to compensate for the limitations of the main menu, which cannot display all the URLs of a large site. On the doubleportion.fr sitemap, each section groups pages by theme, allowing users to locate specific content without going through the search bar.
A common mistake is to produce only an XML sitemap and consider navigation covered. An XML file does not replace a human-readable structure. Both formats coexist and serve complementary functions.
Information Architecture: Structuring Pages Before Listing Them
Listing URLs is not enough. A readable sitemap relies on prior work of semantic grouping of content. Each page must belong to an identifiable category, and each category must have an explicit label, formulated in the vocabulary that users actually use.
We recommend limiting the depth to a maximum of three levels. Beyond that, navigation becomes opaque for both visitors and bots. Content buried at the fourth level receives less internal link juice and will be crawled less frequently.
Criteria for Classifying Pages in the Sitemap
- Thematic proximity: pages that deal with the same topic or service are grouped under the same parent node, even if they belong to different content types (article, product sheet, category page).
- Consultation frequency: the most visited pages rise to the top of their section. The sitemap is not an alphabetical inventory; it is a navigation interface driven by usage.
- Functional dependency: a terms and conditions page depends on an order page, not on an editorial section. The sitemap reflects the actual user journey, not the internal organization chart.
This architectural work precedes the publication of the sitemap. Changing the order of sections afterward generates inconsistencies in internal linking and disrupts the signals sent to search engines.
Accessibility and Keyboard Navigation on the Sitemap
Each link in the sitemap must be reachable via keyboard, in a tab order consistent with the visual hierarchy. The WCAG 2.2, published on October 5, 2023, reminds us that navigation commands should not rely solely on the mouse or visual cues.
In practical terms, this means that link labels must be explicit out of context. A link labeled “Learn more” does not inform a screen reader about the destination. The anchor text must describe the target page.
Checklist for an Accessible Sitemap
- Sections and subsections use hierarchical heading tags (h2, h3) so that assistive technologies can navigate by sections.
- The contrast between link text and background meets a minimum ratio allowing reading by visually impaired individuals.
- The order of the source code corresponds to the visual order: a discrepancy between the two creates incoherent navigation for keyboard users.
Since June 28, 2025, the European Accessibility Act requires websites offering digital services to comply with enhanced accessibility requirements. A poorly structured sitemap can constitute a point of non-compliance.
Internal Linking and Sitemap: The Often Overlooked Technical Link
The HTML sitemap serves as a hub for internal links. Each URL listed receives at least one link from an indexable page of the domain. For sites with orphaned pages (no other page links to them), the sitemap becomes the only means of discovery by crawlers.
This mechanism has a limit: if the sitemap contains several hundred links on a single page, the weight passed to each URL decreases. On sites exceeding a few hundred pages, it is preferable to segment the sitemap into thematic sub-sitemaps, each linked from an index page.
The XML sitemap complements this setup by signaling to search engines the recently modified URLs. The combination of both formats covers both automated crawling and human navigation. Neglecting either one means leaving part of the site in the dark, either for bots or for visitors.
A well-organized sitemap is not a footer accessory. It is a structural component that determines the quality of internal linking, compliance with accessibility standards, and the ability of search engines to explore all published content.
