Apr 18 2018
This blog is secure
In order to protect my visitors’ data, increase loading speed, and move up the ranks on Google, I recently converted this blog from an unsecured http://… site to a secure https://… site. What happened since, however, is not exactly as expected.
The site does not load any faster, the number of daily visitors has been cut by a factor of three, and some readers have told me that they are getting warnings from Google when connecting.
According to the company that hosts my blog and sold me my security certificate, the site is clean. To make sure it stays that way, I have also beefed up its security with tools from WordPress.
According to the hosting company, it may take four to six weeks for Google to notice that the site is safe and stop emitting the warnings.
Mark Graban
April 19, 2018 @ 5:43 am
I’m not getting any security warnings when viewing the site with Google Chrome.
Is traffic 1/3 of what it used to be?
I switched leanblog.org over to SSL and didn’t have similar issues. Mine is “self hosted WordPress” (through a hosting company).
Good luck getting things sorted out.
SSL is definitely the way to go. Hopefully the issues are just temporary for you.
Michel Baudin
April 19, 2018 @ 8:07 am
Thanks for responding. It’s good to hear that *someone* is not having a problem…
Christoph Roser (AllAboutLean) told me he had the same problem, and that it was due to plugins. Some plugins still used “http” links after the site had been converted to “https,” which Google does not like.
As usual in WordPres, there are a few plugins that claim to solve this problem. I installed one of them.