Browse sections
What does this check look at?
A machine-readable date is found in dateModified, datePublished or article:modified_time. Within 12 months is a full pass; older is a partial pass. If only the HTTP Last-Modified header carries a date, that is a partial pass.
The first date found in source order wins: dateModified is checked before datePublished, which is checked before article:modified_time. They are not compared with each other, so a fresh datePublished beside a stale dateModified is read as stale. A date within twelve months is worth the full 3 points, a recent Last-Modified header 2, and an old or unparseable date 1.
How do I fix it?
- Partial pass: Refresh date-sensitive pages and update the date when you do.
- Partial pass: Use ISO 8601 dates (YYYY-MM-DD) in schema and meta tags.
- Partial pass: Also declare dateModified in structured data; headers are not shown to readers.
- Partial pass: Declare dateModified in structured data and keep it current.
- Publish a machine-readable modification date.
Why is it worth 3 points?
Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:
| Dimension | Freshness — 5% of the total score |
| Points for this check | 3 of 5 in this dimension |
| Worth at most | 3.0 of the 100 points |
Low to moderate: a real but secondary signal.
Which dimension does this belong to?
Freshness — 5% of the total score, decided by 2 published rules.
Dated content is deprioritised in generated answers, and an undated page gives an engine nothing to reason about.
None of the five guides covers this rule, which is why this page shows the fix in full rather than pointing at one.
What else is measured in this dimension?
- A current year appears in the content — 2 points
How do I see my own result?
Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.
Run a free GEO audit on your own site →
The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.
Questions about this rule
What does this check look at?
A machine-readable date is found in dateModified, datePublished or article:modified_time. Within 12 months is a full pass; older is a partial pass. If only the HTTP Last-Modified header carries a date, that is a partial pass.
Evidence and sources
GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024
This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.
Primary sources
- Generative Engine Optimization (KDD 2024) — the measured gains the citability weight follows
- What Generative Search Engines Like — what generative engines prefer in retrieved content
- What Gets Cited: Competitive GEO — which of two competing sources is cited first
- The rule set and its weights — every check, its weight and its pass condition