Freshness signals

What are freshness signals?

Freshness signals are the metadata and on-page inputs engines combine to decide how recent a piece of content is. The primary signals:

• datePublished: when the page was first published (ISO date in Article schema)¹.
• dateModified: when the page was last meaningfully updated.
• On-page recency markers: "Last updated" labels, year references in headings, version numbers.
• Crawl-history signals: how often engines have observed the page changing.
• External recency signals: when other authoritative pages have linked to or cited this page recently.

Engines may use these signals, directly or indirectly, when evaluating recency-sensitive content. There is no single public "freshness score" formula from any major engine; the precise weighting and combination logic is not vendor-documented.

Status in 2026

Increasingly relevant for time-sensitive queries, with meaningful per-engine variation. Ryan Law and Xibeijia Guan's July 2025 Ahrefs analysis of 16.975 million citations across ChatGPT, Perplexity, Gemini, Copilot, AI Overview, and Google's organic SERPs found AI-cited URLs are on average 25.7% fresher than organic-cited URLs ((1432 − 1064) / 1432 = 25.7%; AI assistants average 1064 days / 2.9 years since publication vs. Google organic's 1432 days / 3.9 years)².

But the headline number hides important per-engine variation, including one notable exception:

AI Overview behaves closer to classical Google search than to the other AI engines on this dimension, which makes sense since it inherits the same ranking systems. The practical implication: if a site primarily targets AI Overview citation, aggressive content-update cadence has lower marginal return than it does for Perplexity or ChatGPT optimization.

Two caveats Ahrefs flags in the original study:

• Even AI engines mostly cite long-lived content: the 2.9-year average across all AI assistants means "fresher" is relative, not "must update weekly." Most AI citations still go to multi-year-old content.
• "Fresh" combines two metrics: Ahrefs measured both time since publication and time since last update; the study does not isolate which signal dominates.

Practitioners observe a 2024–2026 trend toward engines being more sensitive to date spoofing (bumping dateModified without substantive content change). The mechanism is plausible (re-embedding cycles in retrieval indices naturally surface real content change vs mere date bumps; whether engines explicitly score against this is not vendor-documented) but no engine has published a specific date-spoofing penalty policy.

How to apply

Freshness is signal-quality, not signal-quantity. Three concrete moves:

• Update content when it actually changes: every legitimate revision bumps dateModified. Calendar-driven "freshness updates" that do not change substance are detectable by content-diff inspection (for crawl-based systems) or by re-embedding/index-rebuild cycles surfacing identical content (for retrieval-based AI engines), though the specific mechanism each engine uses is not vendor-documented.
• Match on-page freshness markers to schema dates: if you ship <time datetime="2026-05-14">Last updated May 14, 2026</time> on the page, the schema's dateModified should match. Mismatches can create ambiguity for crawlers and users about which date is authoritative.
• Track freshness decay per content type: definitions, foundational concepts, and history can hold for years without revisiting; vendor comparisons, pricing, and product mentions tend to need updates roughly every 3–6 months (practitioner heuristic; no engine has published required cadence). Tag each page with its expected revision cadence and audit on schedule.
• Calibrate to engine mix: if you primarily target AI Overview, freshness has lower marginal return (AI Overview cites slightly older content than organic per the Ahrefs July 2025 data). If you target Perplexity, ChatGPT, Copilot, or Gemini, freshness updates are higher leverage.

What to skip: bulk date-bumps on unchanged content. Search systems may discount or ignore freshness signals when the visible update date does not match substantive content changes; the result is typically loss of freshness credit rather than a documented penalty, though practitioners report excessive date-bumping correlates with reduced citation over time.

How it relates to other concepts

• Direct input to authority signals within this glossary's four-layer authority model (the four-layer framing is editorial to this glossary; it is not a published industry-standard taxonomy).
• Component of E-E-A-T in the practitioner reading: practitioners commonly interpret freshness misrepresentation (date-bumping) as a Trustworthiness signal, though Google's E-E-A-T documentation does not explicitly cover freshness.
• Exposed via Article schema datePublished and dateModified properties.
• Relevant input for RAG retrieval, especially in production systems with recency-filtered indices for time-sensitive query classes.