A sitemap serves two distinct functions that are often confused: guiding a human visitor to the right page and signaling to crawlers which URLs to explore. Measuring the gap between these two uses helps to understand why some sites remain partially invisible despite an apparently correct structure. This article compares the HTML sitemap (intended for users) and the XML sitemap (intended for search engines), then details the technical criteria that make each truly useful.
HTML Sitemap and XML Sitemap: Two Tools, Two Logics
The HTML sitemap is a standard web page, readable by any visitor. It lists sections and subsections in the form of clickable links. Its role is to provide an overview of navigation, especially for people using a screen reader or navigating via keyboard.
The XML sitemap, on the other hand, is never displayed in a browser. It is a technical file submitted to search engines via the Search Console or the robots.txt file. It contains the list of URLs that the site wants to be crawled.
| Criterion | HTML Sitemap | XML Sitemap |
|---|---|---|
| Target Audience | Human Visitors | Crawling Bots (Googlebot, Bingbot) |
| Format | HTML Page with Hyperlinks | Structured XML File |
| Size Limit | No formal limit | 50,000 URLs / 50 MB uncompressed |
| Direct SEO Impact | Internal Linking, Accessibility | Crawl Signal (not a guarantee of indexing) |
| Update | Often manual or semi-automatic | Automatic generation by CMS or plugin |
The most common confusion is believing that an XML sitemap is enough to get all its pages indexed. According to Google Search Central documentation, an XML sitemap serves as a crawl signal, not a firm instruction. Google is free to ignore certain listed URLs if it deems their content to be of low quality or detects conflicting signals (noindex tag, redirection, blocked by robots.txt).
A blog like the one presented on the Lordy’s sitemap illustrates this complementarity well: the HTML sitemap page gives the reader quick access to all sections, while a separate XML sitemap feeds the bots in the background.
XML Sitemap: Technical Errors That Sabotage Crawling
Generating an XML sitemap takes a few seconds with most CMS. Keeping it clean requires regular vigilance. Three errors consistently arise.
Non-canonical or Redirected URLs
URLs listed in a sitemap must return a 200 status, be canonical and indexable. Including pages with 301 redirects, URLs blocked by robots.txt, or with a noindex tag sends conflicting signals to the crawler. The crawl budget is wasted on pages that the engine cannot process.
Exceeding File Limits
Google sets the limit at 50,000 URLs and 50 MB uncompressed per sitemap file. For sites exceeding this threshold, the solution recommended by Google Search Central is to create a sitemap index file that points to multiple child files. Ignoring this constraint leads to partial abandonment of crawling.
Failure to Update After Content Deletion
Deleting a page without removing its URL from the sitemap generates 404 errors in the Search Console. These errors do not directly penalize rankings, but they clutter coverage reports and obscure real indexing issues.
- Check monthly that the sitemap contains no URLs with 404, 301, or noindex
- Separate sitemaps by content type (pages, articles, images) to facilitate diagnosis
- Submit the sitemap in the Search Console after each structural change to the site
User Navigation: What Makes an HTML Sitemap Truly Useful
A poorly designed HTML sitemap resembles an endless list of links without hierarchy. To improve navigation, it must adhere to a few principles that go beyond a simple inventory of pages.
Readability relies first on thematic grouping. A visitor arriving at a sitemap is looking for a category, not an isolated page title. Organizing links by main section, then by subsection, replicates the logic of the menu structure without forcing the user to navigate page by page.
Screen reader users benefit the most from a well-structured sitemap. Navigating an entire site by tabbing from one interactive element to another takes considerable time. A sitemap page with consistent heading levels (H2 for sections, H3 for subsections) allows users to jump directly to the relevant section.
Another often overlooked point: the HTML sitemap is not a duplicate of the navigation menu. The menu exposes priority pages. The sitemap, however, can include secondary pages (legal notices, privacy policy, blog archives) that do not appear in the main menu but that some visitors are searching for.
Structure and Click Depth: The Link Between Structure and SEO
Click depth refers to the number of clicks needed to reach a page from the homepage. Reducing click depth improves both user experience and the crawling frequency by bots. A page accessible in two clicks will be crawled more regularly than a page buried at the fourth level.
In practice, this means that the category structure should remain as flat as possible. Multiplying sub-subcategories for the sake of classification creates deep silos where content stagnates without receiving sufficient internal links.
- Aim for a maximum of three levels of depth for pages with high SEO stakes
- Use the HTML sitemap as a safety net: any important page should be included, even if it is accessible via the menu
- Check the “Crawl Stats” report in the Search Console to identify pages that are rarely visited by Googlebot
A sitemap, whether HTML or XML, does not fix a flawed structure. It makes it visible. The site structure precedes the sitemap, not the other way around. Fixing a click depth issue by simply adding a link in the XML sitemap will change nothing if the internal linking remains poor. The sitemap functions as a diagnostic tool: if it is difficult to organize in a readable way, it is likely that the navigation itself needs to be rethought.