An XML sitemap lists a website’s URLs so that crawlers can discover them faster. However, not all sitemaps are created equal: a poorly constructed file or one filled with outdated fields can confuse the signals sent to Google instead of clarifying them. Measuring the gap between a properly configured sitemap and a neglected one helps to understand why this technical file remains a concrete lever for indexing.
XML sitemap fields: what Google really uses
The XML sitemap protocol includes several fields for each URL: loc, lastmod, changefreq, and priority. In practice, search engines do not treat these fields the same way.
| Field | Initial Role | Use by Google (2026) |
|---|---|---|
| loc | Page URL | Systematically used for discovery |
| lastmod | Date of last modification | Used only if the date corresponds to a real and verifiable change |
| changefreq | Estimated update frequency | Ignored by Google |
| priority | Relative importance of the page | Ignored by Google |
Google Search Central documentation confirms this: changefreq and priority do not influence crawling or ranking. Many guides still recommend filling in these two fields, which provides no measurable benefit. Spending time ensuring the reliability of lastmod has a much more direct effect on crawl frequency.
To see how a site concretely structures its XML file with the right fields, the sitemap page of Nouvelle Jeunesse provides a telling example.
Reliability of the lastmod field: the underestimated freshness signal
Google indicates that it uses the lastmod date when it consistently and verifiably corresponds to the last significant modification of the page. A simple automatic regeneration of the sitemap or an update of the copyright date does not count as a relevant change.
This point changes the game for several categories of sites:
- Product catalogs whose prices or availability change frequently lose credibility if the lastmod is updated with each regeneration of the file without any real change on the page.
- News sites that change a date without touching the editorial content send a misleading signal, which can slow down the recrawl of pages that have actually been updated.
- Showcase sites with few modifications benefit from updating the lastmod only when there is a visible change (new paragraph, corrected price, replaced image).
A reliable lastmod accelerates the discovery of real changes. An artificially inflated lastmod dilutes the crawler’s trust in the entire file.
Canonical and indexable URLs: filtering what goes into the sitemap
A sitemap can be technically valid while degrading the signals sent to search engines. The problem arises when the file includes URLs that should not be there.
Recent recommendations, including those from Bing, state that only canonical and indexable URLs should be included in the sitemap. This means excluding noindex pages, duplicate filtered URLs, old redirects, and paginated archive pages without unique content.
Why an inflated sitemap harms crawl budget
Each URL listed in the sitemap consumes a fraction of the crawl budget allocated by search engines. On a site with a few dozen pages, the impact remains negligible. On a catalog of several thousand product listings, including non-indexable URLs amounts to wasting crawl requests on pages that Google will ultimately ignore.
Removing non-canonical URLs from the sitemap focuses the crawl on the pages that matter.
XML sitemap and IndexNow protocol: two complementary mechanisms
The XML sitemap remains a passive file: it waits for the crawler to come and read it. For sites with frequently changing content, this waiting can delay the acknowledgment of changes. The IndexNow protocol, adopted by Bing, allows for actively notifying the search engine that a URL has been modified or created.
The two mechanisms do not replace each other. The sitemap provides a permanent overview of the site’s structure. IndexNow sends a one-time signal for a specific URL. Combining a reliable sitemap with IndexNow notification covers both global discovery and responsiveness to specific updates.
Google has not adopted IndexNow but uses its own indexing API system for certain types of content (job postings, live broadcasts). Therefore, the XML sitemap remains the common denominator accepted by all major engines.
Checking that the sitemap is actually read by search engines
Submitting a sitemap in Google Search Console does not guarantee that it will be utilized. The tool displays the number of submitted URLs and the number of indexed URLs, allowing for measuring the gap between intention and result.
Three concrete checkpoints:
- Check in Search Console that the status of the sitemap is “Success” and not “Fetch error” or “Contains errors”.
- Compare the number of submitted URLs to the number of indexed URLs. A significant gap indicates non-canonical, noindex, or redirected URLs.
- Check the date of the last read of the sitemap by Google. If this date is old, the file may have been abandoned by the crawler.
The gap between submitted URLs and indexed URLs is the first quality indicator of a sitemap. A ratio close to 1 means that the file contains only useful pages. A low ratio indicates a need for cleanup.
The XML sitemap is not a file to be generated once and then forgotten. Its value directly depends on the rigor applied to the included URLs, the reliability of the lastmod field, and regular monitoring in Search Console. A clean and up-to-date file remains the most direct way to guide crawlers to the pages that deserve to be indexed.
