I would like to set up a new business site. I plan to direct www.example.com to example.com and only use that domain. My plan is also to only use https and not http. Does this affect the SEO for the site? E.g. do Google put lower or higher rank for sites that is only available via https?
|
|
|||
|
|
|
Google doesnt care, but it may be a waste of your bandwidth. Google sees an https:// and http:// request as the same. But will see the www.example.com and example.com as two seperate sites. Most sites just use the https:// on pages where user logs in, gives credit card, edits his/her information etc. On pages where someone just reads iformation such as home page, or terms, or privacy policy, blog artices and so on its best not to force https. |
|||||||||||||||
|
|
It is my experience that offering a page only via HTTPS sometimes leads to problems. We had the problem that Digg.com doesn't like our page via HTTPS, and thus we couldn't add our page to Digg. There are some other examples where we had similar problems. If you consider that a link from Digg may be part of your SEO work, HTTPS-only mode may be bad. Also, some (maybe older) web crawlers don't like HTTPS (you can see that in your logs if you offer a redirect). |
||||
|
|
|
Check Majestic hitorical back links to each and you will see it does make a differentce |
|||||||||
|
|
From an SEO standpoint, it's not necessarily bad to force HTTPS. From a User Experience perspective however, it's usually not a great idea. Forcing HTTPS will use more bandwidth, and more resources on your server, which will result in a someone degraded User Experience. This could potentially cause your site to have a higher Bounce Rate, which in turn can lead to your site ranking lower. As John Mueller pointed out above, HTTPS can also cause some scary warnings to pop-up which could scare away potential users, and also further increase the Bounce Rate. |
|||
|
|
