With cyber crime becoming an ever increasing concern across the globe, it’s important for you to make sure that your WordPress website is set up properly to avoid driving away visitors and incurring penalties from Search Engines. Almost all browsers today “punish” websites that do not have fully functional SSL certificates with ominous notices to visitors. Should this happen to your site, there is every possibility that you will begin losing much needed traffic.
Can I get a mixed content error when my site has a valid SSL certificate?
This is a question that is often asked by people out there. Despite the fact that you may have a valid SSL certificate, you may find that your website still triggers mixed content errors on such browsers as Mozilla and Google Chrome. So, the answer is, yes, you can get mixed content errors even if you have a valid SSL certificate on your website.
What causes Mixed Content Errors?
So, what is it that causes mixed content errors on websites? The major issue, for most of the websites that are out there, is that they still retain HTTP links on their sites. When we encountered mixed content errors on this website, it was because we had some affiliate links from Commission Junction and from Amazon that appeared to be HTTP and not HTTPS.
How to fix mixed content errors in WordPress
In WordPress, mixed content errors can be fixed by taking the following simple steps;
- Download and install the SSL Insecure Content Fixer plugin
- Activate the plugin
- In the backend of your site, hover your cursor over Settings and then click on SSL Insecure Content
- Setup the plugin
Which settings should I use?
When we installed the SSL Insecure Content Fixer plugin on our own website, we discovered that the “Simple,” setting did not solve the problem. We then tried the “Content,” setting, which did the job for us.
Now our website is no longer triggering the Mixed content error when opened using any of the above mentioned browsers. We hope this quick fix for the mixed content errors in WordPress will help resolve the issue on your own WordPress website.