Google Tightens the Screws on Content Farmers

Just before so-called “content farm” Demand Media went public in January at a $ 1.5-billion valuation, Google said that it was planning to make some changes to its search algorithms to clamp down on the profusion of low-quality results from content farms. Last night, the search giant finally rolled out those changes, and they appear to be a dagger aimed directly at the heart of companies such as Demand, whose stock tumbled on the news. The content company maintains that it won’t be affected by the new algorithm, but it seems clear that Google is upping the ante in the content-farming game.

Google hasn’t specifically said that the changes are aimed at content farmers — in fact, the term doesn’t appear anywhere in its blog post, which simply refers to “low-quality sites” — but Search Engine Land says the rollout is almost certainly aimed in that direction. According to Google, the changes affect about 12 percent of the company’s search results, which is a fairly large proportion for such a change, and an earlier revision last month targeted so-called “scraper” sites, which simply copy content verbatim from other sites. Google’s statement in January said that action would be taken against both scrapers and content farms, so by the process of elimination this algorithm change seems likely to be directed at content farmers.

So why is Google being so coy and not calling these changes an attack on content farms? Perhaps because the whole term “content farm” is problematic — not just in the sense that it is difficult to define, but problematic for Google, since sites like Demand Media run a lot of Google advertising (although the company says this plays no part in whether it cracks down on their results). GigaOM Pro analyst David Card and I looked at the content-farm industry in a recent research note called Content Farms: The Players, the Benefits and the Risks (sub req’d), including the challenges of dealing with Google, and I also discussed the need for Google to take action against content farms in a related paper (sub req’d).

Demand Media — which is adamantly opposed to the term “content farm” — maintains that its content is high quality enough to escape Google’s crackdown. After the search giant announced the coming changes in January, founder and CEO Richard Rosenblatt said that Google’s comments “were not directed at us in any way.” And on the Demand Media blog, it responded to the latest changes by saying that:

As might be expected, a content library as diverse as ours saw some content go up and some go down in Google search results… It’s impossible to speculate how these or any changes made by Google impact any online business in the long term – but at this point in time, we haven’t seen a material net impact on our Content & Media business.

When it comes to the latest changes and their effect on content, the stakes are high for all content-production companies — including Yahoo’s Contributor Network (formerly called Associated Content, which was acquired by Yahoo last year) and other sites such as Suite101 — but they are arguably highest for Demand, which went public based in large part on the value of the content created for its eHow platform and related sites. Among the risks it detailed in the “risk factors” section of its securities filings prior to the IPO was the possibility that Google could make changes to the way it handles and ranks content, and that this could negatively impact the success of eHow.

Now, investors will no doubt be paying close attention to the effect of Google’s changes — and they seem to already be skeptical about Demand’s insistence that this won’t change anything, since the stock dropped by more than 5 percent after the Google news.

Related GigaOM Pro content (sub req’d):

  • Content Farms: The Players, The Benefits, The Risks
  • Demand Media — Search Spam or the Future of Content?
  • Google Needs to Fix Its Spam Problem Even If It Hurts

Post and thumbnail courtesy of Flickr user Armchair Aviator


The exponential data center is here: Juniper Networks


GigaOM