+8801744383834

24/7 Customer Support

WhatsApp +8801744383834

July 2018: Chrome will name non-HTTPS sites “unsafe”

Content

July 2018: Chrome will name non-HTTPS sites “unsafe”

 

Last Updated June 29th, 2018 at 02:26 pm
After years of pushing for “safe by default” websites, Google will identify unsafe sites in the Chrome browser starting in mid-July.

Months passed and here we are: July arrived
July is shaping up to be a great month for Google . In early February, the Australia Business Phone List announced that its speed update will be released in July. In addition, it announced that it will mark all sites that have not migrated from HTTP to HTTPS as “not secure.”
Chrome July 2018

Chrome HTTPS: successful campaign
Google has been pushing webmasters to make the switch to unsafe websites for years. The campaign has been successful. According to the Google blog post:

Australia Business Phone List

Over 68% of Chrome traffic on Android and Windows is now protected.
More than 78% of Chrome traffic on Chrome OS and Mac is also protected.
81 of the top 100 sites on the web use HTTPS by default.

Guides for making the transition
Depending on the size of a site and the scope of the project, a migration from HTTP to HTTPS can be hard work. You can check out the resources below for detailed guides. They are in English, but they can be used to make this change on your or your client’s sites, along with resources for validation and handling of mixed content issues.

HTTP to HTTPS: An SEO Buy
Betting Email List Guide to Protecting a Website | Guide written by Patrick Stox, April 14, 2016, for Search Engine Land.
A Complete Guide to SSL Certificates | Guide written by Stephanie LeVonne, Jan 4, 2017, for Search Engine Land.
Some insecure resources can be upgraded to HTTPS | When Google announced this update, in February 2018, they uploaded this guide to Developers.Google

Leave a comment

Your email address will not be published.