<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Next Generation Problem Article System</title>
	<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html</link>
	<description></description>
	<pubDate>Fri, 25 Jul 2008 08:34:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Lance Winslow</title>
		<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10400</link>
		<pubDate>Fri, 29 Jun 2007 21:47:01 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10400</guid>
					<description>Complexity, drive bureaucracy and decreases efficiency and creates chaos? Is this the beginning of the end? Remember that strength comes from efficiency and simplicity, it is the only reasonable strategy.

I wish the authors would do better to stop the abusiveness saving you time from creating more rules, more complexity and costing you more labor. Chris you have worked too hard along with your team to endure this level of hardship.</description>
		<content:encoded><![CDATA[<p>Complexity, drive bureaucracy and decreases efficiency and creates chaos? Is this the beginning of the end? Remember that strength comes from efficiency and simplicity, it is the only reasonable strategy.</p>
<p>I wish the authors would do better to stop the abusiveness saving you time from creating more rules, more complexity and costing you more labor. Chris you have worked too hard along with your team to endure this level of hardship.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christopher M. Knight</title>
		<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10397</link>
		<pubDate>Fri, 29 Jun 2007 07:13:59 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10397</guid>
					<description>All,

At the moment, we don't plan on releasing a list of all problem status codes or templated emails, but we will continue to release common problems found to help newbie authors avoid common mistakes.

Here are 3 very typical article problems that we would flag an article for:

1) affiliate link violation
2) self serving active link in first sentence
3) author name mis-match with bio box.

Also, popular problems include excessive HTML bloat, keyword abuse, invalid html code or images or javascript included, excess active links, invalid reprint rights conflict, lack of quality content, and we haven't even begun to talk about spelling/grammar or punctuation errors.

&lt;strong&gt;Here's some interesting stats on the 10,052 articles that are in a problem status holding queue today:&lt;/strong&gt;

16.9% of all problems that we flag an article for are because of an excess of self-promotion or the advertising to content ratio is too high.

14.6% are from too much self promotion of a particular product.

That means 31.5% of all problem articles are because the content doesn't meet the basic tenet that the article body must be a GIVE with the resource box being the TAKE, concept.

9.9% are for grammar/spelling and most likely punctuation errors made by ESL authors.

7.6% of all problem articles are for affiliate link violation.

6.6% are press releases wrongly submitted.

6.3% of the time the author name in the by-line does not match the resource box. I can't believe we have 635 articles in this problem status at the moment.

and it goes on....

Keep in mind that when we flag an article as being a PROBLEM, that is a GOOD sign because it means we did not REJECT it completely. When we indicate that an article is a problem, it means that we think there is a chance that the article could be rewritten to become acceptable with a little author effort.</description>
		<content:encoded><![CDATA[<p>All,</p>
<p>At the moment, we don&#8217;t plan on releasing a list of all problem status codes or templated emails, but we will continue to release common problems found to help newbie authors avoid common mistakes.</p>
<p>Here are 3 very typical article problems that we would flag an article for:</p>
<p>1) affiliate link violation<br />
2) self serving active link in first sentence<br />
3) author name mis-match with bio box.</p>
<p>Also, popular problems include excessive HTML bloat, keyword abuse, invalid html code or images or javascript included, excess active links, invalid reprint rights conflict, lack of quality content, and we haven&#8217;t even begun to talk about spelling/grammar or punctuation errors.</p>
<p><strong>Here&#8217;s some interesting stats on the 10,052 articles that are in a problem status holding queue today:</strong></p>
<p>16.9% of all problems that we flag an article for are because of an excess of self-promotion or the advertising to content ratio is too high.</p>
<p>14.6% are from too much self promotion of a particular product.</p>
<p>That means 31.5% of all problem articles are because the content doesn&#8217;t meet the basic tenet that the article body must be a GIVE with the resource box being the TAKE, concept.</p>
<p>9.9% are for grammar/spelling and most likely punctuation errors made by ESL authors.</p>
<p>7.6% of all problem articles are for affiliate link violation.</p>
<p>6.6% are press releases wrongly submitted.</p>
<p>6.3% of the time the author name in the by-line does not match the resource box. I can&#8217;t believe we have 635 articles in this problem status at the moment.</p>
<p>and it goes on&#8230;.</p>
<p>Keep in mind that when we flag an article as being a PROBLEM, that is a GOOD sign because it means we did not REJECT it completely. When we indicate that an article is a problem, it means that we think there is a chance that the article could be rewritten to become acceptable with a little author effort.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan Snyder</title>
		<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10396</link>
		<pubDate>Fri, 29 Jun 2007 04:10:39 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10396</guid>
					<description>Chris, 

Can you please post your list of possible errors because I'm curious. I am trying to imagine how someone could have more than 3 errors in a 300 word article. 

Do you run stats on whether people actually use the preview feature after they input their article copy? 

Maybe after a certain number of consecutive errors you can &quot;suggest&quot; that a writer get more help. Such as the product available in the right-hand column with your picture on it. 

I got a lot of help by taking a course from Jeff Herring. And that was after I read a dozens of articles that are already freely available on this web site.</description>
		<content:encoded><![CDATA[<p>Chris, </p>
<p>Can you please post your list of possible errors because I&#8217;m curious. I am trying to imagine how someone could have more than 3 errors in a 300 word article. </p>
<p>Do you run stats on whether people actually use the preview feature after they input their article copy? </p>
<p>Maybe after a certain number of consecutive errors you can &#8220;suggest&#8221; that a writer get more help. Such as the product available in the right-hand column with your picture on it. </p>
<p>I got a lot of help by taking a course from Jeff Herring. And that was after I read a dozens of articles that are already freely available on this web site.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: austin</title>
		<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10395</link>
		<pubDate>Fri, 29 Jun 2007 01:32:26 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10395</guid>
					<description>Always great stuff Chris! Thx. Do show the problem articles, circle the area that needs attention so we can learn from an example? Or couild you take one of yours and show what would it would look like done incorrectly? Thx</description>
		<content:encoded><![CDATA[<p>Always great stuff Chris! Thx. Do show the problem articles, circle the area that needs attention so we can learn from an example? Or couild you take one of yours and show what would it would look like done incorrectly? Thx<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Murray Johnson</title>
		<link>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10392</link>
		<pubDate>Thu, 28 Jun 2007 20:04:13 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2007/06/next-generation-problem-article-system.html#comment-10392</guid>
					<description>Good for you, Chris. It's about time.</description>
		<content:encoded><![CDATA[<p>Good for you, Chris. It&#8217;s about time.<br />
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
