Does your website require visitors to enter sensitive data, like passwords or credit card information? You probably need to read this article carefully if your site is under the HTTP protocol.
Update: The title “Google drops support for HTTP on Chrome” tracked too much attention (which we liked) but with negativity (yeah it’s actually missleading – we see it now). Anyway, we heard you, we fixed it. – Thanks
All for the security of the user
Ther has been a major update for Chrome on January this year, where websites that lack an SSL certificate, are labeled as not secured, in a step to inform the users that the data they are about to enter are not protected from prying eyes, prompting them to be more cautious on the info they provide.
This neutral label appears on all HTTP sites and becomes more attention-catching on pages that contain form inputs like passwords.
Things will change on Chrome v62
On their security blog Google has announced
the next steps they are going to take on this matter, in order to help users be more protected on their online experience.
More specifically, the “not secure” notice will be shown on two more situations, that is when user enters data on an HTTP page, and on all HTTP pages visited in Incognito mode.
Treatment of HTTP pages in Chrome 62 – Google Security Blog
All user data should be treated as private
As mentioned, the “not secure” label is currently visible when the user enters sensitive data like passwords and credit card data. As Google states, not only this information should be treated as private but all data that the user enters.
When users browse the web on incognito mode, they are more likely to expect a more private experience. The issue here is that private browsing doesn’t mean secure browsing and people do not have that clear in mind. That’s one of the main reasons Google aims to inform those users on every case they are required to enter data on a website.
The ultimate plan
Google also stated that they plan to mark all websites that are not served over HTTPS as not secure, ultimately labelling them with the red triangle they use for broken HTTPS connections.
Google security blog
What you should do
The only thing that should be done to resolve this situation, is to switch your website to HTTPS and waive goodbye to HTTP. This can be easily achieved by purchasing an SSL certificate. Don’t worry, they are not as expensive as they used to be.
There are many places where you can purchase one and the setup is fairly easy. Just do a Google search.
Why should you care about purchasing an SSL certificate
Purchasing an SSL certificate may seem like a nuisance to many, but switching to HTTPS is a big thumbs up as it may be a good means to possible increase of your profits
Don’t believe me? Let me explain.
websites under the HTTPS protocol are placed higher in Google rankings
That’s something every SEO expert will tell you and you know you want to rank higher, don’t you? That’s a great way to get there.
Users tend to leave not secure pages
A study from Google showed a 23 percent reduction in navigation to non secure pages that require sensitive data.
This could mean an increased bounce rate
to your checkout pages.
We live in an era where people tend to be more cautious when it comes to their privacy. By switching to the HTTPS protocol, you show them that they are valuable to you and that you care about their personal data. Believe me, they will admire that.