Have you heard of the Rabbit Bug? Find out in this article how the Rabbit Bug managed to break the Google’s SERPs.
Three weeks ago, I was a guest at SEontheBeach in La Manga, Spain for the first time. I had heard lots of great things about this event, so I was really excited to be invited to speak there, especially since Google’s Gary Illyes and I were the only ones invited who weren’t Spanish speakers. SEontheBeach turned out to be one of the best “pure” SEO events I have ever been to, because all the best Spanish SEOs were there and they shared their knowledge very openly. The Spanish SEO community has a great reputation, especially when it comes to pushing the boundaries and trying lots of SEO experiments.
When I arrived in La Manga, the beach was buzzing with the story of a legendary Spanish SEO, who had managed to break the Google SERPs with what he called “the Rabbit Bug” just two days before the event. Still, most people didn’t really know what exactly happened, so I was eager to finally read the whole story on Alex Navarro’s Blog Vivirdelared.com. (You should definitely keep Alex’s Blog on your radar – he’s a well-known Spanish SEO expert from Alicante and his blog is one of the most-read Spanish SEO blogs).
The story about the Rabbit Bug is so interesting that I didn’t want my English- and German-speaking SEO friends to miss out, so here’s the translation of the interview Alex conducted with Alvaro Peña from iSocialWeb, who found this incredible Google bug:
This bug came to light on #SEOMafia, a twitter group of SEOs who conspire against Google on a daily basis. In the group, Xavi Viguer tweeted:
“Gentlemen! Albert Esteve from my team has found the following information:”
This conversation led to this tweet:
After the tweet:. most of the staff didn’t even know about the node, but with one thing and another, it ended up reaching JohnMu…
…and after a couple of days, the result of that query and other similar ones were solved. But now…
Since many of you followed the Twitter thread about this error, let’s clarify this point before we go into more detail about the Rabbit Bug.
Today is June 28th, and if we look for “Loro” (parrot) in Google, we see the following:
The search stops after just three results. This is how I discovered the bug was still active. So it wasn’t gone, it was just biding its time.
From the image and tweet above, you can see that the bug causes a breakdown in the SERPs. All results ranking after the website that implement this technique no longer appear in the Google search results.
What’s the implication of this? Well, if you’re ranking in the top position, and you apply this technique, you’ll be the only one left in the Google search results. Similarly, if you are second or third, you will only have one or two more companions to share the CTR with instead of 10.
It would make little sense to be penalized. This is a bug in the search engine, so it is not going against Google policies, and it could be generated by chance. Google will solve it when they solve it, and that will be it.
Here comes my interpretation of why I think the error occurs. If anyone has a different idea, let’s discuss it so that we can learn from each other.
If you have basic programming skills or have done any coding, at some point you will have had problems with quotation marks, double quotation marks, and special characters. If they are not implemented correctly, you find code breaks, leading to unwanted results.
Let’s make an analogy with a programming language that the vast majority of people know, and let’s give an example that everyone can understand easily. Imagine we have the construction of a PHP language called echo, which shows one or more strings.
Something very typical with this sentence could be:
echo “hello world”;
This would return => hello world
Now, what if we had:
echo “Hello”, Mr. Alex Navarro.”
When the programming language in question processes the string, you will find that it begins with “Hello” and ends with the following double quotes: “Hello”. So everything that comes after that, will generate an error and break down, as it does not have the right structure.
If you have understood this, you will be able to easily understand what is happening in the rabbit’s SERPs error. Let’s see the picture of the breakup:
If you look carefully, the rupture occurs after processing the emoji. So the way in which Google processes this chain does not allow for special cases that can’t be foreseen.
First of all, you have to take into account that this bug cannot be applied in all searches. In order for this error to be reproducible and usable, it must be possible for Google to scrape information from HTML tables and display it as added information in its results.
This is something that happens a lot in animal-related searches, for example, where Google takes additional information, for example about the animal kingdom, and species.
But this is not the only case, you can also find it in ticket prices and other searches, for example:
All these pages have a common pattern and are nothing more than HTML tables. Google searches for additional information, and the tables give Google an easy way of classifying and schematizing this type of information, so Google uses these tables to collect data.
Well, no, you need a little more. This is how you would create the bug:
1. Generate an HTML table with interesting information for Google to display in the SERPs.
2. Generate links with anchors in the table fields.
3. Add an emoji within the link text.
You can see this on this website for example:
** Retrieved from the website of Christian Ranz Pangeanimales.com
Erroneous processing of special characters in the SERPs is not common, but we have found and exploited these bugs on other occasions. An example is this character (or however you would define this):
At the time, this character generated an anomaly in the SERPs that generated something similar to this:
With this anomaly, when the character appeared, the length of the text of each search result was moved proportionally to the length of the character. This happens now for example in the Twitter app, as you can see with this example from my friend Victor:
In fact the result that I showed you in the first image is the concatenation of both characters
Before I finish the article, I would like to highlight something. Sharing this type of “tip” is not intended to spam SERPs, but to make the community think, and realise that we can all find errors that give us advantages over the competition in SEO which can help us to better understand how Google works.
Professionals like Alex Navarro or Chuiso are exceptional because they really think about the different SEO areas. Don’t attempt to blow up the Google Search results, but contribute what you can, give it added value, and in that way we all will win ;) Both SEOs and Google can use these sorts of experiements as free testers.
Thanks to Alex and his team for giving iSocialWeb the opportunity to get into their home. We hope to share more interesting topics soon!
P.S. from Ryte: Thanks to the great SEOs Alex and Alvaro for sharing this content, and allowing us to make it available to our English readers!
Practice makes perfect!
Analyze your website with Ryte for FREE
Published on 07/02/2018 by Marcus Tandler.
Marcus loves SEO. He’s a proud member of the Achuar tribe and his Indian name “Ni Nawenak Ukutin“ (“White warrior who shot himself into the foot“) reveals why he must not carry a weapon in the jungle any more. Marcus is happy to live on nothing but pretzels, kaiserschmarrn and streuselkuchen for days on end.Become a guest author »
Get more traffic and customers by optimizing your website, content and search performance. What are you waiting for?Register for free
Do you want more SEO traffic?
Improve your rankings for free by using Ryte.Register for free