A website sitemap is not just an XML file submitted to Google Search Console. It is an architectural document that determines crawl depth, the distribution of internal PageRank, and users’ ability to reach any page within a maximum of three clicks. We regularly observe sites where the HTML sitemap and the XML sitemap diverge, creating indexing inconsistencies and degrading actual navigation.
WCAG 2.2 Criteria That Change Sitemap Design
The WCAG 2.2 version, published on October 5, 2023, introduces requirements directly related to navigation structure. Mainstream articles rarely address these criteria, even though they condition the legal compliance of many sites in Europe.
Criterion 2.4.11 (Focus Not Obscured, level AA) requires that the keyboard-targeted element is never completely hidden by a sticky header, a cookie banner, or a chat widget. In practice, this necessitates rethinking the height of fixed menus and the stacking of overlays in the page layout.
Criterion 3.2.6 (Consistent Help, level A) mandates that any help mechanism (contact link, FAQ, chat) appears in the same relative position on every page of the site. A sitemap that does not account for this placement from the tree structure phase generates costly corrections in production.
Criterion 2.5.8 (Target Size Minimum, level AA) sets a minimum target area of 24 x 24 pixels for interactive elements. Dense navigation menus, with tightly packed links on mobile, often fail this test. We recommend validating target sizes as early as the wireframe stage of the visual sitemap.
XML Sitemap and HTML Sitemap: Two Distinct Functions in Web Architecture
Confusing XML sitemaps with HTML sitemaps remains the most common mistake. The XML file is intended for indexing bots from Google and other search engines. The HTML sitemap is a page accessible to visitors, listing the site’s categories and pages in a readable hierarchy.
To illustrate this complementarity, the sitemap of www Site de Bankai functions as a table of contents for users, while the corresponding XML file targets only crawlers.
A well-designed HTML sitemap reduces navigation depth. Each important page becomes accessible within two clicks from the root, improving both crawl budget and user experience simultaneously. The XML sitemap, on the other hand, must accurately reflect canonical URLs, without including noindex pages or 301 redirects.
Signals of Divergence to Watch For
- URLs present in the XML sitemap but absent from the HTML sitemap indicate orphan pages that Google indexes without visitors being able to reach them through navigation.
- URLs listed in the HTML sitemap but excluded from the XML create an inconsistency: the site displays links to pages that it implicitly requests Google not to crawl.
- An XML sitemap containing URLs with 404 errors or redirects undermines the indexing bot’s trust and slows down the crawl of actually active pages.
Internal Linking Driven by the Sitemap
The sitemap determines the distribution of internal PageRank. Without prior mapping, internal links accumulate randomly, concentrating authority on the homepage and main category pages at the expense of deeper content.
We structure the linking starting from the hierarchy of the HTML sitemap. Each hierarchical level (home, categories, subcategories, final pages) receives a number of incoming links proportional to its SEO priority. This principle avoids diluting link juice to low-value pages.
Click Depth and Impact on Indexing
A page located more than three clicks from the root statistically has a lower chance of being crawled regularly. The sitemap serves as a safety net: even if the main navigation does not lead directly to a deep page, the HTML sitemap ensures access within a maximum of two clicks.
Contextual links within the content reinforce this linking structure. A link placed in a relevant paragraph conveys more semantic value than a generic link in the footer. The sitemap identifies thematic connections between pages to guide this internal linking strategy.
Tree Structure Errors That Sabotage Navigation and SEO
An overloaded navigation menu does not compensate for a poorly thought-out structure. Beyond seven items in the main menu, the click-through rate per item drops significantly. We recommend limiting the first level to five or six entries, then using targeted submenus.
Too flat structures pose a symmetrical problem. A site that places all its pages at the same hierarchical level prevents Google from understanding the semantic relationships between contents. The search engine struggles to identify pillar pages and satellite pages.
Keyword Cannibalization and Duplicate URLs
A blurry structure encourages SEO cannibalization: two pages target the same keyword without the sitemap defining which one is prioritized. The solution involves an audit of the structure, page by page, cross-referencing each URL with its target keyword and its position in the hierarchy.
Duplicate URLs (with and without trailing slashes, www and non-www versions) must be addressed in the XML sitemap with consistent canonical tags. A clean sitemap eliminates these duplicates before they fragment domain authority.
Effective navigation on a website relies on an architectural decision made upstream, not on fixes applied after launch. The sitemap, whether HTML or XML, remains the only document that forces consideration of all navigation paths before writing the first line of code.