Does Changing a Page's Date Help It Get Cited by AI?

The date on a page is one of the few things an LLM reads that has nothing to do with whether the page answers the question, and it still moves the ranking. A peer-reviewed experiment presented at SIGIR-AP 2025 gave pairs of equally relevant passages different dates and nothing else. Depending on the model, between 9% and 25% of the model's choices flipped toward the newer date. That result is real. It also explains less than the "refresh your dates" advice built on it suggests.

Key facts

Key takeaways

We have already covered how long it takes to get cited and how old cited content is: median citation ages run from five to eight months depending on the engine, and pages left unrefreshed lose visibility faster. That post concluded that re-dating a page that does not answer the question will not earn a citation.

The question marketing teams actually ask next is narrower and more awkward: if the page does answer the question, does the date by itself make a difference? That is a question about the date as a signal, separate from the content behind it, and observational data cannot answer it. It needs an experiment that holds the content fixed and changes only the date. That experiment now exists.

Hanpei Fang, Sijie Tao, Nuo Chen, Kai-Xin Chang, and Tetsuya Sakai, of Waseda University and the Hong Kong Polytechnic University, took the TREC Deep Learning 2021 and 2022 passage collections, which come with human relevance judgments for 53 and 76 queries. For each query, BM25 retrieved the top 100 passages and an LLM reranked them: the standard retrieve-then-rerank setup in information retrieval research.

They then prefixed each passage with a line reading "Published on YYYY/MM/DD" and reran the reranking. Seven models were tested: GPT-3.5-turbo, GPT-4, GPT-4o, LLaMA3-8B and 70B, and Qwen2.5-7B and 72B. The paper was accepted to SIGIR-AP 2025, and a revised version was posted on 21 September 2026.

Two designs came out of it, and they answer different questions.

The listwise test dated the 100 passages in reverse order of their BM25 rank: rank 100 got 2025, rank 1 got 1926, a year apart each. Newer-dated passages moved up across the board. The average date of the top ten shifted forward by 1.3 years for GPT-4o, 3.2 years for GPT-3.5-turbo, and 3.9 to 4.8 years for LLaMA3-8B, and individual passages jumped by as many as 95 ranks.

The pairwise test is the cleaner one. The researchers took pairs of passages with the same human relevance grade, found which one the model preferred, then gave the preferred passage a 1980 date and the other a 2025 date. The only thing that changed was the date.

All four results were statistically significant. The authors' summary: "Although larger models attenuate the effect, none eliminate it."

The limits matter more than usual here, because this paper is easy to read as permission to bump dates.

The listwise numbers are a stress test. Because the newest dates went to the passages BM25 ranked lowest, the design pits recency directly against first-stage relevance. The large year shifts show how hard a date can pull on a weak passage. They are not an estimate of what re-dating a strong page in a real results set would do. The pairwise reversal rate, measured between equals, is the figure that fits the "my page versus a similar page" scenario.

The gap was 45 years. The pairwise test compared 1980 with 2025. A marketing page competing on "Updated March 2026" against "Updated September 2026" presents a much smaller cue, and the paper does not measure how the effect scales with the size of the gap.

The date was in the text. It appeared as a line inside the passage the model read. Production engines do not document whether a page's structured-data dates, HTTP headers, or byline reach the model that ranks passages, so the result tells you nothing about a dateModified value hidden in markup.

The models are a step behind. None of the seven are the models answering buyers' questions today, and the trend inside the paper points one way: GPT-4o was swayed less than GPT-3.5-turbo, and each 70B-class model less than its smaller sibling.

Reranking is one stage. A passage has to be retrieved before an LLM can rerank it. A new date on a page that is never retrieved for a prompt changes nothing.

Two large observational datasets measure the outcome the experiment cannot: what AI engines actually cite.

Ahrefs' July 2025 study, by Ryan Law, pulled about 17 million cited URLs from ChatGPT, Perplexity, Gemini, Copilot, and Google's AI Overviews alongside organic results. AI-cited content averaged 1,064 days since publication against 1,432 days for organic results, about 25.7% fresher; on last-update date the gap narrowed to roughly 13%. The same study cautioned against updating publish dates without changing the content.

Discovered Labs analyzed 2 million citation observations over six months and modeled which page features accompany citation. Page age carried a coefficient of +0.05. Prompt-content alignment carried +0.37, which the report describes as roughly three times the next-strongest page-level signal.

These look like they disagree. One says AI engines lean clearly toward newer content; the other says age barely matters. The experiment reconciles them. If the date works as a tiebreaker between passages that are otherwise close, it will show up as a consistent average tilt toward fresher content across millions of citations, and as a small coefficient next to relevance in a model that controls for relevance. Both findings describe the same mechanism from different distances.

There is a second point neither observational study raises. Both measure the dates pages display. A page whose date was bumped last month without any edit counts as fresh content in these datasets. So the observed freshness premium is not purely evidence that updated content is better; part of it may be the date bias itself, measured in the wild. That is exactly why these studies cannot settle whether a date bump works, and why the controlled result matters.

Google is the one party with a documented rule. Its helpful content guidance lists, among search-engine-first practices to avoid: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Its byline date documentation says dates "must describe the publication or update date of the page." And Google's guidance on AI features says AI Overviews and AI Mode are rooted in its core ranking and quality systems.

So the evidence splits by surface. On engines that lean on LLM reranking, a newer date is a demonstrated but shrinking tiebreaker. On Google's surfaces, a bumped date without an edit is named as the wrong behavior.

The reconciliation turns into four rules.

There is also a strategic reason to avoid building on the date trick. It is the kind of signal that stops paying as more pages exploit it: if everyone's page says "updated this month," the date stops distinguishing anyone, and the bias itself is now a published, measured weakness that model builders have a reason to reduce.

"AI prefers fresh content" is true and incomplete. The controlled evidence says the date itself is part of what engines respond to, which makes an accurate, visible, recent date worth having. The observational evidence says it is a small part, far behind answering the question. And the one engine owner that has written a rule says the date has to mean something.

The practical upshot is to stop thinking of the date as something you set and start thinking of it as something you earn: it moves when the page does.

Elmo is an open-source, self-hosted AI visibility platform that runs your prompt sets across ChatGPT, Claude, Gemini, Perplexity, and Google's AI surfaces on a schedule and stores every answer with its citations. Because each cited URL and each run date are in your own database, checking which of your cited pages carry stale dates, or comparing citation rates in the four weeks after a substantive update, is a query over your own history.

For the timing of citations, start with how long it takes to get cited by AI and citation volatility. For how dates and authorship are expressed in markup, see structured data for AI search. For the fundamentals, see AI citations, the AEO guide, and the AI search glossary.