A sitemap, whether in HTML format for visitors or XML for indexing bots, serves two distinct functions that are often confused. The first is structural: to provide direct access to all pages of a site without relying on the main menu. The second is technical: to provide search engines with metadata about each URL, including the last modified date. Measuring the gap between these two uses helps to understand why some sitemaps actually aid SEO, while others degrade it.
Misleading sitemap and freshness signal: what engines detect
The lastmod tag in an XML sitemap indicates to bots the actual last modified date of a page. Google Search Central specifies that this date should reflect a significant change in content, not a simple automatic regeneration of the file.
The practice of listing the current date on all URLs, without any real content modification, tends to erode trust in the lastmod signal. A search engine that sees hundreds of pages displaying the same daily modification date eventually ignores this data entirely for the domain in question.
When you want to access the sitemap of Tous les Faits, you access a structured index that reflects the actual hierarchy of published content, with dates corresponding to actual updates.
In contrast, Bing takes a stricter approach. Its recent recommendations emphasize a complete ISO 8601 date format, including time and time zone. Bing also requires at least daily updates for content that actually changes. This divergence between Google and Bing means that the same sitemap can be treated differently depending on the engine.
Comparison of Google and Bing requirements for XML sitemap
| Criterion | Bing | |
|---|---|---|
| lastmod date format | Simple date (YYYY-MM-DD) accepted | Complete ISO 8601 with time and time zone recommended |
| Reaction to identical dates across all URLs | Gradually ignores the lastmod signal for the domain | May reduce the site’s crawl frequency |
| Expected update frequency | Only for significant changes | At least daily for evolving content |
| priority tag | Ignored | Considered in a limited way |
| changefreq tag | Ignored | Used as a secondary indication |
This table shows a notable gap. Google simplifies: only the reliable lastmod date matters. Bing, on the other hand, utilizes more tags and expects finer temporal granularity. Optimizing a sitemap for one engine is not enough if your audience comes from multiple sources.
When the priority tag is useless
Google has confirmed that it ignores priority and changefreq tags in XML files. Many automatic generators continue to fill them with default values (0.5 for priority, “weekly” for changefreq). These lines bloat the file without providing any benefit on Google’s side.
Bing still reads them, but their weight remains marginal compared to lastmod. Spending time calibrating priority page by page represents a disproportionate effort relative to the actual gain.
HTML navigation versus XML indexing: two sitemaps not to be confused
The HTML sitemap is a page accessible to visitors, listing the sections and subsections of the site. Its role is to compensate for the limitations of a navigation menu, especially on sites with several hundred pages. A visitor lost in a deep hierarchy can find their way by consulting this single page.
The XML sitemap, on the other hand, is never seen by visitors. It is aimed exclusively at indexing bots. Its technical content (canonical URLs, dates, metadata) has no utility for a human.
- The HTML sitemap enhances user experience by providing a comprehensive view of the site’s structure, which reduces the bounce rate on sites with complex hierarchies.
- The XML sitemap accelerates the discovery of new pages by engines, particularly useful for new sites with few inbound links.
- Both formats complement each other: removing one in favor of the other creates a blind spot, either for visitors or for bots.
On a site with fewer than fifty pages and clear navigation, the HTML sitemap adds little value. The XML sitemap remains useful regardless of the number of pages, if only to signal updates to engines.
Reliable lastmod dates: distinguishing real updates from automatic regeneration
The majority of CMS regenerate the XML sitemap with each publication or modification, including for minor changes (correcting a typo, adding a tag). The problem arises when this regeneration updates the lastmod date of pages that have not changed substantially.
For a lastmod date to be considered a true freshness signal, it must correspond to a visible modification of the main content of the page. Adding a paragraph, updating data, redesigning a section: these interventions justify a new date.
- Modifying only the footer or sidebar does not constitute a significant change in the eyes of engines.
- Changing the displayed publication date without touching the content (fake freshness) is identified as a spam practice by Google.
- A sitemap whose lastmod dates reflect real changes maintains its credibility with bots over the long term.
How to check the consistency of your sitemap
Comparing the lastmod date of a URL in the sitemap with the last modified date visible on the page itself allows you to spot inconsistencies. If the sitemap shows a recent date but the content hasn’t changed for months, the signal sent to engines is contradictory.
The tools in Search Console (for Google) and Bing Webmaster Tools report format errors and anomalies in submitted files. Regularly checking these reports prevents a misconfigured sitemap from going unnoticed for months.
A sitemap, whether intended for visitors or engines, only fulfills its role if it accurately reflects the structure and state of the content. An accurate sitemap for twenty pages is more helpful than an inflated sitemap for a thousand outdated URLs. The reliability of the file takes precedence over its size.
