We respect your privacy.

We use strictly necessary cookies to keep you signed in and to protect against CSRF. With your permission we also use a small amount of first-party analytics to improve the product. We do not sell your data and we do not use third-party advertising trackers. See our cookie policy and privacy policy .

Crawlmind
← All learn topics

Rule site.sitemap.stale

Keep sitemap <lastmod> dates accurate

site.sitemap.stale is a check in Crawlmind's site audit that grades low-impact issues of this kind. This page explains why the rule matters and the exact fix.

Impact: lowEffort: low

Why it matters

Crawlers and AI indexers use `<lastmod>` to decide what to re-fetch. When the newest date in your sitemap is over six months old, they assume nothing has changed and revisit less often — so genuinely updated pages keep serving a stale copy to search and AI answers. Accurate `<lastmod>` is one of the cheapest freshness signals you can send.

The fix

Emit a real `<lastmod>` (ISO-8601) per URL, updated whenever the page changes:

```xml
<url>
  <loc>https://example.com/pricing</loc>
  <lastmod>2026-07-01</lastmod>
</url>
```

Most frameworks and CMSes can generate this from the page's real modified date — wire it to your content's `updatedAt`, not the build time (a build-time stamp makes every page look freshly changed and is ignored). For instant propagation on Bing/Copilot, also ping IndexNow when a page changes.

References