The Google API leak is the 2024 publication of internal documentation for Google Search’s Content Warehouse API. The material contains over 2,500 pages and 14,014 attributes. It describes data and modules, but not how strongly they affect rankings. The leak is a closed 2024 event. For what counts in ranking today, Google’s own documentation and the findings of the court in the US antitrust case remain the reliable sources.
At a glance
- Type
- Publication of internal documentation (event)
- Started
- March 27, 2024 (according to SparkToro)
- Completed
- May 7, 2024 (according to SparkToro, publicly accessible until)
- Affects
- Data fields and modules of the Content Warehouse API, no weights
- Confirmed by
- no, according to reports only; no Google documentation
Last checked:
What happened?
According to SparkToro, the documentation was uploaded to a public GitHub repository on March 27, 2024 and stayed accessible until May 7, 2024. Rand Fishkin of SparkToro received it from an anonymous source and published his findings in 2024. He reports that former Google employees who reviewed parts of it considered it legitimate, and that Mike King, founder of iPullRank, who analyzed it, also considers it legitimate.
What does it show?
The files read like an internal inventory of data elements available to Search engineers. They mention, for example, NavBoost together with click data. SparkToro states that the documents do not show the weight of individual elements in ranking and do not prove which elements are in use. Some may be old, experimental or switched off.
How should the leak be read?
As a source of terms and data structures. Claims such as “confirmed ranking factors” go beyond what the documents say.
Sources
- Leaked Google Search API documents – SparkTorosparktoro.com
- United States v. Google LLC, Memorandum Opinion, Findings of Fact (2024-08-05)storage.courtlistener.com
Last updated: