HUGE Google Search document leak reveals inner workings of ranking algorithm

The documents reveal how Google Search is using, or has used, clicks, links, content, entities, Chrome data and more for ranking.

A trove of leaked Google documents has given us an unprecedented look inside Google Search and revealed some of the most important elements Google uses to rank content.

What happened. Thousands of documents, which appear to come from Google’s internal Content API Warehouse, were released March 13 on Github by an automated bot called yoshi-code-bot. These documents were shared with Rand Fishkin, SparkToro co-founder, earlier this month.

  • Read on to discover what we’ve learned from Fishkin, as well as Michael King, iPullRank CEO, who also reviewed and analyzed the documents (and plans to provide further analysis for Search Engine Land soon).

Why we care. We have been given a glimpse into how Google’s ranking algorithm may work, which is invaluable for SEOs who can understand what it all means. In 2023, we got an unprecedented look at Yandex Search ranking factors via a leak, which was one of the biggest stories of that year.

This Google document leak? It will likely be one of the biggest stories in the history of SEO and Google Search.

What’s inside. Here’s what we know about the internal documents, thanks to Fishkin and King:

  • Current: The documentation indicates this information is accurate as of March.
  • Ranking features: 2,596 modules are represented in the API documentation with 14,014 attributes.
  • Weighting: The documents did not specify how any of the ranking features are weighted –?just that they exist.
  • Twiddlers: These are re-ranking functions that “can adjust the information retrieval score of a document or change the ranking of a document,” according to King.
  • Demotions: Content can be demoted for a variety of reasons, such as:A link doesn’t match the target site.SERP signals indicate user dissatisfaction.Product reviews.Location.Exact match domains.Porn
  • Change history: Google apparently keeps a copy of every version of every page it has ever indexed. Meaning, Google can “remember” every change ever made to a page. However, Google only uses the last 20 changes of a URL when analyzing links.

Links matter. Shocking, I know. Link diversity and relevance remain key, the documents show. And PageRank is still very much alive within Google’s ranking features. PageRank for a website’s homepage is considered for every document.

Successful clicks matter. This should not be a shocker, but if you want to rank well, you need to keep creating great content and user experiences, based on the documents. Google uses a variety of measurements, including?badClicks, goodClicks, lastLongestClicks and unsquashedClicks.

Also, longer documents may get truncated, while shorter content gets a score (from 0-512) based on originality. Scores are also given to Your Money Your Life content, like health and news.

What does it all mean? According to King:

  • “[Y]ou need to drive more?successful?clicks using a broader set of queries and earn more link diversity if you want to continue to rank. Conceptually, it makes sense because a very strong piece of content will do that. A focus on driving more qualified traffic to a better user experience will send signals to Google that your page deserves to rank.”

Documents and testimony from the U.S. vs. Google antitrust trial confirmed that Google uses clicks in ranking – especially with its Navboost system, “one of the important signals” Google uses for ranking. See more from our coverage:

Brand matters. Fishkin’s big takeaway? Brand matters more than anything else:

  • “If there was one universal piece of advice I had for marketers seeking to broadly improve their organic search rankings and traffic, it would be: ‘Build a notable, popular, well-recognized brand in your space, outside of Google search.'”

Entities matter. Authorship lives. Google stores author information associated with content and tries to determine whether an entity is the author of the document.

SiteAuthority: Google uses something called “siteAuthority”.

Chrome data. A module called ChromeInTotal indicates that Google uses data from its Chrome browser for ranking.

Whitelists. A couple of modules indicate Google whitelist certain domains related to elections and COVID – isElectionAuthority and isCovidLocalAuthority. Though we’ve long known Google (and Bing) have “exception lists” when “specific algorithms inadvertently impact websites.”

Small sites. Another feature is smallPersonalSite – for a small personal site or blog. King speculated that Google could boost or demote such sites via a Twiddler. However, that remains an open question. Again, we don’t know for certain how much these features are weighted.

Other interesting findings. According to Google’s internal documents:

  • Freshness matters – Google looks at dates in the byline (bylineDate), URL (syntacticDate) and on-page content (semanticDate).
  • To determine whether a document is or isn’t a core topic of the website, Google vectorizes pages and sites, then compares the page embeddings (siteRadius) to the site embeddings (siteFocusScore).
  • Google stores domain registration information (RegistrationInfo).
  • Page titles still matter. Google has a feature called titlematchScore that is believed to measure how well a page title matches a query.
  • Google measures the average weighted font size of terms in documents (avgTermWeight) and anchor text.

The articles.

Update, May 29. Google provided a statement to Search Engine Land. Read our follow-up: Google responds to leak: Documentation lacks context.

Update, May 30. King has written a follow-up article for Search Engine Land:

  • Join Mike King and I at SMX Advanced for a late-breaking session exploring the leak and its implications.?Learn more here.

Dig deeper. Unpacking Google’s massive search documentation leak

Quick clarification. There is some dispute as to whether these documents were “leaked” or “discovered.” I’ve been told it’s likely the internal documents were accidentally included in a code review and pushed live from Google’s internal code base, where they were then discovered.

The source. Erfan Azimi, CEO and director of SEO for digital marketing agency EA Eagle Digital, posted a video, claiming responsibility for sharing the documents with Fishkin. Azimi is not employed by Google.


要查看或添加评论,请登录

社区洞察

其他会员也浏览了