<?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: Vanity in Your Address Bar &#8211; WWW or no-WWW</title>
	<atom:link href="http://www.westwardstrategy.com/blog/2008/www-subdomain-vs-seo-concerns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.westwardstrategy.com/blog/2008/www-subdomain-vs-seo-concerns/</link>
	<description>Information on Natural Search Optimization, Web Design, Web Site Maintenance, Internet Marketing &#38; SEO from a Reno Nevada marketing company</description>
	<lastBuildDate>Thu, 20 Oct 2011 21:08:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Reviewing SEO &#38; Web Related Topics from the Past &#124; Reno SEO, Web Design &#38; Internet Marketing Blog</title>
		<link>http://www.westwardstrategy.com/blog/2008/www-subdomain-vs-seo-concerns/comment-page-1/#comment-95</link>
		<dc:creator>Reviewing SEO &#38; Web Related Topics from the Past &#124; Reno SEO, Web Design &#38; Internet Marketing Blog</dc:creator>
		<pubDate>Tue, 29 Apr 2008 21:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.westwardstrategy.com/blog/2008/vanity-in-your-address-bar-www-or-no-www/#comment-95</guid>
		<description>[...] How 3 Lines of Code Can Improve Your Rankings&#160;&#160;&#160;&#160; Our Post from February 20, 2008 - Vanity in Your Address Bar - WWW or no-WWW [...]</description>
		<content:encoded><![CDATA[<p>[...] How 3 Lines of Code Can Improve Your Rankings&nbsp;&nbsp;&nbsp;&nbsp; Our Post from February 20, 2008 &#8211; Vanity in Your Address Bar &#8211; WWW or no-WWW [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.westwardstrategy.com/blog/2008/www-subdomain-vs-seo-concerns/comment-page-1/#comment-76</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 25 Feb 2008 17:46:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.westwardstrategy.com/blog/2008/vanity-in-your-address-bar-www-or-no-www/#comment-76</guid>
		<description>I have to disagree with the 404 part of your answer. 
You never have control over what a user might do. You also do not have control over how other websites might link to yours. There may not be a reason for anyone to type it in, but that will not stop some people from doing it.

If they are searching for the default content you should direct them to the default content, not a 404 page. It just makes for better usability.</description>
		<content:encoded><![CDATA[<p>I have to disagree with the 404 part of your answer.<br />
You never have control over what a user might do. You also do not have control over how other websites might link to yours. There may not be a reason for anyone to type it in, but that will not stop some people from doing it.</p>
<p>If they are searching for the default content you should direct them to the default content, not a 404 page. It just makes for better usability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Annesley</title>
		<link>http://www.westwardstrategy.com/blog/2008/www-subdomain-vs-seo-concerns/comment-page-1/#comment-75</link>
		<dc:creator>Paul Annesley</dc:creator>
		<pubDate>Thu, 21 Feb 2008 22:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.westwardstrategy.com/blog/2008/vanity-in-your-address-bar-www-or-no-www/#comment-75</guid>
		<description>Regardless of whether you include the trailing slash on a domain when linking or typing it into your browser, the first line of the HTTP request will be &#039;GET / HTTP/1.1&#039;.  So there&#039;s really only four, not six, different URLs that search engines etc will see.  Of course, that&#039;s still three too many, and the web server should certainly normalize them to a single canonical URL.

In my opinion, the add/remove www prefix should be handled by a 301 permanent redirect, and a request to e.g. /index.html instead of / should be a 404.

Some people would argue with the second point (404), but really there&#039;s no reason fo anybody to type it in, and even if they tried, there&#039;s a myriad of possible &quot;defaults&quot; like index.html, index.htm, default.htm, index.php, index.asp etc.  If most of them will produce a 404, then you may as well make all of them the same.</description>
		<content:encoded><![CDATA[<p>Regardless of whether you include the trailing slash on a domain when linking or typing it into your browser, the first line of the HTTP request will be &#8216;GET / HTTP/1.1&#8242;.  So there&#8217;s really only four, not six, different URLs that search engines etc will see.  Of course, that&#8217;s still three too many, and the web server should certainly normalize them to a single canonical URL.</p>
<p>In my opinion, the add/remove www prefix should be handled by a 301 permanent redirect, and a request to e.g. /index.html instead of / should be a 404.</p>
<p>Some people would argue with the second point (404), but really there&#8217;s no reason fo anybody to type it in, and even if they tried, there&#8217;s a myriad of possible &#8220;defaults&#8221; like index.html, index.htm, default.htm, index.php, index.asp etc.  If most of them will produce a 404, then you may as well make all of them the same.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

