EEAT Mechanics

ULP: the languages a user reads, as a profile

ULP, the User Language Profile, holds the languages a user can read, each weighted by a probability, so a bilingual user can get results in their second language. Google confirms that it does not force results into the settings language; the profile itself is RESONEO's reading.

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

01What the schema shows

Two objects sit in the quality_twiddler namespace: UlpQuerySignals and UlpResultSignals, query-level and per-result signals. RESONEO expands ULP as User Language Profile: a list of the languages a user can read, each weighted by a probability. Its example is someone whose first language is French but who can read English too and so can be shown English pages.

The pairing makes sense for a language rule: the query side holds what is known about the user, the result side the language of each page. Like every twiddler, it only recommends; the framework in Superroot, the layer that merges what Google's indexes return, decides. The parent article on twiddlers covers that framework.

Source per claim (2)
C
ULP has query-level signals (UlpQuerySignals) and result-level signals (UlpResultSignals) in the quality_twiddler namespace.[1]
C
RESONEO expands ULP as User Language Profile, the languages a user can read, each weighted by a probability; the probability profile is not described on any Google page we read.[2]

02What Google says about languages in Search

Google wrote on 8 September 2023 that about half of its searchers are multilingual and often search in a language other than their settings. The language setting in Search only controls buttons and menus; results are not forced to match it.

Google's help page lists what it weighs instead: the language of the query, whether content in another language is helpful, the display language, the language of the device, and the user's location. A per-user language profile would fit this description, but Google does not name one.

Source per claim (3)
O
"About half the people searching with Google are multilingual and often search in a language that doesn't match their settings."[3]
O
"The search results themselves are not forced to match the display language."[3]
O
Google lists the factors it weighs for the language of results: the query language, whether content is helpful, the display language, the device language and the user's location.[4]

03E-E-A-T and what a site owner can do

ULP has no E-E-A-T bearing. It matches languages to readers and says nothing about the quality of a page. What a site owner can do is what Google asks for: publish in the languages people use in a region and mark the language versions, so that the right one can be matched to the right reader.

Source per claim (2)
O
Google encourages publishers where several languages are common to create content in those languages, and to tell Google about localized versions of their pages.[3]
C
ULP is a language-matching rule with no E-E-A-T bearing.[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