Now it is high time to leave the HTTP for HTTPS.
When Chrome 56 will be released in January (2017), the browser will start to warn on many sites that do not use HTTPS.
This may be the last nail in the coffin for HTTP sites, and forces us to use HTTPS
What is https
is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security or its predecessor, Secure Sockets Layer. The main motivation for HTTPS is authentication of the visited website and protection of the privacy and integrity of the exchanged data.
Read full explanation on Wikipedia
If you have a regular blog, or other site where you no ask for any sensitive information, than you will not have any problem, at least not yet.
But sites that ask you to enter sensitive information such as login credentials or credit card information, and do not use HTTPS, will be flagged as dangerous.
Why is Google doing this?
It’s a very simple question to answer, Google simply want a safer Internet
If you load a site over HTTP, someone else that are logged on to the same network can see what you send, or modify content before it reaches you.
So in short: Details from credit card and passwords that you enter can be easily be snapped up by someone else.
So how will this work.
The warning in Chrome will appear as warning “not secure” next to the address bar.
And if a site is secure, will it be just like today, a green padlock next to the address bar.
But Google does not stop with this, in the long term, all sites that use HTTP will be marked as unsafe.
The warnings in Chrome is only one step to get people changing over from HTTP
When it comes to ranking, so will HTTP be ranked lower than the more secure HTTPS://