Content Freshness
Quick facts
- The two parts of freshness
- Recency measures a page's age and can be stated by the publisher. Currency describes whether its claims remain true and cannot be established by the publisher alone. Freshness failures arise when recency changes but currency does not.
- Where freshness matters
- Freshness matters at two points. Retrieval determines whether the updated page is indexed, while grounding and reranking determine which candidate passage is selected.
- What the finding means
- AI-cited URLs average about 1,064 days old (roughly 2.9 years), compared with about 1,432 days for organic top-10 results. That difference is the widely quoted '25.7% fresher.' Fresher is relative; it does not mean new.
- What recency can do
- Recency has its strongest effect as a tiebreaker between passages of equal relevance. It cannot rescue a page that falls short on relevance, trust, or extractability.
- Why date-bumping fails
- Google says it uses sitemap lastmod only when the value is 'consistently and verifiably accurate.' Stated dates are checked against observed changes, so advancing a date without changing the content creates a trust failure rather than a cost-free benefit.
1. What content freshness is
Content freshness describes whether a page’s age and update history help or hurt its chances of being retrieved and used to ground an answer.
Freshness combines two properties that behave very differently:
- Recency concerns the timestamp. It measures how long it has been since the page was published or last changed. This is a machine-readable fact.
- Currency concerns the substance. It describes whether the page’s claims remain true. This is a semantic fact that no timestamp can establish.
The distinction matters because each anti-pattern in §7 attempts to improve recency without improving currency. The practices in §6 correct the substance first and then update the date to reflect that work.
Freshness can affect two stages in the answer loop. At retrieval, the updated version must first be present in the index, which depends on recrawling. At grounding and reranking, the engine chooses among candidate passages. A genuinely updated page may appear unchanged to an engine if the new version has not been fetched. Within GEO, freshness is one signal rather than a complete strategy.
2. Recency versus currency: What each can prove
| Property | What it is | How a machine reads it | What it cannot prove |
|---|---|---|---|
| Recency | Age since publication or last modification | dateModified, visible byline date, sitemap lastmod, observed content diff on recrawl | That any claim on the page is still accurate |
| Currency | Whether the live claims are still true | No direct signal exists; engines infer it from corroboration by other sources and the size of observed changes | Nothing the publisher can assert directly |
The relationship is asymmetric: a publisher can assert recency but not currency. A publisher can set dateModified to any value, but cannot simply declare that every claim remains true.
Engines therefore treat stated dates as claims that need corroboration, not as facts in their own right. The practices in §7 can damage trust rather than merely fail to help. In E-E-A-T §4.4, Trustworthiness includes the “accuracy, transparency, currency” grouping. This is separate from citability, which concerns whether a passage can be extracted. A current page must still be extractable, and an extractable page must still be accurate.
3. What the evidence shows and what it does not
Evidence that AI systems prefer recent content comes in two forms. One body of work is observational, while the other is counterfactual. Each supports a different conclusion.
3.1 Correlational evidence: AI systems cite fresher content, but “fresher” does not mean new
The largest public dataset comes from an Ahrefs analysis of 16.975 million cited URLs across ChatGPT, Perplexity, Gemini, Copilot, AI Overviews, and organic Google results (Law & Guan, July 2025). It found that AI-cited URLs were 25.7% “fresher” than organic results.
The 25.7% difference compares an average age of about 1,064 days for cited URLs with about 1,432 days for organic results. In other words, the average AI-cited page is roughly 2.9 years old.
Here, fresher describes a comparison with an old baseline; it does not mean new. The aggregate results contradict the idea that publishers must post every week to retain citations. Across engines, the pattern was consistent: ChatGPT favored the newest content among the major assistants, while Google AI Overviews behaved much more like organic search than the other AI surfaces.
This evidence is observational. Fresher pages may receive more citations because of their age, or because newer pages also tend to be better structured, better linked, and more closely aligned with current questions. Correlation cannot separate those possibilities. The counterfactual experiment in §3.2 isolates the effect of the stated date.
3.2 Causal evidence: Recency bias appears in the model, not just the corpus
Fang, Tao, Chen, Chang, and Sakai (2025) provide counterfactual evidence that isolates recency more directly than observational data can.
The authors prepend artificial publication dates to passages from the TREC Deep Learning collections (DL21 and DL22), then repeat the LLM reranking process. The passage text remains unchanged; only the stated date moves. Any resulting change in ranking therefore comes from the date.
| Measurement | Result | Why it matters here |
|---|---|---|
| Top-10 mean publication year after date injection | Shifted forward by up to 4.78 years | A date signal alone changes the reranker’s result set |
| Movement of individual items | Up to 95 ranks | The effect is large, not marginal |
| Pairwise preference between passages of identical relevance | Reversed up to 25% on average | Recency acts as a tiebreaker where relevance is equal |
| Model coverage | 7 models: GPT-3.5-turbo, GPT-4, GPT-4o, LLaMA-3 8B/70B, and Qwen-2.5 7B/72B | The finding is not limited to small models |
| Effect of model scale | Larger models attenuate but do not eliminate it | Frontier models still show the bias |
The result has a troubling implication: the bias responds to the stated date, not to an observed change in the content. That makes the stated date open to manipulation. §7 explains the drawbacks of exploiting it.
3.3 How to interpret the evidence
| What the evidence supports | Important limit |
|---|---|
| Engines do favor recent content, and the preference is causal rather than merely correlational | The measured effect occurs in reranking. The study used lab rerankers over TREC collections, not production pipelines with their own freshness handling. |
| Recency acts most strongly as a tiebreaker at equal relevance | It does not rescue a page that falls short on relevance, trust, or extractability |
| Aggregate ages of cited pages run to about 2.9 years | Absolute thresholds in vendor content, such as “under 30 days” or “under 13 weeks,” reflect the query mix rather than a general rule. See §4. |
Vendor marketing on this topic often repeats figures from other vendors without adding evidence. Reliable conclusions depend on three types of sources: original-data studies, peer-reviewed or preprint research, and first-party engine documentation. Other sources can indicate a pattern, but they cannot support precise conclusions.
Related evidence also limits how much recency can accomplish. When a model chooses between conflicting sources, topical relevance dominates, while stylistic credibility markers have little effect (Wan et al., ACL 2024). Freshness can influence that choice, but it cannot replace topical fit.
4. Freshness depends on the query
The average cited page in §3.1 is about 2.9 years old, yet vendor studies report that half of AI citations are less than 13 weeks old. Both findings can be accurate because the value of freshness depends on the query, and the two samples included different types of queries.
This mechanism comes from classical search and remains part of generative retrieval. Recency receives more weight when the answer is likely to have changed since publication. Google’s ranking-systems guide calls these Freshness systems and describes “various ‘query deserves freshness’ systems designed to show fresher content for queries where it would be expected” (A Guide to Google Search Ranking Systems). The phrase where it would be expected makes the condition explicit. The system does not apply a blanket preference for new pages.
| Query class | Example | Freshness weight | Practical review cadence |
|---|---|---|---|
| Volatile / breaking | ”What happened with X today”, live pricing, outage status | Decisive. Stale content is wrong, not merely down-ranked. | Monitor continuously or review after relevant events |
| Fast-moving technical | ”Best model for X”, API and version questions, tool comparisons | High | Review at least quarterly |
| Periodic / seasonal | ”Best X in 2026”, annual rankings | High near the annual or seasonal boundary; low between | Review annually at the relevant boundary |
| Slow-changing practical guidance | How-to guides, methodology | Moderate | Review every six months |
| Definitional / conceptual | ”What is X”, terminology | Low. A correct definition does not expire. | Review only when facts change |
The review cadence should match how quickly the facts can change. Rewriting a definitional page every month offers almost no benefit and creates the risks described in §7. Leaving a pricing page untouched for a year, however, compromises its currency no matter how well the page is structured.
Freshness also varies across engines and search experiences:
| Engine | Observed preference for recent content | What it implies |
|---|---|---|
| ChatGPT search | Strongest observed preference among the major assistants | The preference for recent content is strongest here |
| Perplexity | Live retrieval with a strong preference for recent content | Rapid refetching allows genuine updates to be recognized quickly |
| Google Gemini | Favors fresher content, between the two extremes | The preference falls in the middle of the range |
| Google AI Overviews | Weakest preference; behaves much like organic search | Freshness provides the least differentiation here |
These findings show broad tendencies. The day counts for individual platforms come from one vendor study that does not disclose its query mix, so they should not be treated as fixed benchmarks. Citability §5 applies the same caution to GEO benchmark figures.
5. What actually signals freshness to an engine
Engines assess freshness through five channels. Publishers fully control only three of them.
| Channel | What it is | How much control the publisher has |
|---|---|---|
| Structured dates | datePublished and dateModified in JSON-LD; see JSON-LD and Schema.org for AI for the markup | Supplied entirely by the publisher |
| Visible on-page date | The human-readable byline Google asks you to label “Published” or “Last updated” | Supplied entirely by the publisher |
Sitemap lastmod | The change-announcement protocol described in Sitemap and IndexNow | Supplied by the publisher, then verified by the engine |
| Observed change on recrawl | The engine’s own diff between two fetches, according to whatever schedule its crawler follows | No direct control |
| Corroboration | Whether other sources reflect the same updated facts, using the trust framework described in E-E-A-T | No direct control |
The two channels outside the publisher’s control determine whether engines believe the other three.
Google documents this verification process. It says the sitemap lastmod value is used “if it’s consistently and verifiably (for example by comparing to the last modification of the page) accurate.” A significant update changes the main content, structured data, or links; a copyright-date change does not qualify (Build and Submit a Sitemap). Google also advises publishers to label a prominent visible date, mark it up with datePublished or dateModified, keep the visible and structured values consistent, and avoid future dates or the date of the event being described (Add a Byline Date).
Google’s AI-features documentation does not describe freshness as an eligibility requirement. It says that “there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary,” and that no special schema.org markup is needed (AI features and your website; Optimizing for generative AI features). Date markup helps an engine distinguish among several dates on a page; it does not create freshness by itself.
6. When to review and update content
6.1 The five decay triggers
A page needs revision when one of these triggers occurs, not simply because a calendar interval has elapsed.
| Trigger | How you detect it | What to change |
|---|---|---|
| Fact drift | Verify the page’s checkable claims at regular intervals | Update the claim and the stated date |
| Surface change | Monitor visibility to detect changes in how an engine answers this query class | Update the section that directly answers the query, following Writing for AI Citation |
| Competitive displacement | Track citations for target queries | Improve depth and specificity where a competitor outperforms your page |
| Dependency shift | Monitor releases for named dependencies | Update only the affected section |
| Stat expiry | Maintain an inventory of dated claims and source years | Update the statistic and its citation |
You cannot detect the second and third triggers by reading your own page. They require the measurement methods described in GEO Metrics.
6.2 What counts as an update
| Tier | Example | What it justifies |
|---|---|---|
| Cosmetic | Typo, formatting, date-only change | Nothing. Do not advance dateModified. |
| Substantive | A claim changed, a section rewritten, new data added | Advance dateModified, update lastmod, and notify engines again |
| Structural | The page’s argument or scope changed materially | Advance dateModified and reconsider whether it is still the same page |
6.3 How to set the review cadence
Use the table in §4 to set a review interval by query class, then revise only when one of the triggers in §6.1 occurs.
The interval prompts a review; it does not require an edit. When a quarterly review is treated as a quarterly update, a page with no factual drift may receive only a new date. A review that finds nothing has changed is still successful and should end without an edit.
GEO Wiki uses an internal nextReviewDue field to schedule the next review. Most reviews leave lastUpdated unchanged.
7. Date-bumping and other freshness anti-patterns
The experiment in §3.2 showed that injected dates can move rerankers. Injected dates can therefore manipulate reranking results, but the resulting costs make the practice inadvisable.
| Anti-pattern | Why it looks like freshness | Why it actually fails |
|---|---|---|
| Cosmetic date bump | dateModified advances with no content change | Stated dates are checked against observed changes, so moving the date without changing the content damages trust rather than having no effect |
| Rolling-year title churn | ”Best X in 2026” retitled annually over a stale body | The title claims currency while the body contradicts it, and §2 shows why publishers cannot establish currency by assertion |
| Republish under a new URL | A new page for old content resets the clock | Discards accumulated link and citation equity and creates a near-duplicate that competes with the original |
| AI-regenerated “refresh” | Paraphrasing produces repeated superficial changes on recrawl | It creates observed changes without improving currency; the pattern is detectable, as explained in AI Content Detection |
| Cadence churn on definitional pages | Monthly updates make evergreen content look active | Freshness carries almost no weight for that query class, so the work has a real cost while the freshness benefit is minimal |
Google itself identifies the first practice as an example of search-engine-first content. Its self-assessment guidance asks publishers: “Are you changing the date of pages to make them seem fresh when the content has not substantially changed?” (Creating Helpful, Reliable, People-First Content).
A page should become more recent because its claims were brought up to date. Changing the date alone reverses that relationship.
Date-bumping can produce an effect; it demonstrably moved lab rerankers. The problem is that any gain is small and temporary, while the loss of trust is neither small nor temporary. The Fang et al. result describes a bias that engines have an incentive to mitigate, not a lasting advantage. Deliberate manipulation of date signals is also a recognized spam pattern; see GEO Spam and Manipulation. The benefit to one publisher also erodes once competitors optimize the same factor (C-SEO Bench, Puerto et al., NeurIPS ‘25 D&B).
8. Why freshness matters for GEO and what to do
Among the signals used for grounding, freshness is inexpensive to fake but costly to maintain. That cost is what gives genuine currency its value. Freshness is also the only major signal that degrades passively. Citability and E-E-A-T decay slowly, if at all; a page’s currency can deteriorate when an external fact changes.
| Goal | Relevant resource |
|---|---|
| Find which of your pages have decayed | GEO Audit |
| Rewrite a page that has drifted | Writing for AI Citation |
| Check whether your source is trusted at all | E-E-A-T |
| Make sure the updated page is easy to extract | Citability |
| Announce the change to engines | Sitemap and IndexNow |
| Understand how freshness fits into GEO | Generative Engine Optimization |
References
Academic:
- Fang, H., Tao, S., Chen, N., Chang, K.-X. & Sakai, T. (2025). Do Large Language Models Favor Recent Content? A Study on Recency Bias in LLM-Based Reranking. SIGIR-AP ‘25. arXiv:2509.11353 · ACM DL · paper summary
- Wan, A., Wallace, E. & Klein, D. (2024). What Evidence Do Language Models Find Convincing? ACL 2024 Main. arXiv:2402.11782 · paper summary
- Puerto, H., Gubri, M., Green, C., Oh, S. J. & Yun, S. (2025). C-SEO Bench: Does Conversational SEO Work? NeurIPS ‘25 Datasets & Benchmarks. arXiv:2506.11097
Original-data studies:
- Law, R. & Guan, X. (2025). New Study: AI Assistants Prefer to Cite ‘Fresher’ Content (17 Million Citations Analyzed). Ahrefs
Official platform documentation (as of 2026-07):
- Google Search Central: Add a Byline Date to Google Search Results · Help Google Search know the best date for your web page
- Google Search Central: Build and Submit a Sitemap
- Google Search Central: AI features and your website · Optimizing your website for generative AI features on Google Search
- Google Search Central: A Guide to Google Search Ranking Systems (the “Freshness systems” entry) · Creating Helpful, Reliable, People-First Content
Frequently asked questions
How often should I update my content for AI search?
Does changing the date on a page count as updating it?
Do evergreen pages need to be refreshed?
I updated my page and it still isn't being cited. Why?
Do I need datePublished and dateModified schema markup for AI search?
See also
Sources
Primary
- New Study: AI Assistants Prefer to Cite 'Fresher' Content (17 Million Citations Analyzed) · Ahrefs · 2025-07-28
- Do Large Language Models Favor Recent Content? A Study on Recency Bias in LLM-Based Reranking (Fang et al., SIGIR-AP '25) · arXiv / SIGIR-AP 2025 · 2025-09-14
- Do Large Language Models Favor Recent Content? (SIGIR-AP '25 Proceedings) · ACM SIGIR-AP · 2025-12-07
- Add a Byline Date to Google Search Results · Google Search Central · 2025-03-12
- Build and Submit a Sitemap · Google Search Central · 2025-11-04
- AI features and your website · Google Search Central · 2025-12-10
- Optimizing your website for generative AI features on Google Search · Google Search Central · 2026-07-10
- A Guide to Google Search Ranking Systems · Google Search Central · 2025-12-10
- Creating Helpful, Reliable, People-First Content · Google Search Central · 2025-12-10
- Help Google Search know the best date for your web page · Google Search Central Blog · 2019-03-01
Secondary
- What Evidence Do Language Models Find Convincing? (Wan et al., ACL '24) · arXiv / ACL 2024 Main
- C-SEO Bench: Does Conversational SEO Work? (Puerto et al., NeurIPS '25 D&B) · arXiv / NeurIPS '25 D&B