Read WebProNews
With Friends!

EzineArticles Hit By Google Panda Update Again

Quality adjustments apparently not enough so far

Get the WebProNews Newsletter!
Top Rated White Papers and Resources
There are 7 Comments. Add Yours.
  1. What I don’t understand is how come spam websites have come out to the top after the panda update.

  2. @Marie,

    What I think about why spam websites have come out to the top after this update is that, the update itself is on the level of tweaking existing conditions on the algorithm and adding some more for extra filter, and is away from human intervention, like actual human reviewing each of the sites in the ranks. Given that, we can assume that those spam websites have, in a way, satisfied the conditions and escaped the filter, making them appear at the top.

    Let me just add that I have good experience with quality content and that those low-quality contents won’t endure forever as people that would notice them on the ranks have the choice to report them as spam, which I think why Google laid out the domain-blocking feature.

  3. EzineArticles has been slapped hard just like the web directories which were slapped 3 years back by Google. Do know what is the end of Google?

  4. Was EzineArticles the only site to get hit a second time around? I’d like to know if other sites, big and small, that got swept up in the Panda update the first time around took a second hit. And how did porn sites come out on top?

  5. The update helped FeelFree.co.. traffic is like +500% after the update.. Thanks to uncle Google

  6. so this is why then,in past when we search for articles ezine appears at first page.now its gone!i dont think Ezine spames,its really hard to post a low quality article at Ezine

What do you think? Respond.

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>