<?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: Can PR driven SEO save search engines, or will marketing SEO kill blog search engines</title>
	<atom:link href="http://www.fortexgroup.com/blog/2006/01/04/can-pr-driven-seo-save-search-engines-or-will-marketing-seo-kill-blog-search-engines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fortexgroup.com/blog/2006/01/04/can-pr-driven-seo-save-search-engines-or-will-marketing-seo-kill-blog-search-engines/</link>
	<description>C-Level PR Counsel</description>
	<lastBuildDate>Thu, 12 Nov 2009 15:52:17 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: B2B Insight Blog &#187; The human brain on a search engine vs. a content site</title>
		<link>http://www.fortexgroup.com/blog/2006/01/04/can-pr-driven-seo-save-search-engines-or-will-marketing-seo-kill-blog-search-engines/comment-page-1/#comment-111</link>
		<dc:creator>B2B Insight Blog &#187; The human brain on a search engine vs. a content site</dc:creator>
		<pubDate>Wed, 08 Mar 2006 15:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://b2binsight.com/blog/?p=11#comment-111</guid>
		<description>[...] Once again, I&#8217;ll return to the rationale for always having a strong search engine PR strategyÂ - it is far easier to meet the people as they look for your information, then to have to search them out and redirect their focus. [...]</description>
		<content:encoded><![CDATA[<p>[...] Once again, I&#8217;ll return to the rationale for always having a strong search engine PR strategyÂ - it is far easier to meet the people as they look for your information, then to have to search them out and redirect their focus. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
