Skip to content
LLMSRank
Docs menu

Sitemap freshness

sitemap.xml present with plausible lastmod

In short: Publish sitemap.xml with a lastmod on every entry, set from each page’s real last edit rather than the deploy time.

  • Category: Ecosystem Integration · weight 18 of 100 within the category
  • Ecosystem Integration is worth 20 in technical, 15 in generic, regulated and commerce (points of 100, by scoring profile)
  • Audit ID E2 (as shown on reports) · rubric v2.1

What it checks

Whether sitemap.xml is present and its lastmod dates are plausible.

Why it matters

Agents and crawlers use the sitemap to find pages and judge how fresh they are. Missing or fake lastmod dates (every page stamped with the build time) make that impossible.

When it applies

Always, in principle. In practice E2 needs a sitemap we could read: with no readable entries it’s Unverified. Index children we did archive count even when the index is incomplete.

An audit that doesn't apply, or that we couldn't verify, is removed from your score and its weight shared among the Ecosystem Integration audits that do apply. It is never scored as a zero.

How it's scored

Presence + lastmod coverage + plausibility: 0.4 readable · + 0.3 × lastmod coverage · + 0.3 × plausible share (v1.1). A lastmod is plausible when it’s a valid W3C date, not after the capture day, and not one timestamp shared by 90% or more of a 10+ page sitemap.

How to fix

  1. Publish sitemap.xml at the root and reference it from robots.txt.
  2. Give every entry a lastmod in W3C format (2026-09-01 or a full timestamp).
  3. Set lastmod from the page’s real last edit, not the deploy time.

Example

<url>
  <loc>https://acme.com/refunds</loc>
  <lastmod>2026-08-14</lastmod>
</url>

Frequently asked questions

What date should each sitemap lastmod carry?
The date the page’s content last really changed, in W3C Datetime format (2026-09-01, or a full timestamp such as 2026-09-01T14:20:00+00:00), not the time the sitemap was generated; the sitemaps.org protocol says exactly that. Google uses lastmod only when it is “consistently and verifiably accurate,” and counts changes to main content, structured data or links as significant, but not a new copyright year.

Sources: sitemaps.org — Sitemaps XML format · Google Search Central — Build and submit a sitemap · W3C — Date and Time Formats (W3C Datetime)

Why does stamping every page with the deploy time lower my sitemap freshness score?
Because a build time says nothing about when pages changed. When one identical lastmod value is shared by 90% or more of the dated entries in a sitemap with 10 or more of them, we treat it as a build stamp and count those entries as implausible, as we do dates that aren’t valid W3C dates or fall after the day we captured the sitemap. Take lastmod from your CMS’s edit time or the page source’s last commit instead. The consistency checker lists each lastmod mismatch with the exact line to fix.

Sources: sitemaps.org — Sitemaps XML format · LLMSRank — Sitemap freshness audit

How exactly is sitemap freshness scored?
0.4 for a readable sitemap, plus 0.3 × the share of entries that have a lastmod, plus 0.3 × the share of those lastmods that are plausible. A sitemap with no lastmod at all scores 0.4; one where every entry has a valid, non-future date that isn’t a build stamp scores 1.0. If we can’t read any sitemap entries the audit is Unverified: removed from your score, never counted as a zero.

Sources: LLMSRank — Sitemap freshness audit · LLMSRank — How we score (rubric v2.0)

Where does LLMSRank look for my sitemap, and do sitemap index files work?
We use the first Sitemap: line in your robots.txt, or /sitemap.xml at your origin if there is none, so declaring it in robots.txt (as the sitemaps.org protocol allows) removes any guesswork. A sitemap index is followed one level down to its child sitemaps (the first 10 in our corpus capture), and the children we could read count toward this audit even when the index is incomplete. A sitemap your own robots.txt disallows can’t be read and leaves the audit Unverified.

Sources: sitemaps.org — Sitemaps XML format · LLMSRank — Sitemap freshness audit

How plausible are sitemap lastmod dates across sites, in LLMSRank’s research?
In our 187-site research corpus (rubric v2.1; sitemaps captured 2026-09-28), 129 sites had a sitemap we could read and 58 were Unverified — more of them than in July, because the corpus has grown faster than our sitemap captures have. 62 of the 129 (48.1%) earned full marks, with a lastmod on every entry and no build stamp, and the mean score was 0.84. Good examples include aflac.com, taylormorrison.com, developers.deepl.com, zapier.com and www.khov.com.

Sources: LLMSRank — How we score (rubric v2.0) · LLMSRank — Sitemap freshness audit