An e-commerce site with several hundred product pages, a recent redesign that changed all the URLs, and an internal search engine that does not return the right results. We’ve all encountered situations where finding a specific page is a real challenge. This is exactly the use case where a well-constructed sitemap page makes a difference, both for visitors and for indexing bots.
When internal linking is no longer enough, the sitemap takes over
On a site with fewer than twenty pages, the main navigation does the job. The problem arises as the structure becomes more complex: pages buried three clicks deep, archived articles that no longer appear in any menu, seasonal product pages removed from the catalog but still online.
In these cases, an HTML sitemap provides direct access to all published pages. We are talking about a page that can be viewed by a human, not just an XML file intended for bots. The difference is significant: a visitor who cannot find what they are looking for via the menu or search bar can scan the complete list of sections and spot the right URL in a matter of seconds.
To see what this approach looks like on an editorial site, you can check the sitemap page of Carré Presse, which organizes its content by category and provides an immediate overview of the site’s structure.
This type of page also fulfills an accessibility criterion that is often overlooked. The WCAG 2.2 guidelines, particularly success criterion 2.4.5 (“Multiple Ways”), explicitly mention the sitemap as a valid mechanism for providing multiple paths to the same page. Main navigation, search, and sitemap form a complementary trio, not redundant.
XML sitemap and HTML sitemap: two files, two audiences, one goal
The confusion between XML sitemap and HTML sitemap remains common. The XML file is a technical document, submitted to Google via the Search Console or declared in the robots.txt file. It lists URLs with metadata (last modified date, relative priority, update frequency).
The HTML sitemap page, on the other hand, displays in the browser like any other page on the site. It is aimed at visitors and serves as a backup plan when traditional navigation fails.
- The XML sitemap helps search engines discover pages that natural crawling might miss, especially on large or poorly linked sites.
- The HTML sitemap enhances the user experience by providing a flat view of the structure, useful for sites whose menu does not reflect the full depth of content.
- Both formats coexist without conflict. Maintaining both is the most robust setup to cover both indexing and human navigation.
What Google really expects from an XML sitemap
One point that most guides do not update: Google treats the submission of a sitemap as a mere hint, not as a guarantee of crawling or indexing. The file signals URLs to explore, but the engine decides on its own whether to visit them, based on its own quality criteria and crawl budget.
The old “ping” mechanism (the URL /ping?sitemap=… that could be called to signal an update) was deprecated in 2023. The two channels that remain operational are declaration in robots.txt and direct submission via the Search Console or its API.
Structuring an HTML sitemap page to make it truly useful
Creating a page that lists all URLs in bulk adds no value. We have seen HTML sitemaps with thousands of lines without any grouping: no one uses them, neither visitors nor bots.
The effective logic relies on grouping by category or type of content. On an editorial site, we separate main sections (news, guides, files). On an e-commerce site, we group by product family. The goal: for a visitor to identify the right section in less than five seconds.
Common mistakes that render the sitemap useless
- Listing 404 URLs or redirects: this undermines visitor trust and sends a bad signal to bots.
- Including utility pages (legal notices, cookie policy, login pages) at the same level as editorial content. They clutter the reading without adding navigational value.
- Never updating the page after adding new sections. An outdated sitemap is worse than no sitemap at all, because it gives a distorted image of the site.
Feedback varies on the ideal update frequency, but a monthly check on an active site allows for the identification of broken links and missing sections before they accumulate.
Sitemap and crawl budget: concrete impact on indexing deep pages
On a site with a few dozen pages, crawl budget is not an issue. On a site that exceeds several hundred URLs, the situation changes. Bots do not systematically explore every page on each pass. Orphan pages (without internal links pointing to them) risk never being discovered.
The XML sitemap acts here as a safety net. It does not replace good internal linking, but it compensates for its shortcomings. Declaring a page in the XML sitemap does not guarantee its indexing, but it ensures that it will at least be proposed for crawling.
The HTML sitemap plays a complementary role on the linking side. Each link present on this page transmits internal PageRank. On a site where the main navigation does not go beyond two levels deep, the sitemap page creates a direct shortcut to the most buried pages.
The combination of both formats produces a result that neither can achieve alone: XML facilitates discovery by bots, HTML distributes internal juice and offers an entry point for lost visitors. On a regularly updated site, this dual coverage remains the most reliable setup to prevent recent or deep content from remaining invisible.
