New Feature Code-Named Rake

I love it when our team whips out new features and today’s newest feature is an improvement to the EzineArticles new article email alerts service:

Later this morning when the 435 new article alerts get delivered as usual, at the bottom of the listing of new articles will be the top 20 articles that were added in each category (1) year ago today. If there weren’t 20 new articles added a year ago today for each category, then it’ll serve up whatever number was added a year ago today.

What is “Rake”? The idea is to leverage the 20 links in an ezine principle that states that ezines with 20 links or more get more click throughs than ezines without 20 links while delivering our subscribers with access to articles they most likely have never seen before. TV shows do it all the time, it’s called a re-run. :) If you’ve never seen the article before, it’s new to you.

In addition, we’ve added a rule on this that I call “Clean Rake” because we’re auto-generating last years top up to 20 articles based on the category they are in right now rather than the category they were in when originally approved. I don’t know if you’ve noticed, but many of our newbie editors don’t always get the category right the first time and within 6-72 hours or so after an article is approved the first time, our QC team will catch it and re-classify the article appropriately. That means in a year from now when today’s newest articles get promoted a 2nd time (assumes this new feature is a success), they’ll be promoted in the correct category.



Nicely done EzineArticles team!

So now you are using re-runs in a positive way! I love it when we can use strategies from other businesses in our own.

Just don’t adopt the Disney policy of “retiring” a classic movie only to re-release it later!

Catch you soon!


Comment provided September 21, 2007 at 12:19 PM



Hi Chris!

Why are the articles published in a wrong category?
Doesn’t the E.Articles’ editor see that an author didn’t choose the correct category from the beginning?

Comment provided September 21, 2007 at 12:42 PM



Editor inexperience is the cause.

They are required to know all 435 categories along with what should and shouldn’t be accepted in each. It takes them 6+ weeks to begin to get it right.

Comment provided September 21, 2007 at 12:47 PM



We have to do something about that!

Why don’t you have only old editors checking for the article’s meaning and choosing the correct category?
New editors would check only spelling, grammar and synthesis.

Comment provided September 21, 2007 at 2:44 PM



This is a great new feature that will again set you apart from others. Giving new life to seasoned articles is good for everyone.

Comment provided September 21, 2007 at 3:53 PM



I had to do 1000 things after arriving home, so I couldn’t really think about your problem before. I just wanted to send you an answer without delay because you answered my question.

Now I’m thinking!

Are you serious? Do you teach each editor Everything??
This is a waste of time and energy. You have to work as if the Ezine was a factory.
Each editor has to do only one part of the work. People work faster and better doing only one thing.

So, you shall have a group of editors A, formed with the old editors that know very well the Ezine’s categories and which articles are decent for the Ezine, etc. that will be responsible for the main verification.

They will be the first ones to read the article and see if it is ok, if it has meaning and if the author chose the correct category. If an article won’t pass from verification 1 there is no meaning on checking for grammar, spelling, etc.
It is rejected from the beginning by the experts.

Then you shall have a group of editors that will check the rest: spelling, grammar and synthesis while each article will be already approved by the experienced editors and in the right category.

This way you only have to prepare new editors for the group B.
Editors on group B shall start learning all the categories while they are looking for writing mistakes but they are not responsible for anything.
They are the future editors A.

Comment provided September 21, 2007 at 4:35 PM


Programmer #1 writes:

Christina Sponias,

Being I created much of the content management system, I feel I need to respond here…

The editors are already split into specific tasks broken down into chunks, based on experience. But the basis of how they are spread around can be very complex, and is based on a system of logic that has proven to be effective and refined over time.

From a technical aspect of things, to have people be doing things as specific as just checking category’s, would be very difficult & inefficient to implement It would result in adding an extra step making the articles take twice as long to be approved.

Let me explain,

A quick peak behind the scenes.. I had to come up with a way for teams of editors to be able to approve thousands of articles per day and keep everything ‘in sync’. You don’t want two editors working on the same thing at the same time for example.

So it works on a batch queuing system. An editor gets a ‘batch’ of articles at a time, reserved for them. The order of the articles they receive is different depending on the experience of the editor, and various priority’s that can be set per individual person, depending on the state of the existing articles in the system.

(remember you are dealing with thousands of submits per day that go to around a dozen or so editors. And an article can be in a number of different status’s, such as a new submit, or existing articles that where edited now waiting to be re approved, on top of being prioritized by member status, and age of the current articles sitting in the primary approval pool, ect, this is a very complex system to maintain!)

New editors will generally start out only getting basics, while the experienced editors will get plats first, or might be assigned for things like re-approvals, etc, etc. So you must envision, the articles as being in separate waiting pools at any given time. A primary pool of articles waiting to be approved, or re-approved, and smaller pools assigned for each editor.

To have articles go to first pools designated to grammar.. then back into the main pool again, now waiting to go to designated category people, the article has now hopped from

main pool-> grammar editor etc -> main pool -> category select people -> finally approved

.. which means it would often take perhaps twice as long for the article to reach a final approval.

Comment provided September 21, 2007 at 9:06 PM


Catalin writes:

Chris, the waiting period 4 weeks is resonable for approving an article. I know what does it require this job as currently working as an editor. I can do this job for you too.

Comment provided September 22, 2007 at 3:09 AM



Hi Programmer 1!

I know that while working we face several problems that our theories cannot predict.

My idea was to have expert editors checking first of all each article. So, they have to start from the final approval.
They will see that the article has spelling and grammar mistakes and is somehow confusing, but it can be improved. The content is good and there is a message. So they approve it and select their category if they don’t agree with the category the author chose. If they don’t know if an article will be good after the improvement, it shall go to the ‚¬“I don’t know‚¬ file.

The articles go to other editors not so experienced for grammar, spelling and organization and as soon as these mistakes are corrected the articles are directly approved without going back to the final approval team.

The problematic articles go back to the expert editors that already read them and know which their mistakes were.
They check them again after the corrections. If the articles are ok they are approved, if not they are rejected.

A new editor shall never be responsible for the article’s category, since he or she doesn’t know well all the categories.

Anyhow, this is my opinion.
You can save time and energy if the most important part of the verification is done from the beginning by expert editors and all the rest by new editors.

Have a nice weekend!


Comment provided September 22, 2007 at 8:27 AM




4 weeks is never acceptable ever to wait for an article approval/review… Under 7-10 days should be the worst case scenerio, depending on load.

Thanks for your offer to assist. Sorry, we only hire editors who work locally in our office.

Comment provided September 22, 2007 at 3:16 PM



Hi Cris,

You rightly said, ” …Under 7-10 days should be the worst case scenerio…”

Everytime I have submitted my articles, I was nervous what would happen to them.

But your editorial team is very effective. Before I submit I check number issues.

Once it is approved by Ezine, I am submitting a few others. A couple of months ago 15 (fifteen) of my articles appeared in the

My thanks to Ezine for the tirless task of helping to spread quality information to the world.


Comment provided September 24, 2007 at 11:08 PM



Hi Friends,

I had a e-mail inquiry about my previous post.

My articles appeared in the



Comment provided September 29, 2007 at 9:28 AM


RSS feed for comments on this post.

Leave a comment

Please read our comment policy before commenting.