Chrome Update 62: How to switch from HTTP to HTTPS in 24 hours (more or less)Chrome Update 62: How to switch from HTTP to HTTPS in 24 hours (more or less)

Chrome Update 62: How to switch from HTTP to HTTPS in 24 hours (more or less)

Written by Tania Varga on 26th Oct 2017

You may be wondering how the latest Chrome update will impact your website or your rankings. I’ve been asked about the implication of the latest Chrome update a few times over the last couple of weeks by clients and companies in the process of reviewing their digital strategies.

We have previously covered moving your website to HTTPS and purchasing a SSL certificate so read this article first if you are not sure what impact the HTTPS move can have.

Our web development team and I came up with a useful guide for marketers to advise those concerned about the update on how to start the process of switching from HTTP to HTTPS to ensure their website doesn’t appear in Chrome as “Not Secure”:
Chrome Update 62Source: Chromium Blog

Every website is different, but the following steps should get you started:

  1. Get a security certificate and install on the server (3 hours)

    • Generate CSR (Certificate Signing Request) on server
      • Look for SSL Manager in cpanel
    • Submit CSR to certificate authority
    • Receive and install the issued SSL (Secure Sockets Layer) certificate
      • You can usually do this by contacting your host directly

    (Certificate may incur a fee, depends on the hosting package you are on)

  2. Update any references to HTTP on the site to HTTPS (1 – 8 hours)

    • Update header scripts and CSS
    • Update canonical tags
      Update any OG tags
    • Update any plugins/modules/add-ons
      Change any CMS-specific settings by following the CMS migration guide
      Make sure any external scripts that are called support HTTPS
  3. Add rewrite to forward all http:// to https:// (0.5 hours)

  4. Update sitemaps to use HTTPS versions of URLs (1 – 10 hours)

    • Update robots.txt with new sitemap
  5. Crawl the site with an SEO spider tool like Screaming Frog to ensure there are no broken links (1 – 4 hours)

  6. Check everything is fine using Search Console (1 – 2 hours)

  7. Update default URL in analytics platform (0.5 hours)

If you want to read more about the Chrome Update 62, @chromiumdev is the place to look!

Get in touch with our team if you have any questions on making the move to HTTPS; Syed and Phil will be more than willing to help.

Read More