Freshness twiddler: a second version and a setting for Human Voices
Beyond the FreshnessTwiddler known from the leak, the schema list shows a FreshnessTwiddler2 with its own settings for HuVo, short for Human Voices. What the second version changes and how HuVo is treated differently is not known.
01What the schemas add
The query-dependent freshness system has its own deep dive on this site, /deep-dive/freshness-twiddler. It covers Query Deserves Freshness, the patent on update scoring and staleness, and what that means for updates. This article does not repeat it. It covers what the schema list adds.
There are four objects. FreshnessTwiddlerDocAnnotations holds information attached to each document, FreshnessTwiddlerQueryAnnotations information attached to the query. Two more belong to FreshnessTwiddler2: FreshnessTwiddler2Params, the settings sent with the query, and FreshnessTwiddler2HuVoParams, a separate set of settings for HuVo.
RESONEO expands HuVo as Human Voices, a label it applies to forum posts, social media and creator material. If that reading is right, freshness is tuned differently for such content than for ordinary pages. In which direction, and for which queries, the schema names do not say. Nor do they say whether FreshnessTwiddler2 replaced the first version or runs beside it.
02What the leak says
The leaked API documentation names the twiddler in one place we have checked. In PerDocData, the large per-document record, a field with date-related information carries the note that it is used in FreshnessTwiddler, with the example that a page is old judged by its date annotations.
RESONEO goes further and says the twiddler reads both a page's stated dates and a date Google estimates for its content, derived from the page text, inbound anchor text and associated pages. That is RESONEO's summary; we have not verified this wording in the leak.
03What Google says publicly
Google confirms the principle, not the twiddler. Its guide to ranking systems mentions several "query deserves freshness" systems for queries where fresher content is expected. Its documentation on byline dates says that Google looks at several date factors, because any single one can be wrong.
That second point is why the freshness twiddler depends on date triangulation (system 25): the twiddler can only judge freshness as well as the date it is given. Neither Google page mentions HuVo, a second version, or different freshness rules for forum and social content.
04E-E-A-T and what a site owner can do
Freshness touches E-E-A-T only through trust, and only indirectly: an outdated answer to a time-sensitive question lets the reader down. Otherwise it is a timing rule. What a site owner controls is the date signal. Google asks for a visible, labelled date and for dates that agree between the page and its structured data. A faked date gains nothing if the dates do not agree, which is the point of triangulation.