Mic King The actual code was pushed to GitHub almost 2 years ago. It's clearly accidental from their automated SDK code generators, and just happened to catch our attention now.
x.com/derek_perkins/…

Mic King Legend Mic King for reporting on this.

Can ya'll remind me of the small websites that have written about losing a lot of Google traffic lately?

Y'all can stop with the 'the leak is fake' now.

Not me saying something different to every journalist that asks me 'what was the most interesting thing you found in the leak'

10 minute listen to Mic King Barry Schwartz and Moz's own Tom Capper commenting on the leak: redcircle.com/shows/today-in…

For the avoidance of doubt -- this is me.

Oh, and I made a quick Chrome extension that extends the sidebar of HexDocs so you can actually read the module names.

Let me know if y'all want that.

When an article about what you wrote is in your Discover feed. 😎

Y'all ready for another one or nah?

The @wordlift team is underappreciated for all they do.

I wear #13 btw

👇🏾

Word.

The leak was not done on purpose to distract from AI Overviews.

Cut it out.

Big thank you Gary 鯨理／경리 Illyes (so official, trust me) John 🧀 ... 🧀 Martin Splitt for the combined *thousands* of questions you've answered about Google Search over the years which are 'confirmed' by looking at this API documentation + *massive* logical leaps on my part. 🪄

You love to see it.

What. a. day!

You're going to see a lot about the Google leak over the next week or so, and I've already seen people jumping to all kinds of conclusions. Remember:

🤔 Just because something is referenced in the API leak does not mean it's 'a ranking factor'

🤔 Googlebot is a protocol buffer.

Legit take.