Return to site

Take steps to secure now with HTTPs

Beginning July 2018, Google will mark non-HTTPs site as non-secure

· Services

Got GDPR done? Now think about HTTPS.

Earlier this year Google started gradually marking sites using HTTP as not secure. What a surprise when I came across very familiar sites marked this way. Here's what it looks like if you're wondering what I'm talking about.

In Internet Explorer it might look like this:

Trust is a big issue with the Internet so Google has been encouraging people to move to HTTPs. The problem is that it can cost money, it takes time to do, and your site is typically down for some time too. However, HTTPS is becoming cheaper and easier to integrate so Google now wants everyone to get to it and they're setting a deadline too.

ImpulseHub and Strikingly Websites

Strikingly started supporting HTTPS by default last year. All ImpulseHub designed websites that went live this year (or at the very end of last year) are good to go. If you're in this category, your site will already be on HTTPs.

If you are still on HTTP you need to move to HTTPS to avoid getting nasty 'site not secure' messages appearing on your website. Google is giving people until this July to get moved or else face the consequences. If you're not moved by then your visitors will see 'not secure' on your site. It's not clear whether this will be the 'not secure' images above or just 'not secure' in the browser (see below).

Either way, the message is clear. Google is serious about this and they want you to move. Plus, you don't want visitors seeing 'not secure' when they visit your site.

Note: all new websites developed by ImpulseHub include HTTPS support as standard.

Checking your site

If you want to check to see if HTTPS is on your site or not, open your site up in a browser and check the address shown. Secure sites will look like the address in the bottom image below. Sites that are NOT currently HTTPS will look like the address on the top.

Upgrading to HTTPS

If you need to upgrade to HTTPs, you should:

  1. Schedule a time for this when it will have the least impact to your business. Perhaps this is early morning or late in the evening.
  2. Notify your clients via Facebook, email or perhaps your website that there will be a short outage to accommodate this. You want your customers to feel safe and secure when they browse the web. 
  3. Upgrade to HTTPS (see below if you're an ImpulseHub client)
  4. Thank customers after the upgrade (through Facebook, email or perhaps your website). Let them know your upgrade is complete and your site is secured with the latest technology.

Note that upgrading to HTTPS is a once off change. It is not something that is done often because the protocol is something that is agreed to and standardized by International committees that include the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C).

If you are not an ImpulseHub client, check with your hosting provider about getting your site upgraded to HTTPS. They should be able to advise you on how best to do this.

Makes Sense

Other than the stick of getting people to HTTPS by telling visitors that say your site is not secure, there is a carrot too. Your site will be given preference in terms of SEO. #smallFavours

Request Upgrade

If you're an ImpulseHub client and need to upgrade your website to HTTPS, there is a €50 charge to do this.

  • Send your request to 
  • Use the link below to schedule your upgrade. 

We will try to accommodate you at a time which best suits your business. Please note that your site will most likely be down for a few hours during the upgrade. You will be notified when it is complete.

Questions can be sent to If you are an ImpulseHub client and need an upgrade, you can secure your site now by scheduling this below.

Google updates on HTTPS:

  • In "A secure web is here to stay" (8 Feb 2018), Google says they will mark all non-HTTPS as non-secure from July 2018.
  • In "Evolving Chrome's security indicators" (17 May 2018) Google says that they’ll soon start marking all HTTP pages as “not secure”, and step towards removing Chrome’s positive security indicators so that the default unmarked state is secure.
  • Timeline on the Chromium Project here includes dates on how Google will make the web more secure.
And for those who are comfortable with tech and are on Wordpress (or a platform where HTTPS is not standard), this link (which shows how to get setup using Cloudflare for free) might be useful: HTTPS Is Easy
All Posts

Almost done…

We just sent you an email. Please click the link in the email to confirm your subscription!

OKSubscriptions powered by Strikingly

Author Name