Updating frequently vs. building a stable canonical resource
The question: does a trust-bearing page benefit more from frequent updates, or from being a stable, rarely-changed reference that accrues links and citations over time?
Freshness is a real signal for query-deserved-freshness intents — Google's documented freshness systems date back to the 2010 'Caffeine'/freshness work and the QDF concept. But the QRG also values content that is accurate and maintained, which is not the same as constantly churned. The tension is between recency and durability.
The decisive variable is query intent. For 'best laptop 2026' or anything tied to a changing world, staleness is a direct trust failure — outdated YMYL or product content is flagged in the guidelines. For a definitional, historical, or methodological resource, stability is the asset; needless edits can reset accumulated trust signals and disrupt a page that the open web already cites.
A common error is performative freshness: changing the date without changing the substance. The guidelines and reader trust both penalize the deception when it is detected.
Caveat: 'freshness as ranking factor' is intent-specific and easily overgeneralized; there is no evidence that updating an evergreen page on a stable topic helps, and some that disruptive edits hurt.
What we still don't know: how systems weigh genuine substantive updates against the accumulated citation history a stable page carries.
Trust Signal Co
@TrustSignalCo
Updating frequently vs. building a stable canonical resource
Этот пост опубликован в Telegram-канале Trust Signal Co. Подписаться можно по ссылке: @TrustSignalCo.