An XML sitemap is present on most websites, but its role goes far beyond a mere technical formality. This site map, placed at the root of the server, serves as a direct interface between your pages and indexing bots. Google, Bing, and others rely on this file to discover, crawl, and rank a site’s URLs. Without a sitemap, some pages remain invisible, especially on large sites or those with gaps in their internal linking.
The lastmod signal in the XML sitemap: an underutilized lever
The lastmod tag of the XML sitemap indicates to search engines the date of the last significant modification of a page. In theory, this signal speeds up the consideration of updates by Google. In practice, most sites generate this date automatically, with no real connection to a content modification.
See also : Why to Consult the ComplexInfo Sitemap for Efficient Web Navigation
Several specialists have recommended, since 2025-2026, either to provide a lastmod strictly aligned with the actual last modification of the content or not to use it at all. A systematically incorrect or updated lastmod with every bot visit can lead Google to completely ignore this signal, neutralizing one of the main advantages of the sitemap for speeding up indexing.
Many CMSs update the lastmod as soon as a comment is published or a plugin modifies a minor element of the page. On an e-commerce site with several thousand product listings, a reliable lastmod allows bots to focus their crawling on recently modified pages.
Recommended read : Who is Philippe Gougler's wife? An investigation into the host's private life
Sites that correctly automate this date notice better responsiveness from Google regarding changes in price, stock, or editorial content. By browsing Refair’s sitemap page, one can see an example of structuring where URLs are organized by categories with consistent modification dates.
Sitemap and crawl budget: why large sites can’t do without it
The crawl budget refers to the number of pages a search engine is willing to explore on a site during a given session. For a blog of twenty pages, this is not an issue. For an e-commerce site, a media outlet, or a SaaS platform with thousands of URLs, the sitemap becomes a management tool.
Google’s documentation on managing crawl budget, updated in 2026, positions the sitemap not just as an indexing tool but as a lever to optimize the crawling of large content bases. The file helps bots distinguish between priority pages and outdated pages.
A well-structured sitemap acts as a filter. Rather than allowing Googlebot to crawl filter URLs, pagination, or pages with no added value, the file directs the crawling towards high-value content. On complex sites, breaking the sitemap into several thematic files (one per product category, one for the blog, one for institutional pages) allows precise tracking via Search Console of which sections are being crawled correctly and which ones are problematic.
Priority and changefreq tags: fields that have become useless
For years, webmasters filled in the priority and changefreq tags in their XML sitemaps, thinking they could influence the frequency of bot visits or the indexing hierarchy. Current recommendations are clear: these two tags no longer affect Google’s behavior.
Technical experts advise against implementing them to avoid giving business teams the impression that these fields still influence crawl frequency or indexing priority. Removing them lightens the file, reduces noise, and refocuses attention on the only actionable fields:
- The URL itself (loc tag), which remains the fundamental information conveyed to search engines
- The lastmod, provided it reflects a real modification of the page’s content
- The organization into thematic sub-sitemaps, to facilitate diagnostics in Search Console
Keeping priority and changefreq tags in a sitemap does not incur a penalty, but it maintains confusion about what actually works. A minimalist sitemap, with only URLs and reliable dates, performs its role better than an overloaded file of outdated metadata.
HTML Sitemap for user navigation: a distinct format
The XML sitemap is for bots. The HTML sitemap is for visitors. This distinction is often blurred, even though the two files serve different purposes.
An HTML sitemap page lists the main sections and pages of the site in the form of clickable links. It serves as a navigation plan for users who cannot find what they are looking for via the main menu or internal search. On a site with a deep hierarchy, this page reduces the number of clicks needed to reach buried content.
From an SEO perspective, the HTML sitemap contributes to internal linking. Each link present on this page passes link juice to the target pages. For sites where certain sections are poorly connected to the rest of the hierarchy, the HTML sitemap acts as a safety net: it ensures that every important page receives at least one internal link.
The two formats are not interchangeable. A well-optimized site uses both:
- The XML sitemap, submitted in Search Console, to guide bot crawling
- The HTML sitemap, accessible from the footer, to provide an alternative access point for visitors
- A consistency between the two: URLs present in the HTML sitemap should also appear in the XML, and vice versa for high-value pages
Many sites generate an automatic XML sitemap via their CMS but do not offer any equivalent HTML page. Bots can find the pages, but lost visitors have no structured navigation recourse.
A sitemap, regardless of its format, does not compensate for a failing site architecture. It corrects gaps in crawling and navigation but does not replace a coherent internal linking structure or a thoughtfully designed hierarchy. Considering it as both a diagnostic tool and a transmission tool remains the most productive stance for technical and editorial teams.