What are SVGs and why should developers be using them?
28th November 2017
January 13th 2017
Google’s own web browser, Google Chrome, will be releasing an update towards the end of January 2017 which will mark websites that have no SSL certificate (also commonly known as HTTPS) as “Not Secure”.
The websites that will be effected will be those which use a password field (typically used for a user login area) or/and credit card details. This is part of a long-term approach from Google to make the web a more secure place, and we should expect the other major web browsers (Internet Explorer / Edge / Firefox / Safari) to follow suit.
It’s also worth noting that Google already consider website security in their ranking algorithm.
SSL stands for Secure Socket Layer. It ensures that data sent from one computer to another has been encrypted. For example, the data has been secured between the visitor’s web browser to the websites server making any other computers/servers that the data might pass through harder to understand.
When a website has an SSL installed, there are some notable differences to the web browser that lets the user know that they are in a secure environment. This includes the recognisable padlock icon, and the https:// text in front of the domain. See below for an example:
If these websites do include the SSL certificate by the time Chrome 56 is released the visitor will see the “Not Secure” notice. See below for an example:
The result of this could be a lack of confidence with the visitor, and the website could see a drop off in leads/sales because the visitor is reluctant to share their personal details.
This is just the first step for Google, as they plan to show “Not Secure” warnings for all websites that don’t include SSL in the future; regardless of whether they have password fields / credit card fields or not.
If you would like to know more information on the matter you can read the official statement from Google:
If your website needs an SSL certificate installing, we can help – so get in touch!