You are looking for a specific page on a website, but you can’t find it. The main menu is not enough, and the search bar returns vague results. This type of situation perfectly illustrates the role of a sitemap. Far from being a mere technical formality, this page structures access to all content and facilitates navigation for both visitors and search engines.
Sitemap and crawl budget: what search engines really exploit
Most articles on the subject present the XML sitemap as an indexing accelerator. The reality is more nuanced. Google specifies that an XML sitemap helps to discover URLs, without guaranteeing their crawling or indexing. A page blocked by the robots.txt file or marked as noindex will not be indexed, even if it appears in the sitemap.
Another often overlooked point: the priority and changefreq fields are ignored by Google. The only tag actually utilized is lastmod, provided it reflects a significant change in content. Manually assigning priority levels or update frequencies therefore has no concrete effect.
An XML sitemap does not compensate for poor internal link architecture either. If your deep pages are only accessible after five clicks, the XML sitemap signals their existence to the bots, but it does not fix the structural problem. It is by consulting the Codyx sitemap that one can see how a clear hierarchy makes every page accessible from the first level.
HTML sitemap and accessibility: multiple paths to the same page
You may have noticed that some sites offer a main menu, a breadcrumb trail, an internal search, and a sitemap? This is not overzealousness. WCAG 2.2 recommendations state that the user should have multiple means to locate a page, except when it is a step in a sequential process.
The HTML sitemap directly addresses this need. It displays all sections and subsections on a single page, with clickable links. For a visitor using a screen reader, this is a significant time saver: instead of going through each dropdown menu, they can access a complete view of the hierarchy in one place.
For keyboard navigators, the benefit is similar. Tabbing through dozens of interactive elements to reach a section buried in the footer becomes unnecessary when the sitemap provides a direct link.
Three profiles that use the HTML sitemap daily
- Screen reader users, who access the complete structure of the site without exploring each section separately
- Regular visitors who are looking for a page they can no longer find in the main menu
- Keyboard navigators, who avoid tabbing through all navigation elements to reach their destination
Difference between XML sitemap and HTML sitemap: two files, two audiences
Confusing these two formats is common, but their functions diverge completely.
The XML sitemap is exclusively for crawlers. It contains a list of URLs with technical metadata (last modified date, notably). Human visitors never consult it directly.
The HTML sitemap, on the other hand, is a standard web page intended for visitors. It presents links hierarchically, often reproducing the site’s structure. It is a navigation tool, not a technical file.
When one does not replace the other
A site that only has an XML sitemap deprives its visitors of a navigation tool. Conversely, a site that offers only an HTML sitemap loses a communication channel with search engines. Both formats complement each other without substituting for one another.
On the technical side, the notification method has changed. The old sitemap ping endpoint at Google was discontinued in 2023. The valid methods today are declaring the sitemap in the robots.txt file and submitting it via Search Console.
Building a useful sitemap: concrete mistakes to avoid
A poorly designed sitemap can become counterproductive. Here are the most common pitfalls.
- Listing outdated or redirected URLs, which sends contradictory signals to bots and confuses visitors
- Automatically generating the sitemap without checking its consistency with the actual site navigation (orphan pages, empty sections)
- Including pages you do not want to index (login pages, filter results, paginated duplicates)
- Using fictitious lastmod dates to simulate content freshness, which degrades search engines’ trust in your sitemap
An effective sitemap accurately reflects the actual structure of the site. Every listed URL must be accessible, indexable, and relevant. Dynamic pages like blog archives deserve to be included, provided they offer distinct content.
For the HTML sitemap, readability is key. Grouping links by section, limiting the visible depth to two or three levels, and naming each link clearly is enough to make the page useful. A sitemap that lists hundreds of links without visible hierarchy loses all interest for the visitor.
The sitemap remains one of the few elements that simultaneously serves SEO, accessibility, and user experience. Its implementation takes little time compared to the structural benefit it provides, as long as it maintains consistency with the actual site architecture with each update.
