<?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: SEO Means Optimize For Users</title>
	<atom:link href="http://www.ItsTheROI.com/search-engine-marketing/seo-means-optimize-for-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ItsTheROI.com/search-engine-marketing/seo-means-optimize-for-users/</link>
	<description>San Francisco Search Engine Optimization Company</description>
	<lastBuildDate>Fri, 04 Jun 2010 05:06:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: randfish</title>
		<link>http://www.ItsTheROI.com/search-engine-marketing/seo-means-optimize-for-users/comment-page-1/#comment-14573</link>
		<dc:creator>randfish</dc:creator>
		<pubDate>Wed, 30 Sep 2009 20:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://ItsTheROI.com/?p=322#comment-14573</guid>
		<description>Jonah - I think you really misread the intent and focus of the post. It was not &quot;don&#039;t design for users&quot; or &quot;don&#039;t focus on users&quot; at all - that would be terrible advice.  Note my update to the post:

&quot;A lot of folks in the comments are under the impression that I&#039;m recommending against building for users - nothing could be further from the truth. Websites are made for people, and users should absolutely be the focus of your efforts. My argument in this post centers specifically around the practice of search engine optimization and the idea that tactics which are engine-focused (like XML sitemaps, anchor text, link architecture, webmaster tools usage, etc.) can be ignored because they&#039;re not &quot;for the user.&quot; The charts and points above are intended to illustrate that if you only focus on &quot;user-targeted SEO&quot; you&#039;re missing a huge chunk of the potential SEO opportunity pie.&quot;

I think we&#039;re on exactly the same page - your points at the end of your post -

SEO involves a lot of tactics that are specifically for the engines nor do I embrace the Google party line that says “make content for users, not for engines”. SEO is a multi-faceted discipline and I completely concur that these factors cannot be ignored.

- are exactly what I was trying to say with the blog. I&#039;m sorry if that wasn&#039;t clearer.</description>
		<content:encoded><![CDATA[<p>Jonah &#8211; I think you really misread the intent and focus of the post. It was not &#8220;don&#8217;t design for users&#8221; or &#8220;don&#8217;t focus on users&#8221; at all &#8211; that would be terrible advice.  Note my update to the post:</p>
<p>&#8220;A lot of folks in the comments are under the impression that I&#8217;m recommending against building for users &#8211; nothing could be further from the truth. Websites are made for people, and users should absolutely be the focus of your efforts. My argument in this post centers specifically around the practice of search engine optimization and the idea that tactics which are engine-focused (like XML sitemaps, anchor text, link architecture, webmaster tools usage, etc.) can be ignored because they&#8217;re not &#8220;for the user.&#8221; The charts and points above are intended to illustrate that if you only focus on &#8220;user-targeted SEO&#8221; you&#8217;re missing a huge chunk of the potential SEO opportunity pie.&#8221;</p>
<p>I think we&#8217;re on exactly the same page &#8211; your points at the end of your post -</p>
<p>SEO involves a lot of tactics that are specifically for the engines nor do I embrace the Google party line that says “make content for users, not for engines”. SEO is a multi-faceted discipline and I completely concur that these factors cannot be ignored.</p>
<p>- are exactly what I was trying to say with the blog. I&#8217;m sorry if that wasn&#8217;t clearer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
