Effective July 2018, Google’s Chrome browser will mark non-HTTPS sites as ‘not secure’
After years of pushing for ‘secure by default’ websites, Google will identify insecure sites in the Chrome browser beginning mid-Summer.
Have you ever searched on a keyword search term only to see a page displayed as “your connection is not private?” Well, Google algorithm is now blocking non-https websites in their Chrome browser.
If you are the search user you most likely will not proceed and go elsewhere.
If you are the owner of the website, well you guess it you will see a drop off on website traffic and rankings.
It’s almost 2019. Ready?
You need to maximize your SEO efforts if you want to succeed online. Let’s face it. If you don’t, your business will be left behind. SEO is a top priority for marketers.
Over 70% of clicks go to organic searches that rank on the first page of Google.
Ranking on the first page of Google can be the deciding factor in making your business thrive online. You probably already know that, right?
These websites are confusing search users when they assume they have landed on a website that was safety. The image below shows what they see when the website page is displayed.
July is shaping up to be a big month for Google. Earlier this month, the company announced its Speed Update set to roll out in July, and today announced it will then also mark all sites that have not migrated to HTTPS as “not secure.”
This move will coincide with the release of Chrome 68 and will look like this in a user’s browser:
Google has been pushing webmasters to make the change to non-secure websites a for years now – including hinting at small rankings boost to further drive the shift. The campaign has proved successful. According to their blog post:
- Over 68% of Chrome traffic on both Android and Windows is now protected
- Over 78% of Chrome traffic on both Chrome OS and Mac is now protected
- 81 of the top 100 sites on the web use HTTPS by default
Depending upon the size of a site and scope of the project, a migration from HTTP to HTTPS can be quite an undertaking. Check out the resources below for in-depth guides to making this change on your or your client’s sites, along with resources for validation and dealing with mixed content issues.
- HTTP to HTTPS: An SEO’s guide to securing a website
- A comprehensive guide to SSL certificates
- Test your website here.
Share website that you’ve run into with this problem @mmgtweets.
By Michelle Robbins, former SVP Content & Marketing Technology, overseeing editorial direction as Editor in Chief for Third Door Media’s digital publications.