AI's "Latest 2026" Filter: Date-Stamping Strategy

When a restaurant owner asks Perplexity "how much does a QR menu cost in 2026," the engine doesn't cite a post from 2024 — it cites one updated three weeks ago. That isn't coincidence; it's a measurable filter. On thMenu's blog we took citations from 18 to 142 in a twelve-month window with one change: every post gets a visible date stamp plus schema.org dateModified, refreshed every 90 days.

Why AI Engines Care About Dates

ChatGPT Search, Perplexity and Claude all run on retrieval-augmented generation. When a query contains a year ("2026 trends"), the retrieval layer filters by date freshness before ranking. In our internal tests, pages with a dateModified within the last 6 months were cited 4.2x more often; anything older than 12 months was effectively invisible.

The signal has two parts: (1) a visible date in the rendered HTML, for the human reader, and (2) datePublished + dateModified in schema.org Article markup, for the machine. Disagreement between the two flags a low-trust page. Missing both pushes the post out of the retrieval pool entirely.

A Practical Date-Stamp Schema

The format we run on thMenu: "Updated: October 24, 2026" in small type directly under the H1, plus a hidden JSON-LD block carrying the same date in ISO 8601. We keep datePublished fixed and bump dateModified on every edit, with a separate timezone offset (Z or +00:00) so AI parsers never have to guess.

• Visible stamp: text-sm text-zinc-400 under the title — first signal an AI crawler sees.
• Schema.org Article: separate datePublished and dateModified, ISO 8601 with explicit timezone.
• HTTP Last-Modified header: Cloudflare sets it automatically, but Next.js ISR caching can desync it — verify after each revalidate.

The 90-Day Minor Refresh Discipline

Bumping dateModified after 90 days puts a post back in the "fresh" tier — but AI engines run similarity hashing in parallel. Touching only the date while leaving the body identical is cloaking, and the penalty is severe. The minimum refresh: rewrite 3+ sentences, add one new statistic, update at least one outbound link.

We automated this at thMenu. A cron job flags posts older than 90 days, an editor spends 15-20 minutes on each in the admin panel, and dateModified bumps automatically. Roughly 63% of our 142-citation gain came from the refresh discipline; the remaining 37% from getting schema right at first publish.

FAQ

What happens if I only change dateModified without editing? Citations rise short-term, then in 2-3 months AI engines flag it via similarity comparison and your domain-wide trust drops. Don't.

Which year tag scores highest? Current year plus one month ahead. If you publish in October 2026, dating it December 2026 scores higher than September 2026.

Does thMenu blog handle this automatically? Yes — Pro+ plans auto-inject visible stamps and schema.org dateModified on publish and edit, and the admin panel surfaces a refresh prompt every 90 days.

Found this helpful? Share it.