EEAT Mechanics

FreshnessTwiddler / RealTimeBoost

BLeak, verbatim

For certain queries Google expects fresh content — the concept is called 'Query Deserves Freshness' (QDF).

By Thomas Wawra·Last reviewed
Function class
Freshness
Axis
Freshness
Reach
Doc
Calibration source
Pattern
Experience· noneExpertise· noneAuthority· noneTrust· indirect

What it measures

For certain queries Google expects fresh content — the concept is called 'Query Deserves Freshness' (QDF). FreshnessTwiddler gives current pages a temporary ranking boost. RealTimeBoost is the sharper variant for real-time events like severe weather or breaking news. Being current means ranking higher — but only if the query actually demands freshness.

Derived from

A combination of the document's freshness state (when was it last updated?) and the query's freshness demand (are many people currently searching with a time reference for this topic?).

Metric detail

FreshnessTwiddler = a freshness-dependent re-ranking boost (Query Deserves Freshness); RealTimeBoost = a sharper, short-lived boost for real-time/event spikes. [B fields, O/C QDF]

Why this attribution

Trust is indirect — an outdated severe weather warning is a breach of trust: someone relies on wrong information. Otherwise this system is E-E-A-T-neutral: freshness is not a dimension of expertise or authority.

Strategic consequence

Where timeliness matters — warnings, live data, fast-changing situations — freshness is central. But the freshness boost only works if pages are crawled and indexed in time (see Crawl-Budget, System 21). Editorial processes for fast updates must be synchronized with the technical infrastructure.

Related systems

Answer modules will appear here (coming soon)