A sitemap is not just an XML file submitted to search engines. It is a full-fledged navigation document, intended for visitors as much as for indexing bots. When poorly designed, it becomes a flat list of links without logic, useless for the user and little utilized by crawlers. Here we discuss the technical points that separate a functional sitemap from a simple dump of URLs.
WCAG 2.2 Criteria Applied to the Sitemap
An accessible sitemap does not consist of just adding an alt attribute to an image. The WCAG 2.2 criteria require that recurring navigation mechanisms appear in a consistent order and position from one page to another. Specifically, if the link to the sitemap is located in the footer, it must occupy the same relative position on each template.
Keyboard navigation poses a common problem on large sitemaps. The focus should never be obscured by a fixed header or a consent banner. Each interactive element must provide a sufficient targeting area, and any drag-and-drop function (such as reorganizing categories in a back office) must offer an alternative without dragging.
These requirements are not theoretical. Since June 28, 2025, the European Accessibility Act applies to e-commerce, banking services, telecommunications, and transport. An e-commerce site whose sitemap is not keyboard navigable is exposed to penalties. Very small businesses benefit from exemptions, but the scope remains broad.
We recommend a combined audit: automated tools to detect markup errors, followed by a manual check of keyboard navigation. An accessibility audit cannot be fully automated, as tools do not detect the contextual consistency of labels or the logic of link grouping.
Sitemap Structure: Hierarchy, Grouping, and Depth
We regularly observe sitemaps that list several hundred pages without any grouping. The L’Actu Dissidente sitemap illustrates a thematic category approach, where each section groups related content under an explicit title. This type of structure facilitates visual scanning and reduces the number of clicks needed to reach a deep page.
Grouping should reflect the actual hierarchy of the site, not an abstract taxonomy. Three levels of depth are sufficient in most cases: category, subcategory, page. Beyond that, the sitemap becomes a mirror of the main menu and loses its own utility.
What the HTML Sitemap Provides Compared to the XML Sitemap
The XML sitemap serves exclusively indexing bots. It contains neither visual hierarchy nor contextual labels. The HTML sitemap, on the other hand, is aimed at visitors looking for a page without going through the menu or internal search. The two are complementary, not interchangeable.
A well-structured HTML sitemap reduces reliance on internal search, especially on sites where the search engine is underperforming. This is often the case on institutional or media sites.
- The XML sitemap contains URLs with metadata (last modified date, update frequency, priority) intended for crawlers.
- The HTML sitemap offers clickable links organized by theme, with human-readable titles.
- The breadcrumb trail complements both by displaying the user’s position in the hierarchy, page by page.
Common Technical Errors on Sitemaps
The first error is the lack of updates. A sitemap that references 404 URLs degrades the user experience and sends a negative signal to search engines. Each listed URL must return an HTTP 200 code. A weekly verification script is sufficient to maintain this consistency.
The second error concerns link anchors. A sitemap where each link displays “Click here” or “Learn more” is unusable for a screen reader and useless for SEO. Each anchor must describe the destination page in a few words.
Orphan Links and Excluded Pages
A page absent from the sitemap and not linked from any other page becomes orphaned. Crawlers find it difficult to discover, and users never find it through navigation. We recommend cross-referencing the HTML sitemap with the XML sitemap and server logs to identify these ghost pages.
Conversely, some pages are not meant to be included in the sitemap: login pages, thank-you pages after forms, internal search result pages. Including them clutters the document and dilutes the relevance of useful links.
Sitemap and Internal Linking: Two Distinct Logics
The sitemap is not a substitute for internal linking. Internal linking distributes SEO weight among pages via contextual links in the written content. The sitemap provides an overview, a global entry point. The two address different needs and complement each other.
An effective internal linking strategy makes the sitemap less sought after by visitors, as contextual navigation is sufficient in most journeys. The sitemap acts as a safety net: when the visitor cannot find what they are looking for through the usual paths, they should be able to access a complete mapping of the content.
- Internal linking connects thematically related pages within the body of text, with descriptive anchors.
- The sitemap groups all accessible pages, organized by section, regardless of the written context.
- The main navigation menu exposes first-level categories, while the sitemap goes down to individual pages.
A site with an up-to-date sitemap, keyboard navigable and structured by logical levels meets both accessibility requirements and search engine expectations. Regular maintenance of this document, often neglected after the initial launch, remains the factor that separates a useful sitemap from a page forgotten in the footer.
