Group: LegacyTR
(12 ranking factors)
Factors |
---|
TR
web_production: 1
Text relevance (Maxfreq is the frequency of the most frequent word that makes sense of the length of the document).
|
TRp1
web_production: 4
Stript priority for TR is a text priority - there are all the words of the request somewhere in the document (while they pass contextual restrictions on the request, for example, both words DB in one sentence).
|
TRp2
web_production: 5
Weight: -0.109820338929289 PHRASE priority for TR is a text priority - there are all the words of the request in a row in the document.
|
TRtitle
web_production: 8
The presence of an accurate phrase (request text) in the header (more precisely, in the first sentence of the document). Contextual restrictions and feet are taken into account exactly as in TRP2, i.e. Factor [8] Minors Factor [5]
|
TRhr
web_production: 9
There was a plot that passed the quorum in which all the word positions are designated as those who have the relevance of Best_relev (title or Meta Keywords).
|
TRhitw
web_production: 16
Hitweigt is a variant of textual relevance, in which the weights of all hits are considered equal (i.e., they do not take into account the allowances for title and the proximity of words). In this case, the corresponding hits must be restricted by the syntactic sorcerer, i.e. We can assume that the TRHITW factor is 0 and only when Softandok is 0
|
TRref
web_production: 25
The factor about the number of Refines. In the queries, there is a feature of user refines ('' word that is faced with a percentage sign '). According to the idea, this means something like 'it would be good if the word in the document was'. The only famous ((http://staff.yandex-team.ru/gulin Andrey Gulin)) the valuable use of this feature is a request [ %official %site name of the film]. This feature is unknown to users, because Not described in any documentation. It is planned that it will disappear from the tongue of requests, but in the sorcerer the words with the priority of User_refine will remain. The factor indicates how much the maximum user_refine was simultaneously found in the framework of a single hit in the quorum. It is believed that there are from 0 to 3 (if> 3, then it is believed that 3). This number is waved in the half interval [0.1)
|
TRUnmapped
web_production: 39
TR divided by a cube of the number of words in a request and transformed by a standard REMAPTR.
|
HasNoTR
web_production: 61
The document has no TR.
|
TRp1All
web_production: 185
Options for relevant factors taking into account the feet of words
|
TRWithStops
web_production: 199
Weight of maximum coincidence of forms in the text and request
|
TR_W1
web_production: 391
Analogues of the factors of the same name, the weight of the word = 1
|