EEAT Mechanics

Shopping personalization: personal adjustment of shopping results

Two annotations point to a twiddler that personalises shopping results. Google's help page names the inputs for personalised shopping in general; that this twiddler uses them is likely but not shown.

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

01What the schema shows

The schema list has ShoppingP13nTwiddlerResultAnnotation and P13nResultAnnotationForShopping. P13n is the common shorthand for personalization: a p, thirteen letters, an n. Both are result annotations, so the twiddler leaves something on each shopping result that later steps read.

RESONEO describes it only as a personal adjustment of shopping results. The schema names do not say which personal data is used. Like other twiddlers, it can only recommend.

Source per claim (2)
C
Shopping personalization has two result annotations in the quality_twiddler namespace: ShoppingP13nTwiddlerResultAnnotation and P13nResultAnnotationForShopping.[1]
C
RESONEO describes the twiddler as a personal adjustment of shopping results, without naming the inputs.[2]

02What Google says about personalised shopping

Google's Shopping help page says products are ranked by relevance and also by a person's search terms and other Google activity. Under personalisation it names searches, views and other browsing on Google, plus saved shopping preferences such as brands and styles. Users can edit those preferences and manage personalisation in their settings.

The page describes the product, not the code. That the twiddler is the part that applies these inputs fits its name, but no source connects the two.

Source per claim (3)
O
"Products are ranked based on relevance, as well as your search terms and other Google activity."[3]
O
"The products you see may be based on your searches, views, and other browsing on Google, as well as shopping preferences you’ve saved."[3]
C
That the shopping personalization twiddler applies the inputs named on Google's help page is a reading of its name; no source links the two.[4]
Source: eeat-mechanics, own reading · Mustang / SuperRoot etc.

03E-E-A-T and the system map

Personalisation is not E-E-A-T. It changes what one person sees, not how a page is judged. The namespace quality_twiddler is not evidence of a quality judgement either; it is where the code lives. A shop cannot optimise for this beyond being the brand or store a person has looked at, liked or saved before.

Source per claim (1)
C
Shopping personalization has no E-E-A-T bearing; the quality_twiddler namespace says where the code lives, not that quality is judged.[5]

04References

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