Ever since SSL was announced as a ranking signal that allows sites that have SSL (https) active to be ranked better than those that don't, it is necessary for every site to have SSL.
Of course, in addition to the purchased variants, there is also a free SSL that works just as well as the purchased ones, therefore Google will not make a difference whether it is free or not, it is important that it exists.
At first, it started to mark sites that have a valid SSL and no mixed content as "secure" and later removed it because the fact that a site has SSL is not automatically secure, it's just more secure than those that don't have SSL.
What is a new step towards that is that since December, sites that have SSL (https) but do not have a "green padlock" are loaded with SSL, but some parts such as images, css, js are loaded via links that are HTTP, that link will not be loaded.
Mixed content is blocked not only by Google Chrome, but also by FireFox and Safari.
What does that actually mean?
This means that if you have installed SSL(https) on your site, it will load without any problems, but if, say, the logo on your site is loaded with http://sajt.tld/logo.jpg will not be loaded because it is blocking it.
How do I solve this?
First of all, it is necessary to set the site to https. In our second article we described redirection to https and www.
If you have already activated SSL and you don't have a green padlock, then you have mixed content that chrome will block and then send this one link.
