There’s a recurring mistake in editorial SEO plans: treating freshness and depth as though they’re the same goal, or at least compatible ones. They’re not — and Google’s ranking systems handle them through different mechanisms, triggered by different query signals, evaluated on different timescales.
Getting this wrong means you end up doing continuous updates to content that doesn’t need them, or leaving genuinely stale pages untouched because they rank fine today. Both are real problems, and they compound over time.
What Google Actually Means by Freshness
Freshness as a ranking signal isn’t a single dial. Google’s QDF (Query Deserves Freshness) system — described publicly by Amit Singhal in 2011 and still demonstrably active — applies different freshness weights depending on query type. The three broad categories that trigger higher freshness weighting are: recent events, recurring events, and hot queries with sudden spike patterns.
For most evergreen informational queries — “how does crawl budget work,” “what is canonical URL” — QDF weighting is low. The document that wins is usually the one with the most coherent passage-level coverage, not the one updated three weeks ago. Refreshing that content with a new paragraph about the latest Google blog post changes the date, not the freshness signal. Those are not the same thing.
The freshness signal Google actually calculates has three components that matter for most SEO work:
- Document inception date — when Googlebot first crawled a substantially new version of the page
- Content change rate — how frequently the core content block (not boilerplate, not nav) changes over time
- Link freshness — when inbound links pointing to the URL were acquired, and how recently those linking pages themselves were crawled
A minor content refresh — fixing a typo, adding a sentence, updating a date in a meta description — doesn’t reliably trigger re-indexing at a meaningful level. What does: a substantial rewrite of the primary content block, changes to the H1/title structure, or a meaningful increase in internal links pointing at the page from recently-updated pages.
What Google Means by Depth (And Why It’s Not Word Count)
We’ve written separately about how Google infers topical depth from a single page. Short version: passage retrieval plus entity density plus coverage of semantically adjacent subtopics. Not raw character count.
But depth also has a document-level and a site-level component that interact in ways most editorial plans miss. A single long-form page on “technical SEO audit” can demonstrate depth on that topic. Google’s systems also evaluate whether the site around that page has coherent coverage of related subtopics — log file analysis, crawl budget, rendering, structured data — because that cluster signals genuine expertise, not just one well-optimized page.
This is why rebuilding one piece of content to be longer rarely moves rankings the way adding the next missing subtopic page does. The depth signal that matters for authority is distributed across the cluster, not concentrated in a single document.
Where They Pull in Opposite Directions
Building genuine depth requires stable, coherent, internally-linked content structures. You write the canonical piece, then the supporting pieces, then you build the internal link architecture that signals hierarchy to Google. That process takes weeks to months, and it works best when core pages aren’t constantly being edited — repeated edits fragment the crawl schedule and can reset the signals Google has accumulated about that page’s relevance.
Chasing freshness on those same pages — re-opening the canonical piece every few weeks to add sections, update statistics, restructure headings — disrupts that accumulation. Googlebot sees a different document each time it crawls. The entity graph Google has built for that URL keeps getting partially invalidated. You’re trading a slow-building depth signal for a freshness signal that only matters if your query type actually triggers QDF weighting.
For most informational SEO content, it doesn’t. QDF matters heavily for news, event coverage, and trending queries. For “how to audit internal links” or “what is topical authority” — the kind of content most SEO-focused sites are building — freshness weighting is marginal. The document that ranks is almost never the most recently updated one; it’s the one with the most coherent passage coverage and the strongest cluster of supporting pages.
The Exception: Content That’s Both
There is a real category of content where freshness and depth are genuinely complementary: topics where the factual ground keeps shifting. SEO itself is a clear example — a 2022 piece on AI Overviews is now materially wrong in ways that affect trust, not just completeness.
For those pages, the right model isn’t continuous micro-edits. It’s periodic substantial rewrites that update core claims, add new subtopics where the landscape has changed, and update the internal link structure to reflect supporting content added since original publication. That kind of update generates a real freshness signal — new inception date, substantively different content block — while also strengthening the depth signal by incorporating newly relevant entities and subtopics.
The distinction is: substantial rewrite on a meaningful cadence vs. cosmetic refresh on a high cadence. In our experience looking at log file data across sites running aggressive refresh programs, the refresh activity shows up clearly as increased Googlebot visits — but ranking movement is often flat or negative because the underlying depth signal is being disrupted rather than compounded.
A Practical Decision Framework
Before touching an existing page, answer this first: what type of query does this page target, and does that query type trigger QDF weighting?
If yes — the query is event-driven, trending, or tied to a specific time period — freshness is a legitimate lever. Prioritize updating core factual claims, not just the date in the byline.
If no — evergreen informational query — the right audit question is whether the page has a depth problem or a cluster problem. Depth problem: the page doesn’t cover the subtopics Google associates with the query. Cluster problem: the page has decent coverage but supporting pages don’t exist or aren’t linked. These have different fixes. Rewriting the canonical page treats a cluster problem as if it were a depth problem, which doesn’t work.
One thing worth being straight about: diagnosing which problem you have requires looking at what actually ranks for the query, not just at your own page. If the top-ranking pages are shorter than yours, you almost certainly don’t have a depth problem — you have a cluster or authority problem. More words won’t fix it.
What This Means for Editorial Planning
Separate your “depth-building” content from your “freshness-maintenance” content and manage them on different schedules with different KPIs.
Depth-building content — evergreen canonical pages, supporting cluster pages, internal architecture — should be relatively stable once published. Measure it by cluster coverage completeness and ranking stability over 60-90 day windows, not by whether you updated it this month.
Freshness-maintenance content — anything tied to events, Google updates, algorithm changes, industry news — needs a refresh process, but that process should be triggered by substantive factual changes, not by a calendar date. “It’s been 90 days, update it” is not a freshness strategy.
The sites that compound authority fastest are the ones that leave stable content stable and build outward — new subtopic coverage, new supporting pages, stronger internal link architecture — rather than cycling back to the same canonical pages without a clear factual reason to do so.
If you’re running a content refresh program right now, pull the log file data first. Check whether your refresh activity actually correlates with increased crawl frequency on those pages, then whether that crawl frequency correlates with ranking movement. Often it doesn’t. Worth knowing that before you spend another quarter on the same approach.