A former employee allegedly leaked a Yandex\u00a0source code repository, part of which contained more than 1,900 factors the search engines uses for ranking search results.<\/p>\n
Why we care.<\/strong> This leak has revealed 1,922 ranking factors Yandex used in its search algorithm, at least as of July 2022. Perhaps Martin MacDonald put it best on Twitter<\/a> today: \u201cThe Yandex hack is probably the most interesting thing to have happened in SEO in years.\u201d <\/p>\n Yandex is not Google. <\/strong>If you plan to read the full list of Yandex ranking factors, remember that Yandex is not Google. If you see a ranking factor listed by Yandex, that doesn\u2019t mean Google gives that signal that same amount of weight. In fact, Google may not use all of the 1,922 factors listed. <\/p>\n That said, a lof of these ranking factors may be quite similar. So reviewing this document may provide some useful insights to better help you understand how search engines, such as Google, work from a technological standpoint.<\/p>\n The bigger picture. <\/strong>The code appeared as a Torrent on a popular hacking forum, as reported by Bleeping Computer<\/a>:<\/p>\n \u2026the leaker posted a magnet link that they claim are \u2018Yandex git sources\u2019 consisting of 44.7 GB of files stolen from the company in July 2022. These code repositories allegedly contain all of the company\u2019s source code besides\u00a0anti-spam rules.<\/p>\n Yandex calls it a leak.<\/strong> Because the code appeared on a popular hacking forum, it was first thought that Yandex was hacked. Yandex has denied this, and provided the following statement:<\/p>\n \u201cYandex was not hacked. Our security service found code fragments from an internal repository in the public domain, but the content differs from the current version of the repository used in Yandex services.<\/p>\n A repository is a tool for storing and working with code. Code is used in this way internally by most companies.<\/p>\n Repositories are needed to work with code and are not intended for the storage of personal user data. We are conducting an internal investigation into the reasons for the release of source code fragments to the public, but we do not see any threat to user data or platform performance.\u201d<\/p>\n Dig deeper.<\/strong> You can find more coverage of the leak on Techmeme<\/a>.<\/p>\n Yandex ranking factors list.<\/strong> MacDonald shared the full list of 1,922 factors here<\/a> on Web Marketing School. I highly recommend downloading it, as I fully expect Yandex will try to scrub this information from the internet. There is also a translated version on Dropbox<\/a>.<\/p>\n Alex Buraks also has an ongoing Twitter thread<\/a> analyzing the various ranking factors. Many are what you\u2019d expect to see \u2013\u00a0PageRank, text relevancy, content age and freshness, lots of end-user behavior factors, host reliability and many link-related factors (e.g., age, relevancy, etc.)<\/p>\n Some of the ranking factors SEOs are finding surprising: number of unique visitors, percent of organic traffic and average domain ranking across queries.<\/p>\n The post Yandex \u2018leak\u2019 reveals 1,922 search ranking factors<\/a> appeared first on Search Engine Land<\/a>.<\/p>","protected":false},"excerpt":{"rendered":" A former employee allegedly leaked a Yandex\u00a0source code repository, part of which contained more than 1,900 factors the search engines uses for ranking search results. Why we care. This leak has revealed 1,922 ranking factors Yandex used in its search algorithm, at least as of July 2022. Perhaps Martin MacDonald put it best on Twitter today: \u201cThe Yandex hack is probably the most interesting thing to have happened in SEO in years.\u201d Yandex is not Google. If you plan to read the full list of Yandex […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"h5ap_radio_sources":[],"cybocfi_hide_featured_image":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-7902","post","type-post","status-publish","format-standard","hentry","category-best-seo-blogs"],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":false,"author_link":"https:\/\/craighordlow.com\/author\/"},"_links":{"self":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts\/7902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/comments?post=7902"}],"version-history":[{"count":0,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts\/7902\/revisions"}],"wp:attachment":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/media?parent=7902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/categories?post=7902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/tags?post=7902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}