A sitemap, whether visible to visitors or intended for indexing bots, serves a specific technical function: mapping all the pages of a website to facilitate access. Its most well-known form, the XML sitemap file, acts as a guide for search engines. The HTML version, on the other hand, is aimed at users lost in a too-deep hierarchy.
The two formats coexist, but their actual role in navigation and organic search deserves a more detailed examination than the usual generalities.
Crawl budget and XML sitemap: what Google really consumes
The XML sitemap does not guarantee the indexing of a page. Its main role is to guide the expenditure of the crawl budget, which is the number of requests that Googlebot allocates to a site during each visit. On a site with several thousand pages, some orphaned URLs or those buried more than four clicks from the homepage may never be explored without this map.
A point often overlooked: Google removed the sitemap ping endpoint in 2023 (confirmed in early 2024). The URL /ping?sitemap= now returns a 404 error. Plugins and automations that relied on this mechanism to signal an update have become useless. Submission now occurs exclusively through the Search Console or by declaration in the robots.txt file.
For sites whose navigation structure relies on an IQ Business sitemap, the logic remains the same: each URL must appear in the sitemap if it deserves to be indexed, and no page blocked by a noindex or disallow should be included.
Lastmod tag in the sitemap: signal of freshness or unnecessary noise
The <lastmod> tag indicates to search engines the date of the last modification of a page. Google specifies to use it only if the value is consistently and verifiably accurate. A CMS that updates this date with every minor record (fixing a comma, changing a widget in the sidebar) sends a misleading signal.
The modification must reflect a significant change in content or structured data. Changing the copyright date at the bottom of the page does not count. Field reports vary on this point: some SEOs notice a faster recrawl after updating lastmod, while others observe no measurable difference.
What is documented, however, is the inverse risk. A systematically incorrect lastmod causes Google to completely ignore this tag for the entire site. The engine compares the declared date to the last cached version. If the discrepancy is recurrent, the signal loses all value.
Check the reliability of lastmod on your own site
- Compare the lastmod date of about ten pages with the actual last modification date in the CMS, excluding automatic updates (plugins, themes).
- Ensure that pages whose content has not changed for several months do not display a recent date in the sitemap.
- Use server logs to cross-reference Googlebot visits with lastmod dates: a recrawl following a lastmod update confirms that the signal is being taken into account.
Technical limits of the XML sitemap: size, segmentation, and performance
The sitemaps.org specification, unchanged since November 2016, sets two limits per file: 50,000 URLs and 50 MB uncompressed. Google confirms these limits in its documentation verified in 2026. A site that exceeds these thresholds must use a sitemap index, a parent file that points to multiple child sitemaps.
Segmentation is not just a volume constraint. Segmenting sitemaps by content type (articles, product sheets, category pages) allows tracking the indexing rate by section in the Search Console. This granularity reveals areas of the site that Google explores little, and those it prioritizes.
A single sitemap of 48,000 mixed URLs provides no actionable data. In contrast, section-based segmentation makes SEO diagnostics immediate: if product sheets show a low indexing rate while all blog articles are indexed, the problem lies in the structure of the sheets or their internal linking.
HTML sitemap: real utility for user navigation
The HTML sitemap is often relegated to the footer as a relic of the 2000s. Its utility for SEO is marginal on a site whose hierarchy and internal linking function correctly. However, it remains relevant for sites with deep or heterogeneous structures, where some pages are only accessible via an internal search engine.
For the user, an HTML sitemap functions like a table of contents. It displays the complete hierarchy of the website on a single screen. On an institutional site with several dozen sections, this overview reduces the number of clicks needed to reach a specific page.
When the HTML sitemap becomes counterproductive
An HTML sitemap that lists hundreds of links without logical grouping produces the opposite effect: it overwhelms the visitor instead of guiding them. The page should replicate the navigation structure of the main menu, with an additional level of detail. If the list exceeds what the user can scan in a few seconds, the sitemap becomes an obstacle.
The available data does not allow us to conclude that Google assigns direct SEO weight to the HTML sitemap page. Its interest remains focused on user experience and the discovery of poorly linked pages in the hierarchy.
The XML file and the HTML page serve two distinct audiences. Confusing their functions means optimizing for no one. The former structures the crawl, the latter structures human navigation. A site that rigorously maintains both covers both dimensions without redundancy.
