Last Sunday I got myself hooked into reading a blog post by Ken Evoy of Site Build It that was titled Proof That Google Has No True Googlebomb Algorithm. I have to say that I knew nothing about Ken Evoy other than being the top guy there, and I didn’t even know he had a blog until this post. After reading the post… my head hurt.
I have kept the post for a while now because I wanted to read it again. The first time I read it I actually knew overall what he was talking about. But it’s quite a long post, so much so that I’m going to tell most of you that if you’re not into technology and a lot of that kind of talk don’t even bother checking it out. I’m going to touch on some of this though, because it’s interesting stuff.
What the Site Build It folks were able to do was prove that the Google system could be gamed. They have all sorts of documentation from someone who made it their goal of showing just how they could fool Google and get to the top of the rankings right under Google’s nose, even telling people what was coming. Site Build It tried to tell Google what was happening and, instead of addressing it, pretty much ignored it.
I say “pretty much ignored” because there were a series of form letters Google sent to Ken, and apparently Ken didn’t like that. At one point Google seemed to tell them they were going to do something really positive, but then didn’t do a thing.
Let me step back for a quick moment, if I may. A “googlebomb” is usually where a bunch of people get together and create a ton of links to something to skew search results so they’ll take you to a specific page for a search term, whether they’ve earned it or not. The most famous google bomb (you can write it as either one or two words) was when you’d put in “miserable failure” and George Bush’s name came up; so wrong! lol
Another google bomb was perpetrated by John Chow when he was able to get something like 85,000 people to keep linking to his name to drive him up to the top in Google’s search engines and in page rank. At least at that time Google hated it so much they delisted his site (that’s bad), but for whatever reason it didn’t end up reducing his visitors, and he still made a ton of cash online. He’s now back on Google after a 3-year absence with a page rank and listing after they kissed and made up (pays to have a direct connection to Matt Cutts; but I digress…).
Anyway, what it’s all boiling down to is, in his own way, Ken is going for his own google bomb, though he wouldn’t call it that. He’s trying to rally the troops, who would be us, to support his cause by going to this link and joining him in kind of a protest. He’s also declared that he won’t write another thing on his blog until Google fixes this algorithm.
I have some takes on this; otherwise, why would I have written this much?
One, Ken has a pony in this race which slightly colors his anger here. Seems there were some folks who google bombed his company with negative reviews, not because they didn’t like him or the company but because they wanted to prove they could do it. That doesn’t sit well with him.
Two, I can’t understand how not writing any posts on his blog will help push his cause. To me, if I had a gripe about something I’d want to write almost every day about it, or at least often. Who does him not writing on his blog anymore help? Google won’t care, people reading his blog that agree or disagree with him won’t go back because they’ll have no idea how long his boycott is, and thus his message will get lost.
Three, I’m not sure all that many people will get enthused enough to join a movement to get Google to take care of this problem of google bombs. I mean, Google did take away the page rank from this blog for a little while, but my posts were still showing up on Google, sometimes in the top spot for certain terms (you want to see something neat?
I could say more, but I think that’s enough for the moment. I guess I’ll just put the question out there and ask who’s angry enough at Google to even think about joining a movement against them? Actually, I hope you go check out what he wrote, but be warned, it’s almost 5,800 words. Good thing I speed read! 😉