<?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: 301 Redirects: Only One Home Page Please</title>
	<atom:link href="http://www.appliedseo.com/archives/seo-tech-only-one-home-page-please/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appliedseo.com/archives/seo-tech-only-one-home-page-please/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Mon, 01 Dec 2008 18:57:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: John Carcutt</title>
		<link>http://www.appliedseo.com/archives/seo-tech-only-one-home-page-please/#comment-74</link>
		<dc:creator>John Carcutt</dc:creator>
		<pubDate>Thu, 20 Apr 2006 00:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.appliedseo.com/?p=6#comment-74</guid>
		<description>Hi pirco, 

That is a very good question and you answered it yourself. :) Consistency is the key. However, keep in mind that you don’t always have control over how other sites link to yours so implementing the 301 redirect is still a must. www. is just another sub domain, it just happens to be the standard default. When you do www.subdomain.domain.com, what you are really doing is sub-subdomain.subdomain.domain.com.

The 301 redirect in this case is all about preventing the indexing of duplicate pages by allowing multiple URLs to display the same content; no matter what the URL or sub sub domain.</description>
		<content:encoded><![CDATA[<p>Hi pirco, </p>
<p>That is a very good question and you answered it yourself. <img src='http://www.appliedseo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Consistency is the key. However, keep in mind that you don’t always have control over how other sites link to yours so implementing the 301 redirect is still a must. <a href="http://www" rel="nofollow">http://www</a>. is just another sub domain, it just happens to be the standard default. When you do <a href="http://www.subdomain.domain.com" rel="nofollow">http://www.subdomain.domain.com</a>, what you are really doing is sub-subdomain.subdomain.domain.com.</p>
<p>The 301 redirect in this case is all about preventing the indexing of duplicate pages by allowing multiple URLs to display the same content; no matter what the URL or sub sub domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pirco</title>
		<link>http://www.appliedseo.com/archives/seo-tech-only-one-home-page-please/#comment-73</link>
		<dc:creator>pirco</dc:creator>
		<pubDate>Wed, 19 Apr 2006 23:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.appliedseo.com/?p=6#comment-73</guid>
		<description>good info! thanks.

how about sub domains? i have a client who insists on using "www" on all their web sites, even if it's a subdomain. so far, i just recommended using both but after reading your article, i'll make sure that we are consistent. is there any argument against using www.subdomain.domain.com?</description>
		<content:encoded><![CDATA[<p>good info! thanks.</p>
<p>how about sub domains? i have a client who insists on using &#8220;www&#8221; on all their web sites, even if it&#8217;s a subdomain. so far, i just recommended using both but after reading your article, i&#8217;ll make sure that we are consistent. is there any argument against using <a href="http://www.subdomain.domain.com?" rel="nofollow">http://www.subdomain.domain.com?</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
