Content Freshness

How Google's Query Deserves Freshness (QDF) algorithm works, what triggers freshness-sensitive rankings, how to signal recency through dates and updates, and how AI search engines weight fresh vs. authoritative content.

First published: Jul 2, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #9 in How Search Works#26 in AI Search#330 on the site

Content freshness is conditional, not universal. Google's Query Deserves Freshness (QDF) systems only weight recency higher for query types that benefit from it — breaking news, recurring events, trending topics — while evergreen queries barely move on freshness at all. Changing a date without a substantive content change is, in Google's own words, 'just noise & useless.' The signal that matters is real revision: updated facts, new sections, current data — reflected consistently across your displayed date, dateModified, and sitemap lastmod. AI search inherits freshness from the same ranked index via RAG/grounding, then each platform applies its own recency preference — so ChatGPT and Perplexity skew newer while Google's AI Overviews actually skew slightly older. Refresh by decline signals in GSC and stale facts, not by a blind calendar.

TL;DR — Freshness is conditional. Google’s freshness-related systems (QDF) only up-weight recency for query types that benefit — breaking news, recurring events, trending topics — not evergreen queries. A date change with no substantive update is, per Mueller, “just noise & useless,” and Google’s helpful-content docs flag cosmetic date-stamping as search-engine-first content. The real signal is genuine revision, reflected consistently across your displayed date, dateModified, and sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. lastmod. AI searchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity. inherits freshness from the same ranked indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. via RAGRAG is the retrieve-then-generate pattern behind AI search: the system retrieves relevant passages from an external index at query time, injects them into the model's context, and generates an answer grounded in those sources — without changing the model's weights./groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it., then each platform applies its own recency preference — ChatGPT/Perplexity skew newer, Google’s AI Overviews skew slightly older. Refresh by decline and staleness, not by calendar.

Freshness is conditional, not universal

Freshness is query-dependent within Google’s public ranking-systems description. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: Google: Ranking systems guide Updating a date without a substantial content change is not a documented ranking shortcut. Evidence for this claim Official or primary documentation supporting the adjacent article claim, with scope limited to the source's published description. Scope: No ranking guarantee or undisclosed system mechanics are inferred beyond the cited source. Confidence: high · Verified: Google: Publication dates

The single most important thing to get right: freshness is not an evergreen ranking lever. Google’s freshness-related systems — the mechanism behind Query Deserves Freshness (QDF) — only kick in for query types that actually benefit from recent results. Google’s ranking-systems documentation groups these under systems that surface fresher content for things like recent or breaking events, regularly recurring events (annual events, earnings reports), and frequently updated topics (product releases, trending subjects).

QDF itself is a real, named concept — it was first surfaced publicly through Amit Singhal in a 2007 New York Times interview — and Search Engine Land maintains a standing explainer on how it works. But do not generalize it to “all queries favor freshness.” For a definition, a historical fact, or a stable how-to, freshness carries little to no ranking weight; relevance, quality, and authority dominate instead. Search Engine Journal frames freshness the same way in its ranking-factors analysis: it’s a confirmed factor only when queries demand it, and simply changing publication dates won’t improve rankings.

What actually signals freshness — and what doesn’t

Substantive updates vs. cosmetic date changes

Google is explicit that faking freshness is treated adversarially, not ignored. In its “Creating Helpful, Reliable, People-First Content” guidance, the self-assessment questions used to flag search-engine-first content include: “Are you changing the date of pages to make them seem fresh when the content has not substantially changed?” and “Are you adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem ‘fresh?’ (No, it won’t)” Both are listed as signs of the content Google’s systems are designed to devalue.

John Mueller has said the same thing directly about date changes: when you write something new or significantly change something existing, change the date — but changing the date without doing anything else is “just noise & useless.” He’s also called out obviously fake current-year titling — the “best X for [year]” posts that just get their year bumped — as an embarrassing spam pattern.

So the rule is simple: the date should move only when the substance moves.

dateModified and structured data

Schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.’s dateModified is the structured-data hook for signaling a real update. It follows the same rule as everything else here — it should move when the content substantively changes, not on every typo fix or template redeploy. A dateModified that lurches forward while the body sits untouched is exactly the cosmetic-freshness pattern Google’s docs warn about.

What the 2024 API leak suggested (industry analysis, not confirmed)

In May 2024, a large set of internal Google Content Warehouse API documentation leaked and was analyzed publicly by Mike King (iPullRank) and others. The leaked material describes multiple separate date-related attributes — commonly referred to as bylineDate, syntacticDate, and semanticDate — plus a “FreshnessTwiddler.” This is industry analysis of a leaked internal document, not an official Google confirmation, and should be treated as such. The practical, defensible takeaway independent analysts draw from it is worth acting on regardless: keep your date signals consistent — the displayed date, the structured-data dateModified, any date in the URL, and the date implied by the content itself should all agree. A “Last updated” badge that nothing else on the page supports doesn’t carry weight on its own.

Bing and content freshness

Bing has publicly documented freshness as one of a small set of named ranking factors, alongside relevance, quality and credibility, user engagement, location, and page load time — reported by Search Engine Land. Bing’s own framing mirrors Google’s query-dependent nuance: in many cases content produced today is still relevant years from now, and in some cases it goes out of date quickly.

On the mechanical side, Bing has been explicit that accurate dates in your XML sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. matter. From its July 2025 post on sitemaps in AI-powered search: “The lastmod field in your sitemap remains a key signal, helping Bing prioritize URLs for recrawling and reindexing,” and — crucially — “The value should reflect the true last modification time of the page content, not the sitemap file itself.” Bing also states there that “For AI powered search engines like Bing, freshness signals directly influence how quickly updates are reflected in search results.” Same theme as everywhere else on this page: the signal only means something if it’s honest. (This connects to how re-crawl scheduling works — see crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial..)

How RAG and grounding use freshness

AI searchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity. doesn’t invent a separate freshness model — it inherits one. Google’s own guide to optimizing for generative AI features describes groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it. as a technique used to improve the quality, accuracy, and freshness of AI responses by relying on Google’s core Search ranking systems to retrieve relevant, up-to-date web pages from the Search index. In other words: AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. and AI Mode pull from the same ranked index where freshness is already conditional and QDF-gated, and then the LLM layer decides what to surface and cite on top of that. (For the retrieval mechanism itself, see RAG and grounding.)

What the data shows by platform

The important corrective for readers is that AI is not a monolith on freshness. Ahrefs’ 2025 study analyzing 17 million citations across AI assistants found that assistants generally skew toward citing fresher content — but not uniformly. ChatGPT, Perplexity, Gemini, and Copilot clearly lean newer, while Google’s own AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. actually cite content that skews slightly older than regular organic results. So “AI loves fresh content” is platform-dependent, not a universal law. Ahrefs’ companion piece, Fresh Content: Why Publish Dates Make or Break Rankings and AI Visibility, walks through the practical implications.

How to actually keep content fresh — a framework, not a calendar

Most competing advice reduces freshness to a cadence: “refresh every 60–90 days,” “update quarterly.” That’s the wrong unit. My angle, shaped by the content-audit work I’ve done, is: refresh by signal, not by calendar.

Signals that a page actually needs a refresh

  • Declining GSC performance — impressions and clicks trending down over months is your clearest “this is decaying” flag. Treat a decline as a prompt to investigate, not proof on its own that stale content caused it — an algorithm update, seasonality, or a new competitor can drop the same numbers without a single fact on the page going out of date. Check for actual staleness before you spend the rewrite.
  • Stale facts — outdated pricing, statistics, screenshots, deprecated tools or APIs. If the information is wrong, that’s a refresh, full stop.
  • SERP / competitor movement — new SERP featuresSERP features are any element on a search results page beyond the classic ten blue links — featured snippets, People Also Ask, knowledge panels, sitelinks, image and video packs, AI Overviews, and structured-data-driven rich results. Google documents that losing rich-result eligibility doesn't affect ranking; their SEO relevance is CTR (they redistribute clicks). Some are unlocked by markup; most are purely algorithmic., or competitors visibly updating and overtaking you.
  • How much it costs to get wrong, and how much the fix costs — a page with real reader or business risk in being outdated (pricing, legal/compliance guidance, security advice) deserves a faster refresh cycle than a low-stakes evergreen explainer, and a cheap fact-check-and-patch job is worth doing more often than a rewrite that needs new research.

This is the same prioritization logic behind the content-audit process I’ve reviewed and walked through publicly — compare a page’s trend history (is it doing 10 orders a month now versus 100 before?), weigh how volatile the query and how risky the content is, and act on that combination, not on the date on the calendar.

What “substantive” means in practice

New sections, updated data, filled content gaps, revised recommendations — real changes to what the page says and does. Not typo fixes, not a template tweak, not a find-and-replace on the year. If the change wouldn’t be worth telling a reader about, it’s not worth moving your date for.

Keep your date signals consistent

When you do make a substantive update, reflect it everywhere and honestly: the displayed “last updated” date, the structured-data dateModified, and the sitemap lastmod. Consistency is the point — mismatched dates are the cosmetic-freshness pattern in a different costume.

Common myths

  • “Changing the date bumps rankings.” No — a date change with no substantive update is “just noise & useless,” and Google’s helpful-content docs flag it as search-engine-first behavior.
  • “All queries favor fresh content.” No — QDF-type systems are conditional on query type; evergreen and definitional queries see little to no freshness weight.
  • “Publishing more often makes my site look fresh to Google.” Freshness is about the recency and currency of content, not the cadence of publishing.
  • “AI search always prefers newer content.” Not uniformly — Google’s AI Overviews cite slightly older content on average than organic, even though ChatGPT, Perplexity, Gemini, and Copilot skew newer.

Freshness connects to how re-crawl scheduling works (crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial.), how AI systems retrieve and cite (RAG, grounding, AI Overviews), and the broader mechanics of how search worksSearch works in three stages — crawling, indexing, and serving (ranking). A page has to clear each one to appear in results: getting crawled doesn't mean you're indexed, and getting indexed doesn't mean you rank.. It’s a signal, not a strategy in itself.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.