A sitemap is a file or page that lists the URLs of a website according to a hierarchical structure. There are two main variants: the XML sitemap, intended for search engine indexing bots, and the HTML sitemap, designed for human visitors. Understanding the difference between these two formats allows you to leverage each according to the intended goal.
HTML Sitemap and Accessibility: A Regulatory Criterion Often Ignored
Most articles discussing sitemaps focus on natural SEO. The accessibility aspect remains largely absent from published content, even though it represents a concrete issue for many sites.
The WCAG 2.2 level AA recommendations require offering multiple ways to locate a page within a site. Criterion 2.4.5 (“Multiple Ways”) explicitly cites the HTML sitemap as one of the accepted mechanisms, alongside the navigation menu and search bar.
For administrations, digital public services, and large commercial sites subject to these standards, maintaining an up-to-date HTML sitemap page is not optional. In the UK, the update to WCAG 2.2 AA is now integrated as a legal requirement for public sector sites. In practice, this obliges the concerned organizations to document at least one sitemap or equivalent as an additional navigation path.
Screen reader users often navigate from link to link without going through the intermediate content. A well-structured HTML sitemap page, with clear headings and a logical hierarchy, provides them with direct access to any section of the site, without relying on a sometimes poorly coded dropdown menu. A concrete example of this approach can be found on the sitemap page of Info Simple, which organizes all content by category in a readable tree structure.
XML Sitemap: What Search Engines Really Read
The XML sitemap is not aimed at visitors. It is a technical file, hosted at the root of the site (often accessible via /sitemap.xml), which provides Google or Bing bots with the list of URLs to explore.
Each entry in the file can contain metadata: the last modified date, the estimated update frequency, and a relative priority indicator. This information helps engines allocate their crawl budget more effectively, visiting first the recently modified or prioritized pages.
When the XML Sitemap Really Changes Indexing
On a small site with a few dozen pages and a coherent internal linking structure, Google usually discovers all URLs without a sitemap. The contribution becomes tangible in specific cases:
- Large sites (product catalogs, news portals) where some deep pages do not receive any direct internal links and may never be explored.
- Recently launched sites, whose domain does not yet have sufficient external links to trigger a complete crawl by the bots.
- Multimedia content (images, videos) that require specific tags in the sitemap to be properly indexed in rich results.
Submitting an XML sitemap via Google Search Console does not guarantee the indexing of every URL. The file is a suggestion, not a directive. Google remains free to ignore pages it deems of low value or duplicates.
HTML Sitemap Page for Visitors: Navigation and Visible Architecture
The HTML sitemap is a page of the site, visible and clickable, that presents the complete structure in the form of a hierarchical list. Its usefulness goes beyond accessibility.
When a visitor arrives at an unfamiliar site and cannot find what they are looking for via the main menu, the sitemap page offers an immediate overview. This is particularly useful on sites with complex structures or where the menu only presents a fraction of the available sections.
Impact on Internal Linking and SEO
Each link present in the HTML sitemap page constitutes an additional internal link to the target page. On sites where certain sections are poorly linked to the rest of the architecture, the HTML sitemap acts as a safety net: it ensures that at least one navigation path leads to each piece of content.
This complementary linking can help search engines discover orphan pages, that is, URLs that do not appear in any menu or article. The HTML sitemap page thus serves a dual function: a navigation tool for the visitor and a structural signal for the bot.
Common Errors in Managing the XML Sitemap
A poorly maintained sitemap sends contradictory signals to search engines. Two errors frequently occur.
The first involves including URLs with a “noindex” tag. The file asks the bot to explore the page, while the tag instructs it not to index it. This type of conflict can degrade the trust that the engine places in the sitemap as a whole.
The second error concerns URLs that are redirected (301 or 302 codes) or returning a 404 error. A sitemap containing broken links signals a poorly maintained site. Google treats these inconsistencies as indicators of low technical quality.
- Check that each URL in the sitemap returns an HTTP 200 code (page accessible).
- Exclude pages marked “noindex” or protected by the robots.txt file.
- Update the sitemap after each deletion or content migration.
A clean XML sitemap, synchronized with the actual state of the site, remains the best way to facilitate the work of crawling bots without creating unnecessary noise. The HTML sitemap page also deserves the same rigor: broken links on a page intended to map the entire site harm both user experience and the technical credibility perceived by engines.
