How To Fix Mixed Content Warning & Force SSL / https Across WordPress

Recently I migrated my blog BloggerStop from Blogger to WordPress.

Then applied an SSL certificate (https protocol) across the blog. That means, all the pages of this blog written several years ago, suddenly got moved to a secured https connection from the old-school http connection.

But I wasn’t able to force SSL across the WordPress blog successfully.

What I wanted to see in the browser was a green lock, like this:


But it did not appear instantly, rather I got a warning of mixed content. You can go through that link if you want to know the details of what mixed content is, but essentially mixed-content just means:

There are some insecure objects (images, videos, Javascript or CSS files) present in your secured page/post.

In even simpler English it means, there were some http:// links (mostly images) in my (now) secured https:// posts/pages.

mixed content = https (pages) with non-https content (images, videos etc.)

Links to/from other domains are not considered, only the images or other objects hosted on your domain are considered for this warning.

So, simply by looking at the page-source you can identify all the objects present in that web page (links starting with http://) which are preventing you from forcing SSL / https successfully across your entire website / blog.

The solution to fix this issue is quite easy: check the page source, find out all the non-https objects – and change the url from http to https. That’s it & you will get the green lock.

That sounds easy but it becomes a tedious task if you have tens and hundreds of pages and posts already published on your blog with several hundred images and videos.

So, keep reading this post to find the out the single WordPress plugin that can force SSL across your website in a matter of minutes, eliminating the risk of human error if you do the same task manually.

But before we go the solution, for the beginners, let’s see what an SSL (https) is and why you should use it.

What is SSL (https)

In layman’s language, SSL (Secure Sockets Layer) is a certificate given to a website, which certifies that the content being shared (to and from the users / readers) is safe.

Benefits of using an SSL / https in a Blog

Earlier SSL certificates were mainly used by ecommerce websites and other big companies, where users used to do online transactions. SSL or https protects sensitive data like Credit Card information and banking information safe from hackers.

With SEO coming into the picture and Google’s announcement to rank websites with SSL higher, several Bloggers started using the secured https connections for their blogs to improve their position in SERPs.

And it does make sense, as SEO is all about keeping the users happy and safe. SSL certificates makes your websites trustworthy. So if you ever plan to monetize your blog and/or start an ecommerce shop on your blog, then your customers can confidently complete all the transactions on your website. Thus, improving the conversion rate for you.

Mixed Content Warnings & Issues while Applying https Across WP

Simply replacing http with an https is not enough. You must make sure that there are no errors or warnings being shown in the browsers. One of the most common warnings that we might face while applying an https protocol is that of a mixed-content.

How to Fix Mixed Content Warnings and Get the Green Lock

The solution is Really Simple. Yes, that’s the name of the plugin: “Really Simple SSL“.
Just install it, configure the settings (takes 5-10 seconds) and that’s it. Enjoy the green lock against your website.
To configure the plugin, simply check the boxes against:
1. Auto replace mixed content
2. Enable javascript redirection to ssl


You will find these options under (WordPress Dashboard – Settings – SSL – Settings).

NOTE 1: In case, you are still facing a warning (in the Configuration page of Really Simple SSL), then it would be mostly due to a conflicting plugin (like W3 Total Cache or WP Speed of Light). In that case, go to that plugin and clean the cache and then check it again in the Configuration page under Really Simple SSL. The warning looks like this:


NOTE 2: If the problem still persists, then check the page source and search (CTRL + F) for the non-https elements in your blog. They might be present directly in your web page or within a CSS or JavaScript file or a plugin you are using in your blog. Simply open the files from your File Manager and replace the links with https. That’s it – now you can enjoy all the benefits of hosting a secured blog or website.


A ProBlogger - helping budding entrepreneurs and solopreneurs realizing their dreams to launch & make their websites and blogs popular and successful :)

Leave a Reply

Be the First to Comment!

Notify of