"Problem: Your article body does not fulfill the promise made in the article title" Anyone else keep getting these for absolutely no reason? For the past two or so weeks I've been getting articles rejected for that reason. I submitted a few 600-700 word articles, which in detail fulfil the promise made in the title. Still, they keep getting rejected, while some other 250 work articles I've written get accepted, despite their worse quality. Seems like EZA's editorial team reject/accept articles randomly. Anyone else noticed this?
It usually happens when you use "How to" in your article title. If you use "how to do ..." in the title you need to give an exact answer "how to" do it in the article. To avoid having an article rejected for this reason I ussualy write "tips and tricks on how to..." or "advice on how to...". This way you can avoid having to give an exact answer. I dont know if this makes any sense Hope you get it.
I think they've taken on some new editorial staff recently, and according to various reports there do seem to be some inconsistencies at the moment. I admit I haven't had a rejection myself, but I know my way round their editiorial guidelines pretty well and always keep one eye on their blog, where policy changes and interpretations are always clarified. I think Tibor probably makes a very good point in the post above.
They've been getting on my nerves lately with inconsistencies. I guess each individual editor has his/her nitpicks. Awhile back I had three articles rejected for "general errors"; they were all proofread and passed Copyscape. I followed all of the guidelines. I sent a message asking why and never got a response. These past couple of months I've had better luck with getting approvals from Constant Content, and they're known to be really strict compared to EZA!
Whenever I see the words "EZA" and "Copyscape" in the same post, I sense a story that's ultimately not going to have a happy ending. Editorial policies are changing rapidly at EZA. Understandably and rightly (in my opinion) they don't want "derivative content" (their words, from their blog).