Sitemap lastmod Freshness
<lastmod> dates in your sitemap signal content freshness to crawlers. AI assistants prefer fresher content per the Ahrefs 17M-citation study. SaaSalyst checks how many sitemap entries have valid ISO 8601 lastmod dates.
What SaaSalyst Checks
SaaSalyst fetches your sitemap (declared in robots.txt or /sitemap.xml fallback) and counts <url> entries with a valid ISO 8601 <lastmod> element. The check passes when ≥50% of entries have lastmod, warns at 20–50%, and fails below 20%. Sitemap-index format is treated separately (sub-sitemap probing deferred to a future scanner improvement).
Why This Matters
Empirical support: Ahrefs analyzed 17M AI citations and found AI assistants prefer 25.7% fresher content over older content of equal authority. Seer Interactive's 5K-URL crawl study found 65% of AI bot hits were on content modified within the past year.
lastmod tells crawlers "this page changed on this date." Crawlers prioritize re-fetching pages with recent lastmod, and AI systems weight freshness in citation decisions. A sitemap full of pages with no lastmod (or stale lastmod from 2019) signals "this site doesn't update much" — and AI assistants down-weight it.
This is a traction signal because populating lastmod requires real content update discipline, not just running a sitemap generator. Fakes (hard-coded "2026-01-01" on every entry) are detectable and counterproductive.
How to Fix It
- Configure your sitemap generator to emit <lastmod> based on actual page modification dates (not the sitemap generation date).
- Use ISO 8601 format: 2026-04-27 or 2026-04-27T12:34:56+00:00. SaaSalyst rejects non-ISO formats.
- Update lastmod when you actually modify content — not on every build. Stale or fake lastmod is worse than missing lastmod.
- For dynamic pages (blog posts, product pages), tie lastmod to the database updated_at column or equivalent.
Frequently Asked Questions
Will SaaSalyst penalize me if I fake lastmod dates?
SaaSalyst doesn't currently detect faked lastmod (e.g., setting all entries to today's date). But search engines and AI crawlers do: they cross-reference lastmod with actual content changes, and persistent fake dates lower trust scores. Treat lastmod as a real signal, not a SEO trick.
Why is this a traction signal?
Per ADR-009 (Storefront vs Traction), SaaSalyst classifies traction signals as those requiring real business activity — not something you can fake by configuring a tool. Real lastmod requires actual content updates, which require an active product or content team.
What about sitemap-index format?
Sub-sitemap probing is deferred. SaaSalyst currently warns when the root sitemap is a <sitemapindex> rather than <urlset>, because we don't yet recursively walk the children to evaluate lastmod coverage. We'll address this in a future scanner improvement.
Check Your SaaS Now | Free
SaaSalyst scans your website in 30 seconds and checks for Sitemap lastmod Freshness along with 101+ other business readiness signals.
Scan Your App