So we all thought that the Google Bombs against our Commander and Chief were over. Well we were all mistaken. President Obama has not even crescent the White House thrown yet and has already been bombed by the blogger sphere.

I was on Twitter last week when someone posted the search results of the term “Failure”. We are all aware of what happened back in 2004 to our former Commander and Chief, he was Google bombed and decided to go and bomb Iraq; Google has denied any involvement in that invasion!

So what causes Google Bombs and why can’t they be stopped. The answer is simple; it’s in the ALGO. Unless Google makes some major changes to their algorithm, this will continue to happen. Now in all fairness, it does take a mass amount of users to complete a Google bomb, but, as we know, it is very much possible. On my birthday last year (Jan 25th) Matt Cutts gave his definition of Google bombs and Google’s solution to the problem.

We wanted to give a quick update about “Googlebombs.” By improving our analysis of the link structure of the web, Google has begun minimizing the impact of many Googlebombs. Now we will typically return commentary, discussions, and articles about the Googlebombs instead. The actual scale of this change is pretty small (there are under a hundred well-known Googlebombs), but if you’d like to get more details about this topic, read on.

First off, let’s back up and give some background. Unless you read all about search engines all day, you might wonder “What is a Googlebomb?” Technically, a “Googlebomb” (sometimes called a “linkbomb” since they’re not specific to Google) refers to a prank where people attempt to cause someone else’s site to rank for an obscure or meaningless query. Googlebombs very rarely happen for common queries, because the lack of any relevant results for that phrase is part of why a Googlebomb can work. One of the earliest Googlebombs was for the phrase “talentless hack,” for example.

People have asked about how we feel about Googlebombs, and we have talked about them in the past. Because these pranks are normally for phrases that are well off the beaten path, they haven’t been a very high priority for us. But over time, we’ve seen more people assume that they are Google’s opinion, or that Google has hand-coded the results for these Googlebombed queries. That’s not true, and it seemed like it was worth trying to correct that misperception. So a few of us who work here got together and came up with an algorithm that minimizes the impact of many Googlebombs.
The next natural question to ask is “Why doesn’t Google just edit these search results by hand?” To answer that, you need to know a little bit about how Google works. When we’re faced with a bad search result or a relevance problem, our first instinct is to look for an automatic way to solve the problem instead of trying to fix a particular search by hand. Algorithms are great because they scale well: computers can process lots of data very fast, and robust algorithms often work well in many different languages. That’s what we did in this case, and the extra effort to find a good algorithm helps detect Googlebombs in many different languages. We wouldn’t claim that this change handles every prank that someone has attempted. But if you are aware of other potential Googlebombs, we are happy to hear feedback in our Google Web Search Help Group.

Again, the impact of this new algorithm is very limited in scope and impact, but we hope that the affected queries are more relevant for searchers.

Blah,Blah,Blah… That’s what I gathered from his ramblings. So in short there is really no sure fire way it will not happen again. Let’s just be glad Palin did not win, boy I could see the terms “turkey killer” and “Russia” being the terms of choice for her.