So many people discussing the #YandexLeak ranking factors, missing out on (part2)

Tag TG_DEPRECATED

Code clearly states what it means:

"the factor shall not be used anywhere, but it is still computed and may be present in existing formulas"

Yet, many discard these factors.
1/

https://twitter.com/cemper/status/1619651363570610177

The there's the additional factors.
Many just base their analysis on a single file shared by @searchmartin ca. 48 hours after the actual leak, and not the leak itself

You can't judge a software system with 100 Gigs source code based on 1 text file :)

https://twitter.com/cemper/status/1619818334048104449

2/

So many people discussing the #YandexLeak ranking factors.

But I think what's missing is a clear separation off static vs. dynamic factors.

It's tagged nicely in there.

TG_DYNAMIC depends on query

TG_STATIC does not depend on query

#yandex #seo

1/3 Second most important critera is the impact scope of any of those Factors ("modifiers")

TG_DOC
depends on document

TG_HOST
depends on host

TG_OWNER
depends on owner

TG_QUERY_ONLY
depends on query only, not document

#scope

2/3

The #YandexLeak is a "political" statement.

All the 100 GB files in the source code archive seem to have the same file date - Feb 24, 2022 - when Russia started its invasion of Ukraine.

It's a subtle hint that Putin will not get control over Yandex.

#yandex #yandexleak

1/4 That leak was an inside job, a highly privileged user - someone as powerful as the legendary "Matt Cutts" of Google...

So "political" means, for me, some kind of "defense" against the Putin regime having too much say in Yandex...

#yandex #yandexleak #leak #Russia

2/4