A visitor arrives on a site, searches for specific information, clicks two or three times without finding it, and then leaves the page. This scenario repeats every day on thousands of sites whose architecture lacks clarity. The sitemap, often relegated to the footer, remains one of the most underutilized navigation tools, even though it precisely addresses this problem.
XML Sitemap and HTML Sitemap: Two Tools Often Confused
People often confuse the sitemap.xml file, intended for crawlers, with the HTML page listing the structure for human visitors. Both share the same name, but their functions diverge.
The XML sitemap helps search engines discover URLs. It does not guarantee their crawling or indexing. Therefore, strategic pages must also be linked by descriptive and crawlable internal links within the site body.
The HTML page, on the other hand, provides an overview of the structure: sections, subsections, and orphan pages made visible. This is the version users consult when the main menu is insufficient. One can observe how a Soupir sitemap organizes its content to give a quick overview of all available sections.
Treating these two formats as interchangeable creates a blind spot: a complete XML sitemap does not compensate for poor HTML navigation, and vice versa.
Accessible Navigation Architecture: What the European Accessibility Act Changes Practically
Since June 28, 2025, the European Accessibility Act applies to several digital services intended for consumers: online shopping, banking services, passenger transport, electronic communications, and e-books. Accessibility obligations now extend beyond the public sector.
For a sitemap, this involves specific constraints:
- Each link must be reachable and activatable via keyboard, without relying solely on the mouse or a touch gesture.
- Dropdown menus and modal windows integrated into navigation must remain usable with assistive technologies (screen readers, voice navigation).
- The link text must be descriptive: a label like “click here” is not enough; the destination must be named (“product catalog,” “delivery terms”).
A well-constructed HTML sitemap simplifies this compliance. It provides a flat list of explicit links, without complex interactions, making it naturally compatible with keyboard navigation.
Sitemap and Internal Linking: Identifying Orphan Pages
An orphan page is not linked by any internal link. Search engines find it difficult to discover, and visitors even more so. On a site with several hundred pages, feedback varies on the actual number of orphan pages, but the phenomenon affects the majority of sites that do not regularly audit their linking.
The HTML sitemap makes orphan pages immediately visible. If a URL does not appear in any section of the sitemap page, it is a clear signal: either it deserves to be integrated into the structure, or it should be removed or redirected.
Concrete Method for Auditing Linking via the Sitemap
We compare the list of URLs from the XML sitemap (extracted from the Search Console or a crawler) with the links present on the HTML sitemap page. The discrepancies between the two lists reveal isolated content.
Then, we classify each orphan page into three categories: to be linked to an existing section, to be merged with similar content, or to be deindexed. This sorting takes less than an hour on a medium-sized site and eliminates the main barrier to search engine crawling.
Structuring a User-Friendly Sitemap for Both Users and Engines
An effective sitemap is not just a raw list of links. Visual hierarchy matters as much as completeness.
- Group pages by theme or by section of the main menu, replicating the logic of the site’s actual structure.
- Limit depth to two or three levels: beyond that, the sitemap loses its quick-reference function.
- Use link titles identical to those in the navigation menu to avoid confusion between the sitemap and the usual sections.
- Update the page with each addition or removal of content, as an outdated sitemap generates broken links and undermines user trust.
An up-to-date sitemap reduces the bounce rate on navigation queries, where the user is looking for a specific page rather than general information. It acts as a safety net when internal search or the menu does not yield satisfactory results.
Update Frequency and Automation
On a site where content evolves weekly (blog, product catalog, news), manually generating the HTML sitemap quickly becomes unmanageable. Most CMS offer extensions that automatically sync the sitemap page with the actual structure. However, it is still advisable to check once a month that the page reflects the actual structure, as some extensions ignore pages excluded from the main menu.
The sitemap remains a seemingly simple tool, but its impact is measured on two simultaneous fronts: the ability of engines to crawl the entire site, and the ability of visitors to find what they are looking for without going through an external search engine. Neglecting either one means only exploiting half of its potential.
