EEAT Mechanics

Document filter: a filter record known only by its schema name

One schema object, DocFilterInfo, belongs to the spam and safety family. RESONEO gives no description, and nothing else is known about it.

By Thomas Wawra· Published · Version 1.0· Systems referenced: Mustang / SuperRoot etc.

01What is known

The entry has a single schema object, DocFilterInfo, in the quality_twiddler namespace. The name says it holds information about filtering documents. RESONEO lists it in the family for spam, removals and safety, and, unlike most entries, adds no note.

Filtering is one of the actions a twiddler can recommend: take a result out of the list. As always, the framework in Superroot, the layer that fans a query out to Google's indexes and merges what comes back, makes the final call.

Source per claim (2)
C
The document filter consists of one schema object, DocFilterInfo, in the quality_twiddler namespace.[1]
C
RESONEO places DocFilterInfo in the spam, removals and safety family and gives no description of it.[2]

02What is not known

Which documents are filtered, on what grounds, for which queries and how often are all unknown. The name is generic enough to fit almost any filter, so it supports no guess about its purpose.

On our map the document filter belongs to the twiddler layer and to no E-E-A-T system.

Source per claim (1)
C
The name DocFilterInfo is too generic to indicate what is filtered or why; the entry is not mapped to any E-E-A-T system.[3]

03References

This Deep Dive is Layer 2 content. It interprets the material and always points back to Layer 1, the reference layer. Every claim is mapped to a source, labeled by type: [A] Sworn testimony · [B] Verbatim from the leak · [O] Documented by Google · [W] Peer-reviewed study · [S] Checked on the page · [C] Our assessment · [P] Patent.

© Thomas Wawra · Senior SEO Manager · wetter.com — a Funke Digital company