If you have sites on HTTP, Google has begin sending out notices to site owners that their sites will be flagged as “not secure” in Chrome beginning in October 2017.
So what does this mean? If your site has any form – which would include things such as a comment form – then Google will show the site as being not secure in the Chrome browser. Additionally, Google will show this warning for ALL pages when viewed in Incognito mode. So if your site has no forms but is the type of site that people might prefer to visit via Incognito, then those sites will be shown as not secure.
The change will begin in October 2017, with version 63 of Chrome, so site owners still have a month or two in order to implement HTTPS on their sites.
However, some sites are getting these notices even if they are HTTPS. This is because many site owners have both the HTTP and HTTPS versions of the site verified in Google Search Console. But even if the HTTP is correctly redirecting to the HTTPS equivalents, Google is still sending a warning notice to those HTTP properties.
Here is what the notice Google Search Console is sending out looks like:
The notice also confirms that this is only a step in the process that will eventually see all pages on HTTP marked as not secure.
Latest posts by Jennifer Slegg (see all)
- No Plans for Google to Mark HTTP as Insecure in Search Results - September 22, 2017
- Google: Do HTTPS Migrations Separate From Other Major Changes - September 22, 2017
- Google: Rankings Should Remain Stable With HTTPS Migrations - September 21, 2017
- Google: Value (or Not) of Doing Link Audits - September 20, 2017
- Google Indexes AMP Version for Mobile First When No Regular Mobile Page - September 19, 2017