Mobile app version of vmapp.org
Login or Join
Murray432

: Removing non-www support I'm not an advocate of the no-www movement. I like the www because it adds as a buffer to distinguish between our public and private/static sites. The problem is that

@Murray432

Posted in: #Htaccess #NoWww

I'm not an advocate of the no-www movement. I like the www because it adds as a buffer to distinguish between our public and private/static sites.

The problem is that with one of our sites, our traffic is split pretty much 50/50 between those that use our www and those that don't.

Should I bother rewriting those who hit our non-www site to our WWW site? Or should I just leave them alone? All our google SEO whatnot is on our www site, so I'm not concerned about any of that, only about user perception.

Has anyone here had this problem before? I'm not concerned about the technial aspect (that's easy with a quick rewrite rule), primarily the social side.

10.04% popularity Vote Up Vote Down


Login to follow query

More posts by @Murray432

4 Comments

Sorted by latest first Latest Oldest Best

 

@Ogunnowo487

I find that for questions like these a good option is to see how the big boys do it. Go visit sites like Google, Amazon, Yahoo, MSN, and so forth.

What I've found is that every one of these types of sites goes with the I'd recommend doing the same.

10% popularity Vote Up Vote Down


 

@Ravi8258870

I would recommend redirecting all users to If you ever want to do any static file hosting then you don't have to worry about cookies.

I've have a few clients who advertise their site without www, but I redirect the users to www and have Google index with I haven't had anyone complain.

Here is what I've put in my .htaccess files:

<IfModule mod_rewrite.c>
# for www
RewriteCond %{HTTP_HOST} !^www.example.com [NC]
RewriteRule ^(.*) www.example.com/ [L,R]
</IfModule>


I haven't had any problems with this yet.

10% popularity Vote Up Vote Down


 

@Deb1703797

Either way is fine from a user perspective, as long as both work when you type them in the address bar. The problem is having both without redirecting one to the other. Google and other search engines will count example.com and example.com as two different URLS. This, along with inconsistently ordered URL parameters, is one of the major causes of duplicate content. If people are linking to both the www and non-www versions of pages, you're effectively diluting your PageRank between two different pages with the same content.

Since most of your Google traffic is coming through the www version, I'd 301 redirect the non-www to the www URLs. By doing it that way, you lose less potential PageRank through the 301 than you would the other way around.

10% popularity Vote Up Vote Down


 

@Mendez628

I think folks are pretty-much used to it, especially those typing in URLs. I modified my primary hobby site to redirect from non-www to www a few years ago and didn't see any negative impact in traffic or user comments. YMMV of course ;)

One comment on the rewrite rule. Be careful if you are rewriting at multiple levels of your site with .htaccess files. I learned the hard way (split PR) that although some .htaccess rules inherit, mod_rewrite doesn't (at least not by default).

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme