Adding SSL to my website.

BoostMedia

Registered Member
Joined
Sep 14, 2013
Messages
64
Reaction score
13
I'm thinking to add SSL to my website. So if URL from - http://www.xyz.com will change to https://www.xyz.com will my ranking will drop? Also if possible then tell me the advantages and disadvantages of it thank you.
 
Last edited:
Google announced that in the beginning of next year SSL would become a ranking factor.

For the setup of SSL as we did:
- Setup SSL on the page (make sure your sitemap also contains https url from then on)
- added https url to Google webmaster tools
- changed prefered url to https type in Google webmaster tools
- redirected (301) all none https traffic to https
 
There is a chance for a dance in rankings.Patiently give some time to get back your ranking level.It will bounce back.
 
Source?

I haven't heard that from any official at Google.

Seems I mixed 2 things up.

https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html Google uses SSL / https as a ranking factor since mid 2014

https://security.googleblog.com/2015/12/indexing-https-pages-by-default.html Google indexes https as default and prefering it

https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html In January Chrome will start to label non-encrypted sites “not secure.”

Sorry for the mix up.
 
Seems I mixed 2 things up.

https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html Google uses SSL / https as a ranking factor since mid 2014

https://security.googleblog.com/2015/12/indexing-https-pages-by-default.html Google indexes https as default and prefering it

https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html In January Chrome will start to label non-encrypted sites “not secure.”

Sorry for the mix up.

No worries ;)
 
I haven't seen any proof that adding a SSL improves rankings. Have you?

My biggest problem with SSL is that it slows down the site (increases the load). And, speed IS a ranking factor.

Personally, my advice is to stay away from SSL unless you need to encrypt the content that goes through the pipe. In other words, if your content is intended for everybody, do not encrypt it, as you have nothing to gain by it.
 
There are no disadvantages. Just 301 every url from the http to https via .htaccess and make sure to add both ssl and non ssl sites to google webmaster stools panel.
 
301 and you're done


The one reason people dance is because they do a 301 but leave the canonical tags as http

If you do it right, doubt you'll have any issues more than the odd hour while google updates
 
HTTPS is a really lightweight ranking signal yet, if it is at all, however, according to Goolge - 'Beginning in January 2017 ... , we’ll mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure', so it looks like it may be strengthened in future, and you may benefit in the long-run.
In case your website carries any sensitive info or involves any transactions - https is really a must. This totally shouldn`t affect your rankings negatively, just make sure to redirect the http version to https properly at once and update your sitemap, then allow some time for adjustments (the rankings may indeed dance for a lil while after the switch).
 
'Beginning in January 2017 ... , we’ll mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure', so it looks like it may be strengthened in future, and you may benefit in the long-run.
Marking pages that collect sensitive/private information as non-secure is precisely the right step and it is exactly what SSL was developed for, in the first place. But, no, it doesn't mean there is any push to have all pages run on https and it also doesn't mean you may benefit from doing so.

The entire discussion here focused on how not to screw up the move from http to https.

What this discussion should focus on, instead, is why would you want to use SSL.
 
My biggest problem with SSL is that it slows down the site (increases the load). And, speed IS a ranking factor.
Personally, my advice is to stay away from SSL unless you need to encrypt the content that goes through the pipe. In other words, if your content is intended for everybody, do not encrypt it, as you have nothing to gain by it.

Then get a decent hosting. I had no speed issues until now. But I run the stuff for the company I work for on vps or full dedicated boxes, not low end. Sites have 500 up to 5K visitors a day.

The second part is plain bs in my eyes. You loose nothing by it, but gain trust. People become more and more aware of web tech. and encryption. If you gonna sell something you need trust.

A down side that I see is that some adnetworks or adservers won't work correct or rather punch a hole in your https.

Marking pages that collect sensitive/private information as non-secure is precisely the right step and it is exactly what SSL was developed for, in the first place. But, no, it doesn't mean there is any push to have all pages run on https and it also doesn't mean you may benefit from doing so.
You can adopt something earlier or later. As for now we have competitors that don't run on full https. I like to be ahead, maybe sometime in the future Google checks how long a page had site wide encryption .
Also with letsencrypt it's pretty painless to get a cert and runs almost on set and forget mode.

The entire discussion here focused on how not to screw up the move from http to https.
What this discussion should focus on, instead, is why would you want to use SSL.

In unedited opening post, op ask how to do it.
 
Then get a decent hosting.
Yes, you can get a better host. But, it doesn't change the fact that SSL takes extra resources.

People become more and more aware of web tech. and encryption.
At that point, people will understand the trust is misplaced. By encrypting information that are intended for public viewing (not private), they gained nothing.

In unedited opening post, op ask how to do it.
True. My answer is: you don't.
 
I don't believe your ranking will improve just because you install an SSL cert. I know what google published but still!
 
Yes, you can get a better host. But, it doesn't change the fact that SSL/TLS takes extra resources.

The extra resources used are little to none for normal users. You're right a SSL/TLS handshake over TCP takes something around 12 packets to complete a handshake while a normal TCP handshake takes 3 packets.

In a paper published in 2010 (! read here):
Modern hardware can perform 1500 handshakes/second/core. That's assuming that the handshakes involve a 1024-bit RSA private operation
I highly doubt that the most users here are running pages that handle 1500 request per second, and that numbers were from 2010, so current hardware would be above that.

Also see this post by maxcdn. Also when Google uses speed and ssl as signals they would credit that securing a connection would cost you something about 0.03 seconds. Again don't use hosting that is overselled.

At that point, people will understand the trust is misplaced. By encrypting information that are intended for public viewing (not private), they gained nothing.

You do understand what SSL or rather TLS means? It's not about encypting content / information. The information is still unencrypted just when the information is send it gets encrypted. I don't see the down site of using TLS,
and I don't get your point except that it seems you use a pretty shitty shared webspace that sucks. TLS will ensure or atleast reduce the risk for certain attacks on transport layer and ensure you're communicating with the correct participant.
I would count that as a gain for the user.

It's not that you break the "Hackers Manifesto" that phrack mag published in 1986, information still stays free and accessible...
 
So, just to sum up your post:

1. Yes, there is an increased load when using SSL/TLS
2. No, using SSL/TLS for non-private information won't help you.

Exactly my point...
 
Back
Top