You’re right! Sooner or later we’ve to move to HTTPS. I appreciate that you shared some points about HTTPS and shared the worth reading post about HTTPS. I’m going to read the Yoast post because I’m thinking to move my site HTTPS.

Thanks!

I think eventually Google will start creating its own websites and content for displaying in search results, and ditch us all for good!

appreciate the comment Amar!

That is indeed the kicker Andrew. It is coming and we need to find an easy way to deal with it. I have been ignoring it as I was not sure if it was going to be easy (most migrations are not) and earlier in the year it was just about a “small ranking factor” until the Chrome (then WordPress) announcement made me listen :>

It is really a good movement to HTTPS. With HTTPS, the story is quite the same as HTTP. But when security is a must, HTTPS differentiates one sender and receiver from another. SSL takes the data, going or coming, and encrypts it. The hope is that this algorithm is so complex it is either impossible or prohibitively difficult to crack. Eventually, thanks for reveling a light on this topic.

With best wishes,

Amar kumar

Very interesting post.

Putting the “not secured” triangle on pages that deal with credit information if they’re not https makes sense. But you blindsided me with “Eventually, we plan to label all HTTP pages as non-secure, and change the HTTP security indicator to the red triangle that we use for broken HTTPS.”

This is really serious and something else I’ll have to look into now. Dave had a good point about the backlinks but that’s something that’ll have to be dealt with eventually. Thanks for the heads up. Going to read on on it more.

– Andrew

there are lots of hurdles for sure Dave, hence my waiting. But sooner or later we all have to do it :>

Looking forward to it myself David. I think it is more a move to weed out the crap. Forcing HTTPS means only legit websites will have it, and crappy sites not. So easier for Goog to find out who sux