Like most things in the world, even Google Chrome needs to be updated on a regular basis.
The reason as to why Google Chrome is updated at such an accelerated rate is due to the numerous amounts of security threats that the web giant faces on daily bases.
Most of the updates that Google chrome goes through are kept close to heart as they are both new security features and updates to the browser’s security network frame, or these updates are new changes to the search engine optimization algorithms to ensure that webmasters are making use of correct SEO practices and that websites are not becoming too “spammy”, this ensures that Google can give its users the best results possible without having to dilute their brand.
The one thing that many people fail to realize is that Google is very image-driven, which is not a bad thing. It just means that every webmaster that decides to join Google’s search engine will be held to a very high standard of practice. Those who look after their websites and ensure that they uphold the Webmaster Guidelines will be rewarded.
The ways that Google rewards its webmasters is by allowing their sites to increase in ratings and by increasing that websites standings within the Google search results in theindex.
To stop people from manipulating this reward system Google releases many updates which they tell us these famous lines, “We are releasing a new update” and that is all the information that we receive. The reason why Google is so vague with their updates and what is in the updates is once again to stop webmasters who make use of malpractice, from finding a way to “trick” the system and not get caught by Google’s algorithms.
What is update 62?
Moving on, as of the 1st of October 2017, the most recent updates that Google has released is Google Chrome update 62.
The main aim of Google chrome update 62 is to target websites which are still using HTTP and not HTTPS.
Why does this matter?
In January Google released its chrome update 56 where they forewarned that all websites would have to start to begin to integrate their sites from HTTP to HTTPS and now we are beginning to see Google crack down on webmasters who have not started to integrate their sites across.
The way that Google is punishing these webmasters is by placing a “not secure” tag on their websites when a user is browsing the site.
This has a massive negative effect on both the user and the SEO algorithms, when they pick up this tag they will immediately punish the site, the users will often leave the site and the algorithms will decrease the credibility of the page which will drop the pages rank in the search index.
What does Google have to say?
Wanting to know more about what Google was trying to achieve by implementing its update 62 we checked the Google Security Blog.
Here they stated that their journey to ensure that this update successful started in January 2017 with the release of their update 56.
Update 62 will have Chrome showing a “Not Secure” warning in two additional situations from the ones that already display this warning.
These new factors are;
- When any user enters any data on any HTTP page
- All HTTP pages that any user visits in Incognito mode.
The warnings will like the following;
The main reason why Google is now implementing stricter algorithms in their updates is that they believe in protecting their client’s data, as Google does not believe that only payment details should be kept safe, rather all of their client’s information should be kept safe.
What is next after this update?
The future plan for Google is to not just target sites that require its users to enter data but to target all websites which are still making use of HTTP.
The reason behind the massive action on sites that make use of HTTP is that HTTP browsing is not private on any network, meaning that if you are connected to a work or public network you can expose everybody and the entire network to a cyber-attack.
Here is how you can move to HTTPS.