HTTPS, Google to a security obligation?

HTTPS, Google to a security obligation?

The HTTPS or the “HyperText Transfer Protocol Secure”, literally “secure hypertext transfer protocol” is the combination of HTTP (communication protocol used on the internet) with an encryption layer like SSL. This SSL certificate makes it possible to secure the exchange of data between a remote machine (the server) and a client station (computer, tablet or any other device).

the HTTPS therefore allows the visitor to verify the identity of the website he accesses, through an authentication certificate issued by a third party authority, deemed reliable and theoretically guarantees the confidentiality and integrity of the data sent by the user (including information entered in the forms) and received from the server (encryption of the exchanges). It can also validate the identity of the visitor, if the visitor also uses a client authentication certificate.

How to enable SSL: certification operator

It is necessary to go through a certification operator (OC) who will ensure the supply and management of electronic certificates. Its role is to implement a secure technical platform, in compliance with the requirements set out in the certification policy. Certification operators are limited in the market and often are hosts themselves.

And Google in all this?

The security team of Google Chrome had proposed in 2014 that all sites in HTTP are considered insecure and that sites secured by SSL are better taken into account in SEO , becoming a criterion of its algorithm.

Subsequently, Google (and its engine ) remained a little discreet on the promotion of HTTPS but things are clear: evocation during the Unix Enigma conference in January, integration in its latest instructions to webmasters, and future changes to its browser (late 2016), which will indicate with a red cross that the site is not secure.

It is not known if there will be a penalty, but it seems that it is a very strong incentive for webmasters to pass their sites under HTTPS.

google red cross, it is unclear whether there will be a penalty, but it seems that this is a very strong incentive for webmasters to pass their sites under HTTPS.

And the  natural referencing  ?

HTTPS will it really be a criterion taken into account in its algorithm? We can expect it because the browser war continues! And if there will be no direct penalty for an unsecured site (at first …), it is likely that a site under HTTPS will be put forward compared to a site in http (the logic of range of products / services …)

The ambition is that all the web goes on HTTPS! The message is clear. If you have the means and knowledge, go to HTTPS, because the future is uncertain for sites that will remain clear.
Especially since the HTTPS is gradually becoming democratic and we see many initiatives like “Let’s Encrypt” which offers free SSL certificates for all users.

Leave a Reply

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