<b>Why outdated content is a trust failure, not a freshness failure</b>

<b>Why outdated content is a trust failure, not a freshness failure</b>

The question: when stale content gets demoted, is recency the signal or is something deeper happening?

The careful reading routes through trust. The QRG flags content that is inaccurate <i>because</i> it is out of date, especially on YMYL topics, as a trust problem. The issue is not the timestamp; it is that the page now makes claims that are no longer true. Recency is a proxy.

— A 2019 tax page citing repealed rules: untrustworthy, not merely old
— A 2010 page on a mathematical proof: old and perfectly trustworthy
— The demotion tracks accuracy decay, not the date field

Evidence: the guidelines tie 'outdated' to YMYL accuracy specifically. They do not penalize age in domains where information is stable.

Counter-evidence: query-deserves-freshness behavior in ranking does reward recency directly for some queries (news, trending). That is a separate ranking mechanism from the quality-label logic, and conflating them causes mistaken 'update everything monthly' strategies.

Caveat: a changed date with unchanged stale content is the worst case, it signals false freshness, which is itself a trust violation.

What we still don't know: how systems distinguish genuinely-stable evergreen content from neglected content that merely hasn't decayed yet.

—
Если тема зашла, посмотри @thesignalnoise