Beware if Your Site is Overly SEO’ed

by YC Ng on March 17, 2012

If your are aggressively doing SEO, your need to take note of this…

Head of Google’s Webspam team, Matt Cutts, announced during Q&A panel at SXSW that Google is releasing an algorithm update specifically to target websites over doing their SEO.

What about the people optimizing really hard and doing a lot of SEO. We don’t normally pre-announce changes but there is something we are working in the last few months and hope to release it in the next months or few weeks. We are trying to level the playing field a bit. All those people doing, for lack of a better word, over optimization or overly SEO – versus those making great content and great site. We are trying to make GoogleBot smarter, make our relevance better, and we are also looking for those who abuse it, like too many keywords on a page, or exchange way too many links or go well beyond what you normally expect. We have several engineers on my team working on this right now.

In fact, Google has started penalizing websites that overly optimized with identical keywords in inbound links. We have observed some changes of Google SERPs these few weeks, but Google denied any new update at the moment. Perhaps, there are still in tweaking their algo. Anyway, there are lot of active discussions at forums and marketeers have started calling it as “Google Panda v3.3″. If you’re caught, your website will be slapped with a -10, -50, -100 & etc rankings penalty or even banned for a more serious case.

Does it mean that you should stop doing SEO? NO.

It is just that Google doesn’t like webmaster to artificially influence or manipulate their SERPs. We need to be smart in SEO our site to prevent over-optimization in the eye of Google.

Naturalization is the key!

In SearchGuru, we practice only safe SEO method for sustainable ranking. We only build high quality backlinks directly to our client sites and have different layers of backlinks to safeguard and boost strength.

Leave a Comment

Previous post:

Next post: