Was the Penguin 2.0 the Biggest Storm in a Teacup in SEO circles yet?
Search Engine Optimisation

Was the Penguin 2.0 the Biggest Storm in a Teacup in SEO circles yet?

27th May 2013

As we all know Penguin 2.0 rolled out last week and it seems to be a remarkably underwhelming update for one with so much hype. Searchmetrics has a great roundup of the winners and losers with the main losers being:

DomainClusterSEO Visibility CurrentDiffin %














ets.orgbusiness /edu28496-14575








The common denominators seem to be thin sites, sites with thin links and sites with predominantly untrusted links.

Penguin 2.0 was possibly the most “pre-launch hyped” update that sparked a great deal of debate about what types of techniques would be hit. Most of them don’t seem to be affected but it may still be early days.

A lot of the Penguin 2.0 predictions seem to be way off:

  1. Guest posting was predicted to be hit a great deal and that hasn’t seemed to happen. I am however betting this is coming, it’s too abused not to be imo.
  2. Anchor text hasn’t seem to be hit a great deal either although there are a few rumblings that certain sites have.
  3. Paid links were also cited in some circles and there are too many examples of sites with blatantly paid for links ranking well post Penguin 2.0 for this to have been dealt with.

So was Penguin 2.0 the biggest storm in the SEO teacup to date?

I feel it is but I also feel it’s probably a tech upgrade that possibly allows Google to widen its net for future penguin updates. First signs show that the Penguin 2 suite seems a bit of a damp squib but I feel more is to come.

What are the biggest areas of link building you feel should have been addressed in Penguin 2.0?

Written By
Louis Venter is the founding director and CEO of MediaVision, a Search Engine Marketing (SEM) company specialising in all areas of search. His particular interests are organic search marketing, paid search marketing, conversion strategy and online PR.
  • This field is for validation purposes and should be left unchanged.