<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: When Should You NOT Approve A Trackback Comment?</title>
	<atom:link href="http://www.blogcontentprovider.com/blog/2008/06/04/when-should-you-not-approve-a-trackback-comment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogcontentprovider.com/blog/2008/06/04/when-should-you-not-approve-a-trackback-comment/</link>
	<description>Professional Blog Management</description>
	<pubDate>Fri, 09 Jan 2009 01:23:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Allen</title>
		<link>http://www.blogcontentprovider.com/blog/2008/06/04/when-should-you-not-approve-a-trackback-comment/#comment-1118</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Wed, 20 Aug 2008 16:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogcontentprovider.com/blog/?p=190#comment-1118</guid>
		<description>I approved the above spam comment as an example of the type of comment I am talking about. These kinds of comments are obviously spam. Here's why:

&lt;ol&gt;&lt;li&gt;Thanks to the article - Bad grammar. Probably written by an Indian or third-world writer the company hired to ghostwrite comments like this dirt cheap.&lt;/li&gt;
&lt;li&gt;The comment doesn't say anything meaningful. It's just plain fluff&lt;/li&gt;
&lt;li&gt;I am incorporating what your wrote to our project! - Nice try, but I'm not buying it. Instead of taking my suggestion as a positive, this commentator is attempting to say something of value while being guilty of the very thing I'm cautioning against. Bad policy.&lt;/li&gt;
&lt;li&gt;Not relevant to our topic - This one is negotiable. Since our blog is targeting companies in a variety of industries regarding blogging services, we don't expect every commentator to be other bloggers and Internet marketers. The comments should come from people in many industries. But that isn't true of all blogs. If your blog is targeted toward a specific niche audience and you get comments from outside of that niche then you should scrutinize the comment. It may be a legitimate comment, but it does deserve scrutiny simply for being out of the ordinary.&lt;/li&gt;&lt;/ol&gt;

This particular commentator was trying to game us by writing fluff and getting traffic to their site. They may be even trying to get a backlink, but because their backlink is coming from a non-relevant site to their own, it won't help them much. Nevertheless, I hope the above comment illustrates well the type of comment you should reject.</description>
		<content:encoded><![CDATA[<p>I approved the above spam comment as an example of the type of comment I am talking about. These kinds of comments are obviously spam. Here&#8217;s why:</p>
<ol>
<li>Thanks to the article - Bad grammar. Probably written by an Indian or third-world writer the company hired to ghostwrite comments like this dirt cheap.</li>
<li>The comment doesn&#8217;t say anything meaningful. It&#8217;s just plain fluff</li>
<li>I am incorporating what your wrote to our project! - Nice try, but I&#8217;m not buying it. Instead of taking my suggestion as a positive, this commentator is attempting to say something of value while being guilty of the very thing I&#8217;m cautioning against. Bad policy.</li>
<li>Not relevant to our topic - This one is negotiable. Since our blog is targeting companies in a variety of industries regarding blogging services, we don&#8217;t expect every commentator to be other bloggers and Internet marketers. The comments should come from people in many industries. But that isn&#8217;t true of all blogs. If your blog is targeted toward a specific niche audience and you get comments from outside of that niche then you should scrutinize the comment. It may be a legitimate comment, but it does deserve scrutiny simply for being out of the ordinary.</li>
</ol>
<p>This particular commentator was trying to game us by writing fluff and getting traffic to their site. They may be even trying to get a backlink, but because their backlink is coming from a non-relevant site to their own, it won&#8217;t help them much. Nevertheless, I hope the above comment illustrates well the type of comment you should reject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Texas Medical</title>
		<link>http://www.blogcontentprovider.com/blog/2008/06/04/when-should-you-not-approve-a-trackback-comment/#comment-1117</link>
		<dc:creator>Texas Medical</dc:creator>
		<pubDate>Wed, 20 Aug 2008 03:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogcontentprovider.com/blog/?p=190#comment-1117</guid>
		<description>Thanks to the article, Now there is more reason to comment than ever before! Everyone should participate. I am incorporating what your wrote to our project!</description>
		<content:encoded><![CDATA[<p>Thanks to the article, Now there is more reason to comment than ever before! Everyone should participate. I am incorporating what your wrote to our project!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
