Does your sitemap honestly report when each page was last updated?
Accurate last-modified dates in your sitemap tell AI crawlers which pages are fresh enough to cite.
What this signal tests
We look at the last-modified date attached to each entry in your sitemap and check three things: the date is in a standard format, it reflects when the underlying page actually changed, and it varies sensibly across the site. A sitemap where every page claims to have changed yesterday is a strong signal that the date is fake.
Why it matters for your visibility in AI
AI search systems prioritise recent content when answering time-sensitive questions, and they rely on the last-modified date in your sitemap to decide what is fresh. If every page in your sitemap shares the same date - usually the date the sitemap itself was built - crawlers learn to ignore the field entirely, and your genuinely updated content is treated as stale. This matters most for businesses where recency builds trust: legal advice, medical content, pricing pages, news, and product availability. When AI systems cannot tell which page is current, they cite an older, more confidently dated competitor instead - and your fresh content goes unread.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| >=80% of sampled entries have valid, plausible lastmod. |
How we test it
We sample entries from your sitemap and check each one for a last-modified timestamp in the standard internet date format. Where possible we compare that timestamp against the actual last-modified header your server returns when we fetch the page, and we look at the spread of dates across the sample. If more than ninety percent of pages share the same date, we flag the sitemap as using a generator timestamp rather than real edit times.
Show technical detection method
For sampled <url> entries require valid lastmod; cross-check Last-Modified header; flag if >90% share the same date (generator-timestamp heuristic).
If your site fails: how to fix it
- Configure your sitemap generator to read the last-edited timestamp from your CMS or database for each page, rather than stamping every entry with the current build time.
- Use a standard date format - ideally the full ISO 8601 form like 2026-05-22T14:30:00Z - so that every crawler parses it without ambiguity.
- Audit your sample of pages: pick ten random URLs from the sitemap and confirm the lastmod value matches when each page was actually changed.
- Remove the lastmod field entirely for pages where you cannot produce an accurate date. An absent field is better than a misleading one and will not be penalised.
- Rebuild and republish the sitemap, then re-run the AI Ready Test to confirm the dates now look authentic and varied.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Crawlability |
Primary sources
Related signals
Frequently asked questions
What format should the lastmod date use?
Use the ISO 8601 / W3C Datetime format. The shortest valid form is just the date, like 2026-05-22, but including the time and a timezone offset is preferred for precision. Avoid US-style or European date orders, which cause parsing inconsistencies.
Is it bad to leave lastmod out entirely?
Not at all. Google has stated publicly that an inaccurate lastmod is worse than no lastmod. If you cannot produce a trustworthy value, omit the field - your other recency signals (page content, dates in markup, freshness of internal links) will still be used.
What if I only edit a small part of a page - does that count as modified?
It depends on judgement. A typo fix probably does not warrant updating lastmod; a substantial content update, refreshed pricing, or new statistics do. The goal is for the date to reflect when a user would consider the page meaningfully updated, not micro-edits.
Does updating lastmod automatically get my page re-crawled?
It is a hint, not a command. Crawlers use lastmod alongside their own scheduling priorities. A consistently accurate lastmod history builds crawler trust over time, which gradually leads to faster re-crawling for genuinely updated pages.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.