In support of the www subdomain prefix
For web addresses, I used to consider the “www” prefix an anachronism and argued that its use be deprecated in favor of the plain-old domain. In other words, I used to consider forms such as bostonazure.org superior to the more verbose www.bostonazure.org.
I have seen the light and now advocate the use of the “www” prefix – which is technically a subdomain – for clarity and flexibility. I now consider www.bostonazure.org superior to the overly terse bostonazure.org.
I am not alone in my support of the www subdomain. Not only is there a “yes www” group – found at www.yes-www.org – advocating we keep using the www prefix, there is also an “extra www” group – found at www.www.extra-www.org [sic] – advocating we go all in and start using two sets of www prefixes. While I’m not ready to side with the extra www folks (which would give us www.www.bostonazure.org), for those who do, you might want to know they offer the following nifty badge for your displaying pleasure.
While use of two “www” prefixes may one too many, here are 4 reasons to embrace a single “www’ prefix, followed by 2 tips on how to implement it correctly.
Four reasons to embrace the www prefix
Reason #1: It’s a user-friendly signal, even if occasionally redundant
The main, and possibly best, reason is that it is user-friendly. Users have simply come to expect a www prefix on web pages.
The “www” prefix provides a good signal. You might argue that it is redundant: Perhaps the http:// protocol is sufficient? Or the “.com” at the end?
First, consider that the http:// protocol is not always specified; it is common to see sites advertised in the form www.example.com.
Second, consider that the TLD (top-level-domain) can vary – not every web site it a “dot com” – it might be a .org, .mil, or a TLD from another country – many of which may not be obvious as web addresses for the common user without a www prefix, even with the http:// protocol.
Third, consider that even if there are cases where the www is redundant, that is still okay. An additional, familiar signal to humans letting them know with greater confidence that, yes, this is a web address, is a benefit, not a detriment.
Today, most users probably think that the Web and the Internet are synonymous anyway. To most users, there is nothing but the www – we need to realize that today’s Internet is inhabited by regular civilians (not just programmers and hackers). Let’s acknowledge this larger population by utilizing the www prefix and reducing net confusion (pun intended).
Reason #2: Go with the flow
The application and browser vendors are promoting the www prefix.
Microsoft Word and Microsoft Outlook – two of the most popular applications in the world – both automatically recognize www.bostonazure.org as a web address, while neither automatically recognizes bostonazure.org. (Both also auto recognize http://bostonazure.org.) Other text processing applications have similar detection capabilities and limitations.
Browsers also assume we want the www prefix; in any browser, type in just “twitter” followed by Ctrl-Enter – the browser will automatically put “http://www.” and append “.com” forming “http://www.twitter.com” (though then we are immediately redirected to http://twitter.com). [Note that browsers typically are actually configured to append something other than “.com” if that is not the most common TLD there; country specific settings are in force.] For the less common cases where you are typing in a .org or other non-default setting, the browser can only be so smart; you need to type some in fully on your own.
Reason #3: Advantages on high volume sites
While I have been aware of most of the raw material used in this blog post for years, this one was new to me.
High traffic web sites can get performance benefits by using www, as described in the Yahoo! Best Practices for Speeding Up Your Web Site, though there is a workaround (involving an additional images domain) that still would allow a non-www variant, apparently without penalty.
Reason #4: Azure made me do it!
It turns out that Windows Azure likes you to use the www prefix, as described by Steve Marx in his blog post on custom domain names in Azure. This appears to be due to the combined effects of how Azure does virtualization for highly dynamic cloud environments – plus limitations of DNS.
In fact, it was this discovery that caused me to rethink my long-held beliefs around the use of www. Though I didn’t find any posts that specifically viewed this exactly like I did, my conclusion is the following:
I concluded the Internet community has changed over the years and is now dominated by non-experts. The “www” affordance inserted into the URLs makes enough of a difference in the user experience for non-expert users that we ought to just use the prefix, even if expert users see it as redundant and repetitive – as I used to.
In other words, nobody is harmed by use of the www prefix, while most users benefit.
Two tips to properly configure the www prefix
One of the organizations promoting dropping the www – http://no-www.org/ – describes three classes of “no www” compliance:
- Class A: Do what most sensible sites do and allow both example.com and www.example.com to work. This is probably the most easily supported in GoDaddy, and probably the most user-friendly, since anything reasonable done by the user just works.
- Class B: Redirect traffic from example.com to www.example.com, presumably with a 301 (Permanent) http redirect; this approach is most SEO/Search Engine-friendly, while maintaining similar user-friendliness to Class A.
- Class C: Have the www variant fail to resolve (so browser would give an error to the user attempting to access it). This is not at all user friendly, but is SEO-friendly.
So what are the two rules for properly configuring the www prefix?
Tip #1: Be user- and SEO-friendly with 301 redirect
Being user-friendly argues for Class A or Class B approach as mentioned above.
You don’t want search engines to be confused about whether the www-prefixed or the non-www variant is the official site. This is not Search Engine Optimization (SEO)-friendly; it will hurt your search engine rankings. This argues for Class B or Class C approach as mentioned above.
For the best of both worlds, the Class B approach is the clear winner. Set up a 301 permanent http redirect from your non-www domain to your www-prefixed variant.
You can set this up in GoDaddy with the Forward Subdomain feature in Domain Manager, for example.
You can also set it up with IIS :
Or with Apache:
Tip #2: Specify your canonical source for content
While the SEO comment above covers part of this, you also want to be sure that if you are on a host or environment where you are not able to set up a 301 redirect, you can at least let the search engines know which variant ought to get the SEO-juice.
In your HTML page header, be sure to set the canonical source for your content:
<head>
<link rel="canonical" href="http://www.bostonazure.org/" />
...
</head>
Google honors this currently:
Google is even looking at cross-domain support for canonical tag (though other search engines have not announced plans for cross-domain support):
From an official Bing Webmaster blog post from Feb 2009, Bing will support it:
Reportedly, Bing and Yahoo! are not yet supporting this very well:
But it appears Bing and Yahoo! have either just implemented it, or perhaps they are about to:
You can also configure Google Webmaster Tools (and probably the equivalents in Bing and Yahoo!) to say which variant you prefer as the canonical source.
Unusual subdomain uses
There are some odd uses of subdomain prefixes. Some are designed to be extremely compact – such as URL shortening service bit.ly. Others are plain old clever – such as social bookmarking site del.i.cio.us. Still others defy understanding – in the old days (but not *that* old!), I recall adobe.com did not resolve – there was no alias or redirect, just an error – if you did not type in the www prefix, you were out of luck.
Another really interesting case of subdomain shenanigans is still in place over at MIT where you will find that www.mit.edu and mit.edu both resolve – but to totally different sites! This is totally legal, though totally unusual. There is also a web.mit.edu which happens to match mit.edu, but www.mit.edu is in different hands.
In the early days of the web, the Wall Street Journal was an early adopter and they used to advertise as http://wsj.com. These days both wsj.com and www.wsj.com resolve, but they both redirect to a third place, online.wsj.com. Also totally legal, and a bit unusual.
—
[edit 11-April-2012] Just noticed this related and interesting post: http://pzxc.com/cname-on-domain-root-does-work [though it is not http://www.pzxc.com .. :-)]
Credit for Traffic Light image used above:
- capl@washjeff.edu
- http://capl.washjeff.edu/browseresults.php?langID=2&photoID=3803&size=l
- http://creativecommons.org/licenses/by-nc-sa/3.0/us/
- http://capl.washjeff.edu/2/l/3803.jpg
Coding Out Loud 
