| Sign In/My Account | View Cart |
|
|
Should 'www' be retired?
![]() Shawn Wildermuth Ok, maybe this may be petty, but why do so many sites require that 'www' before the names? I have wasted lot sof time trying to navigate to sites by just their domain name, only to find out that I need the 'www'. What do I mean? Both of these should work: But then why would some develop a site that doesn't work like that. For example (with apologies to Brent Rector): Or this (again, apologies to John Lam): Shouldn't the 'www' be retired as a relic of the Mosaic days? That's just my opinion, I could be wrong... Shawn Wildermuth is the founder of ADOGuy.com and is the author of "Pragmatic ADO.NET" for Addison-Wesley. Showing messages 1 through 7 of 7.
Return to weblogs.oreilly.com. Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc., disclaims any and all liabililty for that content, its accuracy, and opinions it may contain.
|
|
Sponsored By: |
|||||||||||||
Using URLs without www., I noticed that people adding links to your site prefix your URL out of habit, or maybe to make a "better" URL and do the site owner a "favour".
Now stupid search engines see two sites with each one counting for half of the incoming links, instead of one higher ranked site counting for all of the links.
As a consequence: when enabling both (or even more) URL variants, you should at least redirect the user (and the spiders!) to only one distinct host name.
Jens.