Well, there are some compelling reasons why that is a bad idea. I’d try to make you feel guilty about that decision, if it weren’t for the fact that I’ve been too lazy up until now to do it myself. Oops.

For those of you that are impatient, I’ll deal with the technical stuff first. Then, we’ll take a look at why you shouldn’t be using the ‘www’ subdomain.

How to Use .htaccess to Remove the ‘www’ From Inbound URLs

This can be accomplished with a simple .htaccess mod_rewrite redirect.

First, let’s take a look at the code as it appears in my .htaccess file.

RewriteEngine On
 
#redirect from www.life-of-brian.com to life-of-brian.com
RewriteCond %{HTTP_HOST} ^www.life-of-brian.com$ [NC]
RewriteRule ^(.*)$ http://life-of-brian.com/$1 [R=301,L]

The first line turns on the mod_rewrite engine. You’ll need this at the beginning of your .htaccess file if you plan to use any rewrites.

The “RewriteCond” line tells the server what to look out for. In this case, the simple regex [^www.life-of-brian.com$] grabs any expression that starts with www.life-of-brian.com. The remainder of the expression – such as the trailing part of the URL – is stored in the variable $1.

The “RewriteRule” line tells the server where it should send the user. It rewrites the entire URL, starting with the domain without the www [http://life-of-brian.com] and then it appends the trailing portion of the URL [$1].

How do you adapt this for your own site? Simple.

In the RewriteCond, change www.life-of-brian.com to your own domain (including the www). Then, in the RewriteRule line, replace http://life-of-brian.com wth your own domain.

It’s also a good idea to wrap the whole snippet with the tags <IfModule mod_rewrite.c> and </IfModule>.

Here’s the entire .htaccess file rewritten for the domain mydomain.com.

RewriteEngine On
 
#redirect from www.mydomain.com to mydomain.com
RewriteCond %{HTTP_HOST} ^www.mydomain.com$ [NC]
RewriteRule ^(.*)$ http://mydomain.com/$1 [R=301,L]

If you’re using this with an existing .htaccess file, put this snippet at the very beginning. For example, I use .htaccess to create pretty URLs for my WordPress posts. I placed this snippet before the snippet that was automatically generated by WordPress.

Ok. So Why Remove the ‘www’?

Let’s focus on two main reasons why you shouldn’t use – and why should encourage your users not to use – the www subdomain. The first reason has to do with form and semantics, while the second one might have benefits in terms of SEO and SERP.

The Semantics Argument. If you surf around web design blogs, you’ll see a lot of talk about coding semantically correct and standards meeting sites. There’s a belief that doing things the right way is inherently good – even if there may not be a lot of hard evidence that you benefit from it.

Likewise, there’s an argument to be made for the disuse of the ‘www’ subdomain. It is no longer needed, it is depracated, and it should therefore go by the wayside. I stumbled on the site no-www today, and found a great quote to summarize this position:

Succinctly, use of the www subdomain is redundant and time consuming to communicate. The internet, media, and society are all better off without it.

In most cases, there is no need to use the www subdomain. Your browser and the web server assume that you’re looking for web content – so they serve it up automatically. Including the ‘www’ is therefore redundant.

Since the ‘www’ is no longer necessary, it just seems like the right thing to do to not use it. You should therefore gently suggest to your users that they stop typing in those letters for no reason.

The SEO Argument. If you want visitors to find your website through a search engine, you know at least a bit about SEO (Search Engine Optimization) and SERP (Search Engine Results Page) placement. You know that things like links to your site help improve your SEO and SERP – and ultimately bring more users to your site.

So what happens if the search engine thinks that www.mydomain.com/landing-page.html is different from mydomain.com/landing-page.html? If the inbound links to your site are split between these two domains, the search engine might miscalculate the number of links coming to your page – thus negatively impacting your SEO and SERP.

The htaccess mod_rewrite redirect that we used above automatically sends the search engine spider to one page – no matter URL the inbound link provided. There’s no chance that the search engine will get confused and consider the two URLs to be separate pages.

Considering it takes only a couple minutes to create an appropriate .htaccess file, I think it’s time well spent if it has even the slightest impact on your SEO and SERP.

Turns out it wasn’t quite as easy as I hoped. There’s a WordPress plugin available to redirect your feed to Feedburner, but this only redirects the main feed and the comments feed. No dice for categories.

I found a few people suggesting an alternative: .htaccess rewrites. I never liked working with .htaccess, mostly because I never liked working with regex. But what are ya gonna do?

An .htaccess Alternative to the Plugin

I found an example of a .htaccess solution at Persihable Press.

For a full explanation, head over to the original article. But in the meantime, here’s the .htaccess code he suggested:

# temp redirect all wordpress feeds to feedburner
 
 RewriteEngine on
 RewriteCond %{REQUEST_URI}      ^/?(feed.*|comments.*)        [NC]
 RewriteCond %{HTTP_USER_AGENT} !^.*(FeedBurner|FeedValidator) [NC]
 RewriteRule ^feed/?.*$          http://feeds.feedburner.com/perishablepress         [L,NC,R=302]
 RewriteRule ^comments/?.*$      http://feeds.feedburner.com/perishablepresscomments [L,NC,R=302]

As I understand it, this is more or less a three step process.

First, the regex catches all requests for a URI that includes feed or comments (i.e. your RSS feed). Then, it checks if the user agent is FeedBurner. The FeedBurner bot is allowed to access the original feed, but everybody else should be tossed over to the Feedburner site.

Finally, it sends the user to the appropriate Feedburner URL, based on the request URI.

Adding Category Feeds

That, of course, does the same thing as the plugin. It redirects the site feed and the comments feed, but it doesn’t help you redirect your categories.

For me, each parent category is like it’s own site, so that doesn’t help. I’d like you to be able to subscribe to the “Nerds at Work” feed about web development without being bored by all my ranting on education.

Luckily, somebody commented on the original article and left a suggestion as to how to redirect the category feeds. I used that to create my own .htaccess file, and everything seems to work hunky-dory.

You don’t need to re-write any of the conditions, because that regex will already flag the category feeds. All you need to do is add a few extra rewrite rules, based on the new URIs and provide the appropriate Feedburner URL.

In general, that rewrite rule should look like this…

RewriteRule ^category/nerds-at-work/feed/?.*$
  http://feeds.feedburner.com/thislifeofbrian-work [L,NC,R=302]

Replace ‘nerds-at-work’ with your own category slug, and replace the full URL with the URL to your Feedburner feed.

I had some trouble with this at first, but I think the problem was due to positioning. In the end, I added all of the category specific re-write rules after the general rewrite rule. When I placed them first, it didn’t work. Might just be that I’m a regex/htaccess newb, though.

Here’s the full .htaccess file that I’m using, including what WordPress generated for the pretty-urls.

# Redirect Wordpress Feeds to Feedburner
 
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/?(feed.*) [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(FeedBurner|FeedValidator) [NC]
RewriteRule ^feed/?.*$ http://feeds.feedburner.com/thislifeofbrian-sitewide [L,NC,R=302]
RewriteRule ^category/nerds-at-work/feed/?.*$ http://feeds.feedburner.com/thislifeofbrian-work [L,NC,R=302]
RewriteRule ^category/nerds-at-play/feed/?.*$ http://feeds.feedburner.com/thislifeofbrian-play [L,NC,R=302]
RewriteRule ^category/teach-them-well/feed/?.*$ http://feeds.feedburner.com/thislifeofbrian-teach [L,NC,R=302]
RewriteRule ^category/life-of-brian/feed/?.*$ http://feeds.feedburner.com/thislifeofbrian [L,NC,R=302]
 
# BEGIN WordPress
 
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
 
# END WordPress

Good luck, and hopefully you’re more experienced with htaccess/regex than I am.