The HTTPS protocol is used to encrypt HTTP (Hypertext Transfer Protocol: WEB protocol necessary to exchange with a server) communications between users and a WEB site. In addition, when a browser makes a secure connection with a site using the HTTPS protocol, the WEB server sends it a certificate of authenticity. This certificate is used to verify the identity of the site with recognized certification authorities such as Symantec, VeriSign or Digicert. This behavior is directly integrated in the browsers and if a problem occurs, the browser will prevent users from accessing the WEB site.
The HTTPS protocol effectively prevents tampering and eavesdropping of communications between a user and a Web site, which greatly enhances the site's relative security and gives users confidence. Moreover, this criterion is very important to Google and has a direct influence on the positioning of a page.
The implementation of the HTTPS protocol is done at the server level where a specific configuration must be set up. Likewise, it is necessary to redirect all unsecured HTTP traffic to HTTPS. Find more information on how to set up the HTTPS protocol on Google's documentation.
When HTTPS is active on a site, it is necessary that all the resources of the page are also loaded via this protocol, otherwise the phenomenon of "Mixed Content" (mixing HTTPS / HTTP) occurs and can cause problems with the loading of unsecured resources. Find all the solutions to solve the problem of Mixed Content on the Google documentation.