: Change to www from naked domain impact on seo I have set up my website from the beginning to be used without the www, ie 'naked', with the following command at .htaccess and everything is
I have set up my website from the beginning to be used without the www, ie 'naked', with the following command at .htaccess and everything is working fine.
RewriteCond %{HTTP_HOST} ^www.soeezauto.ma [NC]
RewriteRule ^(.*) soeezauto.ma/ [R=301,L]
Now, I have placed the website on Cloudflare for optimization reasons and it seems that they are only able to handle www domains ( if you come through a partner host, which is my case ), so I need to change my domain to work as example.com
My main concerns are:
Losing INDEXATION
Losing HISTORICAL DATA on Analytics/Webmaster
Make sure all the web pages I have out there without www will show normally when I change to example.com
This is what I found so far:
In Google Webmaster Tools -> Website settings -> Favorite domains, it is marked as not defined, meaning neither example.com nor example.com are selected.
So, should I leave as is or should I choose example.com? Or is it something else I should do?
In Google Analytics I found this article.
Is it fine to do like that?
In .htaccess
RewriteCond %{HTTP_HOST} ^.example.com [NC]
RewriteRule ^(.*) www.example.com/ [R=301,L]
Also, I read in this question, that I should REDIRECT ALL OF MY WEB PAGES to WWW via .htaccess. Is that the case? I have about 4000 pages out there. It will slow the server down quite a lot I believe to have such a huge .htaccess.
Will that work? Last thing I want is to mess this up and lose data/indexation, not to mention have the site inaccessible to my visitors.
More posts by @Cody1181609
1 Comments
Sorted by latest first Latest Oldest Best
Will you lose SEO value?
301-headers will transfer all* SEO value from the naked version to the www version, you have nothing to worry about, as long as the pages keep existing (which should be the case if you only switch to ). Don't forget sitemaps, and other XML files which might contain your domain.
* I've read about loosing the tiniest bit due to a redirect, but cant find documents about that.
Will my server slow down (with 4000 pages)?
Theoretically? Yes. Noticeable? I doubt it. .htaccess is really really fast, you should not worry about this. Besides, after an X amount of time all pages will be index as www, so the need for redirect becomes less and less (until it's only needed for the users why directly type you URL, without www).
# Some example code. ALL pages will be redirected properly,
# No need for individual redirects
# No need for the actual domain name, hard code as little as possible
RewriteCond %{HTTP_HOST} !^www [NC]
RewriteRule ^(.*)$ www.%{HTTP_HOST}/ [R=301,L]
The Google tools/sites
You're gonna have to set all preferred's to the version.
Do you really need a new code? IMO not really. I did this when I switched from HTTP to HTTPS, it confused me a heck of a lot more then it helped, resulting in weird verification problems.
Looking back, I wish I stayed with 1 code, loosing my history wasn't worth "doing it right" (again, IMO).
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.