You are looking for a specific page on a site and you come across a menu that does not list it. The internal search engine returns approximate results. Frustration builds. The sitemap resolves this issue by exposing all accessible URLs, both for visitors and crawlers.
HTML Sitemap and XML Sitemap: Two Distinct Uses for Navigation
The term “sitemap” encompasses two realities that need to be distinguished from the outset. The HTML sitemap is a human-readable page. It displays the site’s links in a hierarchical list format, like a table of contents. When a menu is no longer sufficient, this page allows you to find buried content in just two clicks.
The XML sitemap, on the other hand, is aimed at search engines. It is a structured file that lists each URL along with technical metadata, such as the last modified date. Google, Bing, or other crawlers read this file to discover the site’s pages.
For a user wanting to navigate, it is the HTML sitemap that matters. For example, you can visit Jean-Louis Garret’s sitemap page to see all available sections at a glance, without going through the main menu.
The XML sitemap does not display in a browser in a readable way. It works behind the scenes. The two formats complement each other, but their audiences are different.
What the Sitemap Reveals About a Website’s Architecture
Have you ever visited a site with dozens of sections without understanding how they fit together? The HTML sitemap works like a floor plan. It shows the hierarchy: which page depends on which section, which contents are grouped together.
This overview makes visible what traditional navigation hides. A menu displays five or six entries. The sitemap, however, reveals the entire structure of the site, including deep pages that are rarely linked from the homepage.
In practical terms, this helps in three situations:
- You are looking for an old article on a blog that publishes regularly, and the internal search engine returns nothing relevant.
- The site has been recently restructured, and some links in the menus no longer point to the correct sections.
- You want to compare several pages of the same site (product sheets, services, categories) without navigating page by page.
A well-designed sitemap transforms an opaque site into a transparent one.
XML Sitemap and Search Engines: A Discovery Signal, Not a Guarantee
From an SEO perspective, the XML sitemap plays a role that many overestimate. Google’s documentation states clearly: submitting a sitemap does not guarantee either crawling or indexing of the listed URLs. The file serves as a discovery signal. It tells crawlers that these pages exist. Nothing more.
Google recommends two methods for making an XML sitemap accessible: submitting it via Search Console or declaring it in the robots.txt file. The old ping notification system was abandoned in 2023.
When the XML Sitemap Becomes Really Useful
For a small site with a few pages and a solid internal linking structure, the XML sitemap does not add much. Crawlers find the pages by following the links.
The situation changes for large sites or those that publish content frequently. When hundreds of pages are created each month, the XML sitemap helps search engines quickly spot new URLs. It is also valuable when some pages are orphaned (without internal links pointing to them).
The XML sitemap serves as a safety net for pages poorly linked to the rest of the site. If your internal linking is complete, the XML file remains useful for tracking, not for discovery.
Reading an XML Sitemap in Search Console: Three States, No More
Once the sitemap is submitted to Google Search Console, the associated report displays a deliberately limited diagnosis. Three possible states:
- Success: the file has been read and the URLs have been taken into account as discovery signals.
- Error: the file contains a syntax issue or inaccessible URLs.
- Unable to retrieve: Google could not download the file (server issue, incorrect URL, blocked in robots.txt).
No intermediate alerts, no quality score. This minimalist diagnosis often surprises. It means that the actual tracking of indexing goes through other reports in Search Console, such as the coverage report.
Checking lastmod Dates and Canonical URLs
Recent SEO guides emphasize a point often overlooked: the XML sitemap also functions as a governance tool for the inventory of URLs. Checking that the lastmod tags correspond to the actual modification dates avoids sending misleading signals to crawlers.
Similarly, including in the sitemap URLs that are not the canonical versions (for example, a URL with parameters instead of the clean URL) creates confusion. A reliable sitemap only lists canonical URLs, up-to-date, and truly accessible.
Double Declaration in robots.txt and Search Console
The current best practice combines two approaches. Submitting the sitemap in Search Console allows you to track its status. Declaring it also in the robots.txt file broadens discovery to other search engines that do not have an equivalent of Search Console.
This dual “discovery + control” logic covers both needs. The robots.txt makes the sitemap accessible to any crawler that reads it. Search Console provides operational feedback on what Google does with it.
For a website aiming for visibility beyond Google, this step takes a few seconds and presents no drawbacks. Declaring the sitemap in robots.txt remains the most universal method to make it discoverable by all search engines.
The sitemap, whether HTML or XML, serves a simple role: to make visible what exists. For the user, it is a shortcut to the right page. For search engines, it is a list of suggestions. Neither replaces a well-thought-out site architecture, but both correct its blind spots.