Checklist For Migrating a Website from HTTP to HTTPS

Home/Insights & Impact/Checklist For Migrating a Website from HTTP to HTTPS

Checklist For Migrating a Website from HTTP to HTTPS

The Google Chrome version 62 that is scheduled for release this October will negatively impact all HTTP web pages a visitor types information into or accesses in Incognito Mode. A “Not Secure” warning will appear in the browser when either of these two scenarios occurs. This is in addition to the same not secure warning which is already appearing for any HTTP site that asks for a password or collects credit card information.

It’s important to note the upcoming change is tied to anything typed into an HTTP page. This latest security measure is one more inducement from Google for all website owners to move from HTTP web pages to SSL-secured HTTPS web pages.

A successful HTTP to HTTPS migration involves more than just installing an SSL certificate. There are a lot of details to consider, and it’s easy for things to fall through the cracks if a disciplined approach isn’t taken. Also, when you convert from HTTP to HTTPS, you effectively change your internet address. This means you should give Google (and other search engines) a permanent change of address in the form of a 301 redirect.

About the Author:

Joe McGrattan oversees strategy and business development for Triple Helix. For nearly three decades, he has been helping companies leverage technology and their data to conduct business more effectively in a digital economy. This includes building strategic-level alliances with non-tech professional services firms whose clients are demanding more information management and technology-related guidance from them. Joe’s blog contributions focus on business-oriented advice to companies on how to take advantage of their data to run smarter, faster, leaner and more securely. He can be reached at joe.mcgrattan@3xcorp.com or found on LinkedIn.