What this check tests
A crawled page (the homepage plus up to nine more) counts as having a freshness signal if any one of these is present:
- A parsed JSON-LD block whose top-level object has a
datePublishedordateModifiedmember with a truthy value. A block that is an array, or an object nested inside@graph, is not read. - A
<meta property="article:published_time">or<meta property="article:modified_time">tag. The content is not looked at. - Any
<time>element with adatetimeattribute, anywhere on the page.
The score is the share of counted pages, rounded: 50 or more is a pass, 1 to 49 partial, 0 a fail. The message reads "4/10 pages have date/freshness signals".
The check only detects that a date field exists. It does not parse the value, compare it with today, check that it matches the date shown to visitors, or tell a publication date from other dates: a <time datetime> on an event listing, a comment or an opening-hours block counts the same. It also applies to every page type, so a homepage, pricing page or contact page with no meaningful date lowers the score.
Why it matters to agents
Google's guidance is the best-documented source. It recommends a user-visible date labelled "Published" or "Last updated", and structured data with datePublished and dateModified on an Article, BlogPosting or similar type. It asks that dates match between the visible text and the markup, be accurate, and not be in the future. It also says it does not guarantee that a byline date, whether visible or in structured data, will be shown in search results.
On AI features, Google's guide says its generative systems use retrieval from the search index to improve the quality, accuracy and freshness of responses. It does not say that date markup is a ranking input, and no fetched source says an assistant prefers pages with date fields. So the practical value is for readers who need to judge whether a page is current, and for machines that read the dates to do the same.
A date that is wrong is worse than none. If a page's dateModified changes while the content does not, it misleads exactly the readers the field is for.
How to fix it
For pages that are articles, guides, release notes or documentation with a history:
- Show a date on the page, labelled "Published" or "Last updated", in a
<time>element:
<p>Last updated <time datetime="2026-10-12">12 October 2026</time></p>
- Add the same dates in JSON-LD as a top-level object, using the form Google shows:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to rotate API keys",
"datePublished": "2026-03-04T08:00:00+00:00",
"dateModified": "2026-10-12T09:30:00+00:00"
}
</script>
- Update
dateModifiedonly when the content changes in a way a reader would care about. - Include a time and time zone if you can; Google's guidance says the date is required and the time is optional.
- For pages with no editorial date, such as a homepage or a contact page, a lower score is normal.
Check the block with schema.org validity, and see schema.org completeness for the other fields an article should carry. Author attribution covers the byline that normally sits next to the date.