Before anything else, obviously where it says “http://yoursite.com”, it will be the URL of your own site on any notice you receive specific to it.
It has been a long time coming but it is finally almost here. Google announced almost a year ago that Chrome will eventually mark all HTTP pages as “NOT SECURE“.
I have written in January that “Moving HTTP to HTTPS” should be your 2017 number 1 resolution. Since then I have moved lots of sites from HTTP to HTTPS and without exception, the SEO impact was either positive or not noticeable yet.
However, getting this wrong or leaving it for the last minute may well damage your SEO or brand’s reputation, the average user will simply be put off by the NOT SECURE message and most likely move on. to another site
Last week Google sent a warning to all affected websites via the Google Search Console.
To learn more about HTTPS and the blue button in the email, it takes you here.
Below are some text excerpts from the email.
Starting October 2017, Chrome (version 62) will show a ‘NOT SECURE’ warning when users enter text in a form on an HTTP page, and for all HTTP pages in Incognito mode.
The following URLs on your site include text input fields (such as < input type=”text” > or < input type=”email” >) that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, so that you can take action to help protect users’ data. This list is not exhaustive.
The fix is relatively simple if you know what you are doing of course.
Here’s how to fix this problem:
Migrate to HTTPS
To prevent the “Not Secure” notification from appearing when Chrome users visit your site, only collect user input data on pages served using HTTPS.
Need help with moving to HTTPS without messing up your SEO? No matter the size or complexity, I’m probably better placed than most but do not take my word for it, read my client testimonials.
We are proud members of the London Directory