By now, it’s crystal clear that Google’s long term plan is to herd webmasters towards creating a more secure internet. Google has stated long ago that they will begin to favor secured sites over non-secure sites in search engine results pages. If you haven’t migrated your website to a secure HTTPS:// version, there will soon be added repercussions for not having done so yet.
Back in January 2017, Google began showing “NOT SECURE” warnings on non-secure pages with credit card or password fields.
Adding to this effort, the newest version of Google Chrome will start showing a “NOT SECURE” warning when: users enter text in a form on an HTTP page, or when users attempt to access a non-secure (HTTP) page via incognito mode. This update is scheduled to take effect sometime in October 2017. (If you manage a non-secure website, you might have already received emails on this update via search console).
One possible implication of the update is that users, who begin to fill out a form or enter other information, may abandon doing so when faced with a “NOT SECURE” warning. There could be a real possibility of losing leads due to having forms on non-secure pages.
Eventually, Google plans to call attention to all HTTP pages with its “NOT SECURE” warning as part of its HTTPS Everywhere campaign. Fortunately, migrating a site to HTTPS is a fairly straightforward process for most developers and site configurations. To get you started, take a look at Patrick Stox’s great step-by-step guide via SearchEngineLand.