Going Secure

Over a year ago Google added HTTPS as a ranking signal to their search algorithms, which didn’t at the time change my opinion on the use of HTTPS over HTTP on my sites.

[alert icon=”icon-angle-circled-down” message=”If you want to cut to the chase, scroll to the summary box at the bottom of this post for the facts.”]

My previous job involved a vast amount of personal data so the use of HTTPS was the norm, but when building sites for companies that don’t carry out transactions or gather personal data with their sites it’s not on the list of default actions when building sites.

At the end of last year Google announced that it would be Indexing HTTPS pages by default and the blog announcing it reinforced their call for “HTTPS everywhere“. It was a signal for me to revisit my default setting of reserving HTTPS for sites that are carrying out financial transaction or storing personal data, but I revisited with a slightly different question than before so instead of asking myself “Why should I” I now asked myself “Why shouldn’t I”.

The only stumbling block for me was the potential cost of adding an SSL certificate to my sites and as I’m a one.com customer that block was quickly removed as it included in the price of my hosting package.

I’ve nearly finished converting all my business and personal sites to HTTPS, maybe it’s time for us all to go secure.

Summary Box

[space height=”20″][tabs orientation=”vertical”][/tabs]

[et_bloom_inline optin_id=optin_3]

2 thoughts on “Going Secure

  1. Jason Edwards says:

    Hi Andy, this is a great idea. I can find it hard to keep up with I.T. either by having the time or understanding the jargon, whether it effects me and if I should make the change / update / upgrade etc. Being kept up to date in simple terms will be excellent.
    Have you updated our site to HTTPS?

Leave a Reply

Your email address will not be published. Required fields are marked *