The End of Derivative Content
In the blogosphere they call regurgitated/recycled content made primarily from a derivative of other works as “blogoreaha”. I suppose we could call it “articleareeha” but I prefer to call it “article vomit.”
You know what I’m talking about as it’s very easy to spot this type of content. Usually the author is so embarrassed that they won’t even put their real name on the article or they won’t include their name in the resource box or the landing page that the URL in the resource goes to.
One of the foundations of the success of EzineArticles (besides its’ its highly successful, intelligent and attractive expert authors (nice suck up, eh?)) is our ability to detect in real-time exact duplicate and duplicative article submissions and then use that algorithm to either tag the content as suspect to be further processed or hard reject it before our 2 human editors even see it.
We call it CASM (Content Association Sequence Matching) and this has been 3+ years in development behind-the-scenes.
Over a million articles have been processed by the proprietary EzineArticles CASM system and this allows us to know many distinctions about every article that our members submit and about the pattern of various accounts…including (but not limited to):
- Article content submitted is infringing on itself (meaning the author is rewriting his or her own works by way of rearrangement (not cool))
- Article content duplicates in part or whole on other alternative authors within an account
- Article content duplicates in part or whole against another author’s account (whether their articles are live or not)
- Article content duplicates in part or whole against other articles that have been since deleted or rejected.
- Lots of data about the date history of the duplicated or duplicative content… ie: Article content submitted a bunch of times by various members is a clue we use.
It’s not a perfect system, but we’ve had years of refinement to improve our ability to prevent false positives. There’s quite a bit more to the above list that I can’t share… including how we vary the shield frequency harmonics to prevent enemy ships from beaming non-unique content through our shield.
CASM was originally created to defend against PLR (Private Label Rights) non-exclusive rights content being submitted, but it also proved further useful to defend against plagiarism…something we have a zero tolerance for.
Millions of weekly EzineArticles visitors do not want to see duplicate or duplicative content and we’ve bent over backwards to keep it out of the site.
Read This Tip A Few Times Please: The absolute best way to beat duplicate content filters is to create unique article content in the first place!
IMPORTANT: We recognize that some authors submit duplicate content by innocent accident. This system is not designed to scold or punish you if you submit duplicate content, but rather to give you another tool to help identify if you’ve submitted the same content in the past.
If you have more ideas for how we could improve our ability to keep duplicative content out that we haven’t already thought of, we’d love to hear it.
Hi, Chris,
While I recognize the editorial need to keep pushing forward with new ideas and new approaches to content development, as a copywriter who cranks out the content you dismiss so easily, I feel you’ve missed some critical considerations.
1. There’s only so much you can say about SEO/M and conversion ratios so you have to slice the baloney pretty thin. It ain’t brain surgery. It’s marketing.
2. Just because a post appears on your blog or SEOmoz or some other web-related blog doesn’t mean it can’t be rewritten to be read by another couple thousand folks on another blog.
3. You know the web gobbles content like taco chips and sites want content. If the check clears, I’ll write it (as long as it isn’t personally offensive, i.e., hate speech.)
While your sentiments are noble and on target, take it from someone slogging through the blog meat. We’re just out here “singing for nickels and dimes.”
Thanks for the post.
Paul Lalley
editor@webwordslinger.com
[Reply]