<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SEO Web Design Blog &#187; script</title>
	<atom:link href="http://www.newshoemedia.com/blog/tag/script/feed" rel="self" type="application/rss+xml" />
	<link>http://www.newshoemedia.com/blog</link>
	<description>SEO and Search Engine Friendly Web Design</description>
	<lastBuildDate>Tue, 20 Oct 2009 19:52:29 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>How to 301 Redirect the Non-WWW to WWW</title>
		<link>http://www.newshoemedia.com/blog/seo/301-redirect-non-www-to-www-tutorial</link>
		<comments>http://www.newshoemedia.com/blog/seo/301-redirect-non-www-to-www-tutorial#comments</comments>
		<pubDate>Sat, 03 Jan 2009 23:40:42 +0000</pubDate>
		<dc:creator>Claye Stokes</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[301 redirect]]></category>
		<category><![CDATA[how to redirects]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://www.newshoemedia.com/blog/?p=74</guid>
		<description><![CDATA[Tutorial: Redirecting non-WWW to WWW
I have seen a lot of clients get frustrated quickly after I tell them to set up a 301 Permanent Redirect from the non-WWW version of their website to the WWW version. 
Example: Redirect http://domainname.com to http://www.domainname.com
It is important to note that this method only applies to servers running Apache. Be very careful when [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Tutorial</strong>: Redirecting non-WWW to WWW</p>
<p>I have seen a lot of clients get frustrated quickly after I tell them to set up a 301 Permanent Redirect from the non-WWW version of their website to the WWW version. </p>
<p><em>Example</em>: Redirect <span style="color: #808000;">http://domainname.com</span> to <span style="color: #808000;">http://<strong><span style="color: #800000;">www</span></strong>.domainname.com</span></p>
<p class="highlight">It is <strong>important to note</strong> that this method <em>only</em> applies to servers running Apache. Be very careful when you change the .htaccess file because it can cause your entire site to fail with a simple typo. I recommend hiring an experienced web designer to do this for you.</p>
<p><strong>First</strong>: open your .htaccess file. It should be in the root folder of your website (usually www). If it doesn&#8217;t exist, create a new file named .htaccess &#8211; that is the entire file name, so don&#8217;t add a .txt extension or add anything in front of the period.</p>
<p>Add the following lines  (if there are already some code in the file, add these lines above them):</p>
<ol class="code">
<li><code>RewriteEngine on</code></li>
<li><code>RewriteCond %{HTTP_HOST} ^domainname\.com</code></li>
<li><code>RewriteRule (.*) http://www.domainname.com/$1 [R=301,L]</code></li>
</ol>
<p>REMEMBER: Be <em><strong>extremely</strong><span style="font-style: normal;"> careful, and make sure you know what you are doing. Depending on the structure of your website, adding these lines in the wrong place can break your website. </span></em></p>
<p>I am working on a large post explaining what the .htaccess file is and now to use 301 Permanent Redirects for many reasons &#8211; I will publish it as soon as possible.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.newshoemedia.com/blog/seo/301-redirect-non-www-to-www-tutorial/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
