If users can call up your blog using both www and non-www URLs, it's time to select a preferred domain and perform a 301 redirect.You want all users to access your site the same way. Or at least Google does.
There are many variables at work here, so I suggest a search for redirect www and non-www and redirect non-www to www.
Confused? You might want to start with this squidoo page on 301 redirects.
You might also check the High Rankings forum for redirects or any number of other web forums, including Google's.
My knowledge of server-side is basic, so please read all you can about this issue, including Google's page on 301s. If your host is helpful with code, count your blessings and see if the support guys will check your work.
This code worked for me in changing www to non-www -- on a GoDaddy-hosted Apache/Linux set-up.
www to non-www
RewriteEngine On
RewriteCond %{HTTP_HOST} !^example.com [NC]
RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]
and for the reverse, non-www to www
RewriteEngine On
RewriteCond %{HTTP_HOST} !^example.com [NC]
RewriteRule ^(.*)$ http://www.example.com/$1 [R=301,L]
Don't forget to change "example.com" to your name.
I'm posting these because there are quite a few bad examples out there.
If you don't know what to do with these blocks, please don't try. Dig into the information linked above and learn all you can before acting. WordPress, in particular, has a complicated set of concerns about all this.
Good luck ... let's be careful out there.
Redirect update: Google and the other major search engines released a new "link" tag that is supposed to resolve issues of duplicate content on the same site. The links go on the duplicate pages and point to the canonical URL, meaning the one you want the search engines to serve up. Sounds like a good thing. Now if they can get Webmaster Tools to work ... )
0 comments:
Post a Comment