Chrome will signal the fact that your site is not https secure

The noose is tightening, Google publishes a press release whose tone is unequivocal

In January 2017, I alerted my current and former customers on my blog and by email that the transition to the secure Https protocol would be essential in the coming months.

The search engine has been sending out a warning in an almost threatening tone in recent days ( since August 16) warning that insecure sites would be “tagged” in the browser:

Here is the warning issued by Google Search Console and received by email by the owners of sites that are still in http.

Chrome will display security warnings.

To: Owner of http://www.votre-chouette-site-web.com

Starting in October 2017, Chrome (version 62) will flag HTTP pages with text input forms as insecure. It will do the same for all HTTP pages in Incognito mode.

The following URLs on your site contain text input fields (such as < input type=”text” > or < input type=”email”) >that will trigger Chrome’s new warning.

Review these examples to find out where these warnings will appear, and to take steps to help protect user data. This list is not exhaustive.

http://www.votre-chouette-site-web.com

This new warning is part of a long-term goal to flag all pages using the HTTP protocol as insecure.
To resolve this issue:

Switch to HTTPS

To prevent your site from being flagged as insecure when people visit it on Chrome, only collect user data from pages that use HTTPS.

We understand that it is in the status bar that an icon (red?) will appear – instead of the green padlock that characterizes sites under TLS certificate

Instead of

The press release does not say whether this infamous “tag” will eventually appear on the SERP (the results page), which could frighten the Internet user and push him to click on the results with the green padlock rather than those with the discriminatory mark.

Any help with this migration?

The SEO agency SEO PME has developed a healthy and proven protocol that guarantees that no loss of positions is observed at the time of migration.

The migration takes only one (well-planned) day. However, depending on the configuration of certain servers, it is sometimes complex to set up

This article on migrating to https is also a tutorial that allows you to set up this operation yourself.

Reminder

It should be remembered that secure connections via TLS certificate are considered necessary to reduce the risk of content injection that can lead to eavesdropping, interception, man-in-the-middle attacks and other data modifications.

Firefox too

The change follows similar actions by Mozilla which launched Firefox 51 this week. The browser announces that it will mark the sites that remain under HTTP with the “Not Secure” label,

The long-term goal is to force the entire Web to migrate to HTTPS.

A good point to end this brief

With this update, Google announces an improvement in page refresh that will result in pages loading 28 times faster .