An XML sitemap lists the URLs of a site to guide indexing bots. However, not all the tags it contains carry the same weight in Google’s eyes, and its usefulness varies greatly depending on the size of the site and the freshness of its content. Measuring what the sitemap truly contributes to natural referencing requires distinguishing what the engines utilize from what they ignore.
XML Sitemap Tags: What Google Really Uses
The sitemap protocol provides several tags for each URL: loc, lastmod, changefreq, and priority. Their processing by search engines differs significantly.
| Tag | Declared Role | Considered by Google |
|---|---|---|
| loc | Page URL | Yes, the only mandatory tag |
| lastmod | Date of last modification | Yes, if it reflects a real change in the main content |
| changefreq | Estimated update frequency | No, Google ignores it |
| priority | Relative importance of the page | No, Google ignores it |
According to Google Search Central documentation (consulted in July 2026), changefreq and priority do not serve to determine crawl frequency or the importance of a URL. They can remain in the file without causing an error, but they do not influence Googlebot’s behavior.
The lastmod tag, on the other hand, can guide crawling if it corresponds to a verifiable change: modification of the main content, structured data, or internal links. An artificially updated lastmod, without any real change to the page, will eventually be ignored. Google’s documentation indicates that the reliability of this tag becomes an issue, as some sites modify it to attempt to trigger a recrawl without justification.
For those who wish to delve deeper into indexing mechanisms and the technical setup of a sitemap, it is possible to discover the site Référencement Qualitatif which covers these topics in detail.
Sitemap and Google Search Console: A Diagnostic Tool, Not Just Submission
Most guides present the submission of the sitemap in Google Search Console as a simple declaration step. This view is incomplete.
Google Search Central specifies that the Search Console allows you to monitor the date of the last access of Googlebot to the sitemap as well as any processing errors. This feedback helps detect concrete issues: an inaccessible sitemap (server error), URLs returning 404 codes, or a file that has not been recrawled for several weeks.
In practice, a submitted sitemap that is never revisited in the Search Console loses much of its value. The file itself is not enough: it is the monitoring of its processing that makes the system useful for referencing.
Signals to Monitor in the Sitemap Report
- The number of URLs discovered compared to the number of URLs submitted, which reveals potential orphaned or erroneous pages
- The date of the last access by Googlebot, which indicates whether the engine is still actively consulting the file
- Warnings or errors reported by Google, such as URLs blocked by the robots.txt file or chain redirects
XML Sitemap and IndexNow: Two Complementary Mechanisms for URL Discovery
A sitemap provides a static overview of the site. It lists existing URLs and their last modification date. For sites that frequently publish or update content, this mechanism has a limitation: the sitemap does not notify engines in real-time.
Bing recommends complementing the sitemap with IndexNow, a protocol that signals to participating engines the additions, updates, or deletions of URLs as they occur. The sitemap and IndexNow do not replace each other: the former provides the complete map, while the latter sends a timely signal of change.
| Criterion | XML Sitemap | IndexNow |
|---|---|---|
| Type of Signal | Complete list of URLs | Unit notification of change |
| Frequency | Periodically consulted by bots | Sent with each modification |
| Compatible Engines | Google, Bing, Yandex, etc. | Bing, Yandex, and participating engines |
| Main Use Case | Sites of all sizes | Sites with frequent publication |
Google does not support IndexNow at this time. For sites whose traffic primarily comes from Google, the sitemap remains the main technical discovery channel. However, for sites that also target Bing or Yandex, combining the two mechanisms speeds up the consideration of new pages.
Reliable Lastmod or Cosmetic Lastmod: A Gap That Affects Crawling
The temptation to update the lastmod tag with each regeneration of the sitemap, without any real content modification, is common. Some CMS do this by default. This practice dilutes the trust that Googlebot places in this information.
A reliable lastmod reflects a significant modification: rewriting a paragraph, adding structured data, correcting an internal link. A cosmetic lastmod, triggered by a minor change (sidebar widget, footer), adds nothing and may lead the bot to gradually ignore this tag across the entire site.
The difference between the two approaches can be measured in the Search Console: a site with a reliable lastmod generally sees its new pages crawled more quickly than a site where this tag changes constantly without reason.
- Check that the CMS only updates lastmod when there is a real change in the main content
- Exclude from the sitemap pages without SEO value (tag pages, empty paginated archives)
- Regularly compare the number of submitted URLs and the number of indexed URLs in the Search Console
The XML sitemap does not improve a page’s ranking by itself. Its role is to ensure that the right pages are discovered, crawled, and followed over time. The value of the sitemap lies in the quality of the signals it transmits, not in its mere existence. A submitted, monitored, and maintained file with reliable lastmod data constitutes a measurable technical lever. A file generated once and forgotten provides almost nothing.
