<?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>I Love Usability &#187; www</title>
	<atom:link href="http://iloveusability.com/tag/www/feed/" rel="self" type="application/rss+xml" />
	<link>http://iloveusability.com</link>
	<description>Reviews &#38; articles about rock-solid usability and stunning user experiences.</description>
	<lastBuildDate>Sat, 14 Nov 2009 23:14:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The www Problem</title>
		<link>http://iloveusability.com/usability-tip/www-problem/</link>
		<comments>http://iloveusability.com/usability-tip/www-problem/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 14:00:38 +0000</pubDate>
		<dc:creator>Kevin</dc:creator>
				<category><![CDATA[Usability Tip]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[www]]></category>

		<guid isPermaLink="false">http://iloveusability.com/?p=120</guid>
		<description><![CDATA[To <code>www</code> or not to <code>www</code>: that is the question.]]></description>
			<content:encoded><![CDATA[<p>When visitors type in your site&#8217;s URL, they have many different options. Do they add the <code>http://</code>? Do they add the <code>www</code>? Do they leave it out? Do they mistype the URL somehow? There&#8217;s a lot of variety when it comes to a visitor trying to get to your site and it improves usability when you eliminate as much as possible. Shouldn&#8217;t the <code>www</code> be meaningless by now?</p>
<h3>How Your Site Could Handle Different Requests</h3>
<ol>
<li>Both <code>www</code> and non-<code>www</code> URLs work.</li>
<li>If your visitor enters <code>www.example.com</code>, they will be redirected to <code>example.com</code></li>
<li>If the visitor enters <code>example.com</code>, they will be redirected to <code>www.example.com</code></li>
<li>Or it could be <strong>broken</strong>!</li>
</ol>
<h4><code>www</code> and Non-<code>www</code> Work</h4>
<p>An example of a site that does this would be TechCrunch. Both the <a title="WWW.techcrunch.com" href="http://www.techcrunch.com/"><code>www</code> version</a> and the <a title="techcrunch.com" href="http://techcrunch.com/">non-<code>www</code> version</a> work without any redirects.</p>
<p>This is a usable practice. Visitors don&#8217;t have to worry about being redirected or typing in the wrong address prefix. However, some search engines see the <code>www</code> as a <em>sub</em>domain. If a blog links to <code>www.techcrunch.com</code> and another one links to <code>techcrunch.com</code>, they are counted as links to <strong>two separate sites</strong>, which leads to a lower search engine rank. This can severely hurt TechCrunch&#8217;s SEO score, although that probably isn&#8217;t an issue for them as the <a title="Technorati's Top 100 Blogs" href="http://technorati.com/pop/blogs/">#2 most popular Technorati blog</a>.</p>
<h4>Redirect to non-<code>www</code></h4>
<p>Digg.com redirects its <code><a title="WWW.digg.com" href="http://www.digg.com">www</a></code><a title="WWW.digg.com" href="http://www.digg.com">-inclined visitors</a> to the <a title="digg.com" href="http://digg.com">non-</a><code><a title="digg.com" href="http://digg.com">www</a></code><a title="digg.com" href="http://digg.com"> equivalent</a>. The readability of the URL is improved because the visitor isn&#8217;t distracted by the unnecessary <code>www</code>.</p>
<p><strong>Bonus points</strong>: if you have information in the URL (say you&#8217;re trying to view the top stories over the last 24 hours), using the <code>www</code> prefix doesn&#8217;t delete that information and leave you confused and at their homepage. Check out what happens when you go to their <a title="It redirects to digg.com/all/popular/24hours" href="http://www.digg.com/all/popular/24hours">top stories with <code>www</code></a>. You&#8217;ll never even notice the difference.</p>
<h4>Redirect to www</h4>
<p>Amazon.com is the most popular online retailer and they use this method. When you go to <a title="amazon.com redirects to www.amazon.com" href="http://amazon.com/"><code>http://amazon.com</code></a>, you are quickly redirected to <code><a title="Amazon's Homepage (after being redirected)" href="http://www.amazon.com">http://www.amazon.com</a></code>. This doesn&#8217;t make a difference from a usability standpoint once you consider their audience. Amazon attracts more people that aren&#8217;t as technologically-inclined as Digg users. Seeing the <code>www</code> missing from the URL might confuse them to the point of thinking something is broken with Amazon and abandon whatever shopping they were doing. This is the worst case scenario, but none the less, a valid consideration. Amazon made the right choice when it came to which <code>www</code> method to use.</p>
<p><strong>Bonus points for Amazon</strong>: if you get a bit too trigger happy with your <code>w</code>&#8217;s, Amazon is right there to save you. If you type in <a title="wwwW.amazon.com still redirects to amazon.com" href="http://wwww.amazon.com"><code>www<em>w</em>.amazon.com</code></a>, you are still redirected successfully to Amazon&#8217;s homepage. This reinforces trust in the Amazon brand because they will always have your back. From a business perspective, this is an excellent idea because Amazon wants to get you looking at products faster by avoiding a potentially confusing error from a simple typo.</p>
<h4>URL Was <a href="http://icanhascheezburger.com/2009/05/18/funny-pictures-bell-wuz-broked/">Broked</a></h4>
<p>If your site only works with <code>www.yoursite.com</code>, you are going to run into trouble when a power user comes along, someone who knows that the <code>www</code> is now a pointless exercise. A visitor comes along, doesn&#8217;t type the <code>www</code>, and then is presented with a &#8220;Server Not Found&#8221; error or a 404 page. They will think something is wrong and most likely leave.</p>
<p>Please do <em>not</em> let this happen to your visitors. Accept any variation of URL your visitor can throw at you.</p>
<h3>How To Do It Right</h3>
<p>The ideal solution for the <code>www</code> problem is to redirect all requests to a non-<code>www</code> address as soon as the visitor gets to the site. During the redirection, the visitor should not lose any valuable URL information either. It should preserve the visitor&#8217;s original request, like the Digg example above. Redirect pages are definitely not invited to the party (&#8221;wait here for 5 second while we bore the hell out of you&#8221;). This allows for usability improvements and higher SEO scores for certain search engines.</p>
<p>Truthfully, it doesn&#8217;t matter much whether you use option 2 or 3. It&#8217;s a personal preference and I like keeping <code>www</code> out of all the fun!</p>
<p>The only step to redirecting your visitors is to put the following in your <a title="Apache's Official Documentation on .htaccess" href="http://httpd.apache.org/docs/1.3/howto/htaccess.html">.htaccess</a> file and changing <code>example.com</code> to your domain:</p>
<pre class="sh_html">Options +FollowSymlinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]
RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]]
</pre>
<p>The first bit is turning on Apache&#8217;s ability to redirect certain URLs. The 3rd line is saying &#8220;for URLs that begin with a <code>www</code>&#8221; and the 4th &#8220;permanently redirect to a non-<code>www</code> version of the URL.&#8221; The 301 redirect (note the <code>R=301</code>) makes sure search engines and browsers understand that this is a permanent redirection. Copying and pasting 4 lines into your .htaccess file is an easy way to instantly improve the usability and SEO of your site.</p>
<script type="text/javascript" src="/wp-content/plugins/shjs-syntax-hiliter/shjs/lang/sh_html.js"></script>]]></content:encoded>
			<wfw:commentRss>http://iloveusability.com/usability-tip/www-problem/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
