Our Four-Part Series About Google’s API Documents Leak
This article is the first in a four-part blog series about the Google API documents leak and its impact on small and midsize businesses (SMBs).
Table of Contents for Google API Documents Leak
In this four-part blog series, we share:
- 7 SEO Caveats for SMBs: Insights from the Google API Leak
- SMB SEO Validation: Our Proven Tactics Confirmed by Google Leak
- 12 Key SEO Tips for SMBs: Post-Google Leak Focus
- Google Leak: 12 Shocking SEO Revelations for SMBs
This is Part 1 of the series.
7 SEO Caveats for SMBs: Insights from the Google API Leak
Before we uncover the attributes behind the leaked documents, here are 7 caveats small and midsize businesses (SMBs) need to know.
1. Incomplete SEO Factors in the API Documents.
Although the Google leaked documents contain 14,004(!) attributes that Google tracks, these documents are likely incomplete regarding all factors and systems that impact search engine optimization (SEO).
For example, we did not see mentions of Google Business Profile (GBP) attributes. Google likely uses other systems besides the ones in the leaked document to define its search return pages.
2. Some API Documents Described SEO and Chrome, and Some Did Not.
Not all 14,0004 document attributes concern Chrome and search engine return pages (SERPs).
SMBs should understand that some document attributes describe characteristics of other Google products, such as YouTube.
3. Attributes vs. Algorithm Factors.
An attribute is a feature Google tracks; it is not necessarily an algorithm factor.
We liken it to an ingredient. Just because an ingredient is in your pantry doesn’t mean you use it daily in a recipe—or ever use it.
We can’t be sure that ANY ingredient (attribute) is in the ultimate algorithm “recipe.”
4. Relative Importance and Weights of the Algorithm Attributes.
Although tracked attributes and algorithm factors are not necessarily identical, many of the attributes in the API documents DO appear to be factors that Google tweaks to one extent or another for the search algorithm.
In other words, many of these “ingredients” (attributes) appear to be used in Google’s recipes.
However, we don’t know the comparative weights of each attribute.
Continuing the recipe analogy, the algorithm may include flour and salt, but we don’t know the relative proportions of each. Does the algorithm include a “pinch” of an attribute or several pounds?
5. Twiddling.
Furthermore, as we have long known, Google changes its algorithm at least five times daily and regularly makes more major changes.
Additionally, we now know that Google uses a “twiddler.” Twiddlers tweak factors up and down. This is a new word for SEOs. Perhaps because search marketing needs more jargon. (joking)
6. Still the Flavor of the Day?
The documents seem to have been used for search as recently as March 2024. But this is just one moment in time.
We don’t know which factors Google may have changed since the leak. In other words, has Google altered the recipe? The ingredients?
Additionally, we know that Google had several major ranking updates since this time. This included a March spam update and a CORE update incorporating the so-called “helpful, people-first” content update. The March updates devastated many SMBs.
Moreover, the leaked Google API documents noted that Google had already “deprecated” some attributes—they are no longer being tracked (aka removed from the recipe). Others are scheduled to be deprecated.
7. More Attribute Updates to Come.
Finally, 14,004 attributes are a LOT to review. Moreover, most SEOs focus on enterprise businesses. We will be culling through insights for weeks to come and shedding light on how SMBs may be impacted.
Next up:
Part 2: SMB SEO Validation: Our Proven Tactics Confirmed by Google Leak
What Is the Google API Documents Leak?
Bot “Oops” and What The Google Documents Leak Includes
On March 13, 2024, an automated bot accidentally put 2,596 modules of confidential documents about “attributes” that Google tracks for various Google products on Google’s public repository, called GitHub.
This included information for Chrome’s search engine optimization (SEO), YouTube, and more.
Around May 7, Erfan Azimi, CEO of AE Eagle Digital, stumbled upon these documents and couldn’t believe what he saw. Was this real? Were the modules fakes?
Decoding the Google Leaked Documents
Erfan brought these to the attention of Rand Fishkin, the founder of Moz, who has moved on from his SEO endeavors. In turn, Rand shared these with confidante Michael King on May 24. Mike King is the CEO and founder of iPullRank, an SEO company for enterprise businesses.
Together, Rand and Mike poured over the documents. They had two objectives: 1) to verify that the documents were “real,” and 2) to identify what the contents might mean for SEO.
On May 27, 2024, Rand publicly shared information about the leaked documents and linked his article to an iPullRank webinar on the same topic.
Google Validates the Documentation Is Real
On May 29, Google validated that the documents were indeed real but lacked “context.” They cautioned against assumptions.