Docs AI readiness
Content shows when it was updated
Looks for update dates in your sitemap and homepage, and passes when the newest one is less than a year old.
What it checks
We collect dates from three places: the <lastmod> entries in your sitemap (including the first child sitemap when the sitemap is an index), the og:updated_time meta tag, and the first dateModified value in the homepage HTML. We use the newest.
- PassThe newest date is within the last 365 days.
- WarningThe newest date is over a year old, or no dates were found. This check never fails.
Why it matters
Crawlers and AI tools use dates to judge how current information is. Without any dates, they cannot tell a page updated last week from one untouched for years.
How to fix it
Give every sitemap entry an accurate last modified date, and add dateModified to the structured data of pages that change. Update them only when the content really changes: Google says it uses lastmod when it is consistently accurate, so dates that change on every build teach it to ignore them.
Platform notes
Most CMS and SEO plugin sitemaps add last modified dates for you. Open your sitemap to check they are there and look right.
Set lastModified for each entry in sitemap.ts from the content's real update date, not the build time.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.