What We Think

Lock up Your Websites

HTTP to HTTPS on Chrome

Google Chrome is setting restrictions on your browser. If you are a Chrome user, you will be frequently notified if a website is not SSL.

ssl certificate secure and not secure

How will this affect me?

If your website does not have a Secure Socket Layer Certificate (SSL Certificate) then this will cause issues regarding rankings and conversions. With Google being the world’s most used search engine, it is essential that you have this certificate straight away! An error message will automatically appear depending which browser you use. This will cause time-consuming problems by interrupting your user journey with you having to repeatedly click to advance and proceed.

Not only that, without having your SSL certificate in place, customers have the potential to bounce off your site meaning that your website will fail to serve its purpose!

your connection is not private google chrome

To the left is what your users will see when they try to access your site. This is not what you want!

If you do see this when trying to access a blog or a website that you know is safe and you can trust then:

Click the advanced section highlighted red,

Then click the next button that pops up below (also highlighted in the picture)








What is HTTP?

HTTP stands for Hypertext Transfer Protocol. This defines how messages are transmitted to the visitor’s browser and which actions the server should take where the website is hosted. What this means is when you click onto a website, your header pings to the server to ask it for information, which then pings back to the header to tell the visitor it is loading, which then pings back to the server to retrieve the data. This process seems long-winded which is why Google says to cache your data to your header. You might think if this data is the header, then isn’t it hackable?

Yes, it is which is why we need an SSL Certificate!

What is SSL?

SSL stands for Secure Socket Layer which protects and encrypts the data that is sent between the servers. A very simple explanation, so in ‘lamens terms’:

The certificate takes the code from the website and puts it into a locked chest, it then pings this chest over to the server, then technically sends the key over after it to decrypt the code.


Always set your headers to secure – HTTPS is very important these days. If Google Chrome is standardising this, organic rankings might also be affected if your website is not secure