ICT Insight | Darwin Blog - https://www.itblog.com.au
SSL Protected Websites, What and Why ?
By Michael Feldbauer
Published on 28/12/2017

Why HTTPS Should Be Enabled on Your Website

It’s good for search.
Google’s algorithm requires sites to essentially battle it for top search rankings, two websites that could both rank for a user’s query, essentially running toward the finish line of top results.
But what happens if there’s a tie? Do the sites battle it out in a “sudden death” round?
It all goes back to the idea that Google is constantly solving for the user, and makes frequent changes to its algorithm that create a better experience. Which is why our next point makes sense.

It’s better for users.
SSL helps to prevent these “man-in-the-middle” attacks -- “a form of eavesdropping where communication between two users is monitored and modified by an unauthorised party” -- and keeps user information secure.

That makes https especially important if your website accepts credit cards or has a login functionality. With so many of these hacking incidents making headlines, users want to know that your brand is making an effort to protect them from their private information being stolen or compromised.

user privacy = important
https = good for privacy

SSL is required for AMP.
A few pieces of vocabulary to break down here:

“AMP” stands for Accelerated Mobile Pages. It’s the technology that makes certain pages load almost instantaneously on mobile. So, when you search for something on your mobile device through Google, you might notice that some results have a lightning bolt icon next to it, that means that it’s AMP-ready.

Google is indexing mobile.
So, that thing we just said about the importance of mobile? It turns out, Google is actually going to start indexing mobile, which means that its “algorithms will eventually primarily use the mobile version of a site’s content to rank pages from that site.”
But in order for a mobile site to be indexable, Google recommends several best practices, one of which is to “start by migrating to a secure site,” especially “if [you] don’t support HTTPS yet.”

Not secure.
To elaborate -- In 2017, Chrome 56 will start displaying “not secure” in the browser bar for any http (notice it’s missing the “s”) sites that ask users for login or credit card information.

I don’t know about you, but when I’m about to make an online purchase and see that the site isn’t secure -- for example, that the padlock icon in the browser bar is broken -- I navigate my business elsewhere. And I’m not alone. In fact, only 3% of online shoppers say they would enter their credit card information on a site without the green padlock.

Imagine if Google starts doing that work for users before they can even get to checkout. If the number is as low as 3% now, before search engines start doing the legwork to label sites as “not secure” before anyone even visits them, you can see how traffic to those sites will suffer a huge blow -- as well as its digital sales revenue.

The long and the short of all the above is you need for your web site provider / developer to update your site, purchase a SSL Certificate and secure your website, don't act and miss out...