Skip to content
/Google Search API Leak (2024)
📘Concept

Google Search API Leak (2024)

최종 업데이트:

Definition

A leaked set of internal Google API documents from May 2024 that revealed the actual use of ranking factors which Google had officially denied.

TL;DR

In May 2024, internal Google API documents (2,596 modules, 14,014 attributes) released by Rand Fishkin (co-founder of SparkToro) confirmed the existence of several ranking signals Google had officially denied. These included click data (NavBoost), a site-level authority score (siteAuthority), and the use of Chrome browser data.

Key Findings

NavBoost — Using Click Data for Ranking

Google long maintained the official position that "click-through rate is not a ranking factor." However, the API documents confirmed a system called NavBoost. This system tracks users' click patterns—long clicks vs. short clicks—and factors them into ranking.

siteAuthority — Site-Level Authority Score

Google employees repeatedly stated that "we do not use a score like domain authority." Yet the API documents contain an attribute called siteAuthority, indicating that a site-level authority score is used in ranking.

Use of Chrome Data

It was confirmed that user behavior data from the Chrome browser is used in evaluating search quality. Google had previously stated that it does not use Chrome data for search ranking.

Other Findings

  • Internal tracking of authorship information
  • The existence of a "sandbox" period for new sites
  • Quality evaluation at the site level rather than the page level

Impact on SEO/AEO

Practical implications confirmed by this leak:

  1. Click-through rate matters: CTR optimization (compelling titles, meta descriptions) affects ranking directly rather than indirectly.
  2. Site authority is real: Building authority for the entire site—not just a single page—matters.
  3. User behavior is a core signal: Dwell time, return visits, and bounce rate are reflected in ranking.

Caveats

The existence of an attribute in the API documents does not necessarily mean that attribute is currently active. Some may be past experiments or deprecated features. Google's official response to the leak was that "the internal documents do not accurately represent how Search works."

Related Sources

이런 항목도 있어요

이 페이지가 도움이 됐나요?