A sitemap serves two distinct functions depending on whether it is aimed at search engines or human visitors. This distinction, often blurred in general guides, is crucial for the entire navigation strategy of a website. Understanding what each format brings (and what it does not guarantee) helps avoid structural errors that penalize both SEO and user experience.
XML Sitemap and HTML Sitemap: two objects, two logics
The term “sitemap” encompasses two technical realities that most website owners confuse. The XML sitemap is a file intended for search engine crawlers. It lists canonical, indexable URLs that return an HTTP 200 status, with a correctly filled lastmod metadata. Its role is limited to speeding up the discovery of pages that are poorly linked by internal linking.
The HTML sitemap, on the other hand, is a page visible to visitors. It functions like a table of contents for the site, useful for accessibility and navigation, but has no direct impact on ranking in search results.
This separation has practical consequences. A poorly configured XML sitemap (URLs returning 404 errors, non-canonical pages, redirects) can slow down crawling without improving indexing. A neglected HTML sitemap deprives users of a navigation reference, especially on sites with several hundred pages. By exploring the Bankai sitemap, one can see how a clear structure organizes access to content without overloading the page.
Priority and changefreq tags: what Google ignores in an XML sitemap
For years, XML sitemap generators have proposed two tags intended to guide search engines: priority (relative priority of a URL) and changefreq (declared update frequency). Recent technical documentation confirms that Google practically ignores these two tags.
In practical terms, assigning a priority of 1.0 to your homepage and 0.3 to your legal notices does not change the behavior of the indexing bot. Google determines crawl frequency based on its own signals: actual modification history of the page, popularity, internal and external links.
The only metadata in the XML sitemap that retains measurable utility is lastmod, provided it reflects a real content change. Filling in a fake date or updating lastmod without modifying the page sends a misleading signal that search engines learn to ignore.
What still needs to be configured
- The
lastmodtag with the actual date of the last substantial content modification, not the date of automatic republication - The exclusion of non-indexable URLs: pagination pages, faceted filters, duplicate versions by URL parameters
- Splitting into multiple sitemap files if the site exceeds the limit of 50,000 URLs per file, with an index sitemap that groups them
Site structure and navigation: the real lever for visitors
A well-constructed XML sitemap does not compensate for a confusing structure. The arrangement of categories and subcategories on a website determines how easily a visitor finds what they are looking for. A flat structure, limited to three levels deep, remains the most effective model for the majority of sites.
Beyond three levels, each additional click increases the abandonment rate. Pages buried at the fourth or fifth level also receive less internal “link juice,” reducing their chances of appearing in search results.
Categories and internal linking
The categories of a site are not just simple organizational labels. They constitute standalone, indexable pages that must contain their own content. An empty category page or one reduced to a list of links sends a low-value signal to search engines.
Internal linking, meaning the links between pages on the same site, plays a complementary role. Each strategic page should be accessible within two clicks from the homepage. Orphan pages (with no internal links pointing to them) are unlikely to ever be discovered by bots, even if they are included in the XML sitemap.
HTML Sitemap and web accessibility: an underestimated issue
The HTML sitemap is experiencing a resurgence of interest related to digital accessibility requirements. For users of screen readers or keyboard navigation, a page listing all the sections of the site provides a navigation shortcut that dropdown menus do not always replace.
Web accessibility guidelines recommend that each site offers at least two complementary navigation methods: the main menu and a sitemap or an internal search engine. The HTML sitemap directly meets this requirement without requiring complex development.
- It provides an overview of the site’s structure on a single page, accessible without JavaScript interaction
- It allows visitors disoriented by a deep structure to find a section without returning to the homepage
- It serves as a safety net when the main menu malfunctions on certain browsers or devices
Field feedback varies on the actual use of these pages by visitors. On sites with fewer than fifty pages, the HTML sitemap is rarely consulted. In contrast, on sites with high content volume (e-commerce, media, institutional portals), consultation data shows regular traffic to this page.
Structuring a sitemap, whether XML or HTML, is not just about generating an automatic file and forgetting it. The XML sitemap requires regular maintenance to reflect the actual state of the site. The HTML sitemap deserves an update with each addition of a section. Both formats serve different audiences, with different expectations, and neglecting one in favor of the other leaves part of the work unfinished.
