Why big brands should spam search engines!

BMW was removed for web spamming just a few days ago – it were aggressive doorway pages utilizing javascript …

until now I would not have dared to place such sneaky stuff on ANY site I manage or consult for… well BMW did…

And guess what – just some days after "getting outed publicly by some gung-ho blogger" as Greg Boser puts it – (of course Matt Cutts is addressed :-) BMW is back in the index for responding so fast to Google.

Now this big brand managed to get kicked completely out of Google and even went back in faster than it was dropped… I'm seeing all 46k pages of bmw.de already again :-)

That's probably why Greg says that big brands will be allowed to take cuts because search engines want their sites to show up. They want them to show up because their users expect to see them. And those users don’t give a shit about what’s contained in the source code (javascript or cloaking or whatever).

All they care about is whether or not they land on a page that matches their search.


Until that fact changes, there will be virtually no risk associated with aggressive SEO for big brands. And as long as the risks are low, managers of big brands would be foolish not to explore potential strategies that will ultimately improve the visibility of their brands simply because a search engine has said they disapprove.

Yep – kudos to Greg for this insight…

[Post to Twitter]  [Post to Delicious]  [Post to Reddit]  [Post to StumbleUpon] 

What say you?

Want a little more?



MarketingFan is a search marketing and SEO Blog that was started in 2004 and is maintained by Christoph C. Cemper and his team. If this post was interesting for you, then others might be as well!

Keep up to date with our RSS Feeds



rss

Follow Christoph on twitter.com/cemper



If you want to get notified in a timely fashion about updates of Marketingfan then signup for the Blog Newsletter



Get site updates via e-mail
Mail:
What:


Please enter your (first)name in the form above. Of course we respect your Privacy

Or contact us here ....