There’s a difference between a page that’s old and a page that looks old to a machine. Most operators have heard that AI search rewards fresh content. What almost nobody has fixed is the quieter problem underneath it: AI engines can’t apply a freshness preference to a page if they can’t tell when it was written. And a startling number of pages — including good ones — give the machine nothing to work with.
This isn’t the “refresh your content every two months” advice. That’s about changing the page. This is about signaling the change. You can refresh a page religiously and still lose the citation because the recency signal never makes it into a form an engine can read.
Why an engine needs a date before it can trust you
Freshness is one of the heaviest weights in AI retrieval right now. Roughly 65% of AI bot crawl activity targets content published within the past year, and pages updated within the past two months earn about 28% more citations than older ones. That’s the lever everyone’s chasing.
But here’s the mechanic: that lever only fires when the engine can place your page on a timeline. It establishes a date from three things — the `datePublished` and `dateModified` fields in your Article schema, a visible dateline near the headline, and contextual clues in the body copy (“as of 2024,” “last year’s data”). When all three are missing or contradictory, the engine doesn’t assume your page is fresh. It assumes it’s undateable, and undateable content gets deprioritized for anything time-sensitive — which, in 2026, is most commercial queries.
Worse is the page that’s actively misdated. A huge share of WordPress and CMS-built pages carry a `datePublished` from years ago and have never emitted a `dateModified` at all. You updated the body three times; the schema still says 2021. The engine reads the only date it was given and files you under stale. You did the work and got penalized for it because the signal lied.
The three places your date has to live
A date that exists in only one place is a date the engine might miss. It has to be consistent across all three surfaces, or the contradiction itself becomes a trust problem.
Machine-readable: your Article (or BlogPosting) schema needs both `datePublished` and `dateModified` as valid ISO timestamps. Not one. Both. The gap between them is what tells an engine the page is maintained rather than abandoned.
Visible: a human-readable “Published / Updated” line near the H1. AI engines parse rendered text, and a visible dateline corroborates the schema. Two surfaces agreeing is far stronger than one surface alone.
Contextual: the body copy itself. A page that says “the current state of AI Overviews” with no year reads as timeless; a page that says “as of May 2026” hands the engine a hard anchor and a recency claim in one phrase.
What to do this week
1. Audit your top 20 pages. Open each in a structured-data tester and check whether `dateModified` exists and is recent. You’ll likely find a third of them have no `dateModified` and a stale `datePublished`. That’s your fix list.
2. Add both date fields to your Article schema template, and wire `dateModified` to update automatically whenever the page is edited — not manually, because manual always drifts.
3. Surface a visible “Updated” date near every headline. If your theme hides it, unhide it. The corroboration is worth more than the cleaner design.
4. When you refresh a page, change something real. Engines and Google both detect date-only edits where the content didn’t move, and a bumped `dateModified` with no substantive change can read as manipulation. Update the date because you updated the page, never the reverse.
5. Kill orphan year references. Search your body copy for naked years and either remove them or make them deliberate. “In 2023, marketers…” on an evergreen page is a self-inflicted aging signal.
Paris Roussos has been doing SEO since 1996 (co-founded a Forbes Best of the Web–winning site back in the day) and now runs a white-label AI SEO practice for agencies and brands — flat-rate, $500–$1,500/mo per client. If your top-of-funnel traffic is leaking into ChatGPT and Perplexity and you want it back, email parisroussos@gmail.com.
Freshness isn’t only about doing the work — it’s about making sure the machine can see that you did.