<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why Writing for search engines will get you nowhere</title>
	<atom:link href="http://seocopyblogger.com/do-not-write-for-search-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://seocopyblogger.com/do-not-write-for-search-engines/</link>
	<description>SEO Copywriting and blogging</description>
	<lastBuildDate>Thu, 29 Sep 2011 11:47:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Cleveland</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-1037</link>
		<dc:creator>Mike Cleveland</dc:creator>
		<pubDate>Tue, 02 Aug 2011 06:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-1037</guid>
		<description>I just believe both can be done. I seen it done. You have to really have something of value that people are looking for. The keyword should follow in line with the main point of you post. 
 
An  example if you were writing about the best washing machine, you keyword have to be about &quot;best washing machine&quot;.  
 
I truly believe the more on point your keyword is to your post, the better sounding your post will be. But, great content still is key to keeping your audience engaged and coming back to your blog. </description>
		<content:encoded><![CDATA[<p>I just believe both can be done. I seen it done. You have to really have something of value that people are looking for. The keyword should follow in line with the main point of you post. </p>
<p>An  example if you were writing about the best washing machine, you keyword have to be about &quot;best washing machine&quot;.  </p>
<p>I truly believe the more on point your keyword is to your post, the better sounding your post will be. But, great content still is key to keeping your audience engaged and coming back to your blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luis</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-686</link>
		<dc:creator>luis</dc:creator>
		<pubDate>Thu, 24 Mar 2011 17:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-686</guid>
		<description>Cool info! Thx 
But i believe there is a way to write for humans an for machines too. Aren&#039;t there are simple rules to follow like writting the most important words in the 100 first words and as well as keywords, and then use them again in the last 100 words? I usally do it and it works! 
 </description>
		<content:encoded><![CDATA[<p>Cool info! Thx<br />
But i believe there is a way to write for humans an for machines too. Aren&#39;t there are simple rules to follow like writting the most important words in the 100 first words and as well as keywords, and then use them again in the last 100 words? I usally do it and it works!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jsa</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-552</link>
		<dc:creator>jsa</dc:creator>
		<pubDate>Fri, 25 Feb 2011 06:23:34 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-552</guid>
		<description>Good point for an article but not for a cv or a linkedin profile</description>
		<content:encoded><![CDATA[<p>Good point for an article but not for a cv or a linkedin profile</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-127</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Tue, 09 Nov 2010 13:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-127</guid>
		<description>Yep - in desperation to leverage their article for search engine friendliness. Unfortunately it becomes unfriendly to readers. </description>
		<content:encoded><![CDATA[<p>Yep &#8211; in desperation to leverage their article for search engine friendliness. Unfortunately it becomes unfriendly to readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-125</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Tue, 09 Nov 2010 09:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-125</guid>
		<description>Yep! I agree. And that in desperation to ranking further in the search engines.</description>
		<content:encoded><![CDATA[<p>Yep! I agree. And that in desperation to ranking further in the search engines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-121</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 09 Nov 2010 05:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-121</guid>
		<description>Great post! Thanks heaps. Many people end up writing terrible content that just makes users leave the site. </description>
		<content:encoded><![CDATA[<p>Great post! Thanks heaps. Many people end up writing terrible content that just makes users leave the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://seocopyblogger.com/do-not-write-for-search-engines/comment-page-1/#comment-102</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Fri, 05 Nov 2010 13:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://seocopyblogger.com/?p=3#comment-102</guid>
		<description>My pleasure Rowe! :) Hope you learned a thing or two from it </description>
		<content:encoded><![CDATA[<p>My pleasure Rowe! <img src='http://seocopyblogger.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Hope you learned a thing or two from it</p>
]]></content:encoded>
	</item>
</channel>
</rss>

