Mixed content error in WordPress is for incorrect HTTPs/SSL settings. Are you seeing the mixed content error in WordPress? Often it doesn’t affect your website’s functionality, but it can have adverse effects on your website’s SEO & user experience. It’s time to fix that. This tutorial tells you how to do it.

Many users believe that SSL integration secures a website. However, SSL only protects the private data of a user. It is highly recommended to add HTTPS / SSL in WordPress. Because after July 2018 Google Chrome will mark all http versions of website as insecure.

What is Mixed Content Warning in WordPress?

When a site doesn’t fully protect or secure all content, a browser will display a “mixed-content” warning. Mixed content occurs when a webpage containing a combination of both secure (HTTPS) and non-secure (HTTP) content is delivered over SSL to the browser.

SSL & Non SSL Compare

If you have correctly implemented SSL on your website. Then you will see a green padlock icon next to your website’s URL in the browser address bar.

On the other hand if your HTTPs/SSL settings are not properly setup. Then you will see an info sign or a broken padlock icon in the address bar.

How to find the non-HTTPS contents?

One of the he best way to avoid all kind of mixed content issues is to serve all content via HTTPS instead of HTTP. You can easily search for the mixed content by searching for HTTP elements directly via your source code.

  • You Need to open the source code of any page
  • Using a search function search for “src=http” look for resources such as images, JavaScript, and links that are being called over a non-secure (HTTP) connection.

Fixing HTTPS mixed content

We’ll go through several strategies to fix the HTTPS mixed content warning on a WordPress site. Follow the simple steps below to fix your WordPress mixed content warnings. This assumes you have already done the following:

N.B. Remember, every time you apply a fix, you need to clear the cache from the server & the browser then reload your site to check whether the fix is working.

01: Turn ON Cloudflare Automatic HTTPS Rewrites

Cloudflare makes the Internet work the way it should. Offering CDN, DNS, DDoS protection and security, find out how we can help your site.

If you use Cloudflare, you can use its Automatic HTTPS Rewrites feature to make some of your site’s resources available via HTTPS. You have to go the Crypt section on your Cloudflare dashboard, and switch the Automatic HTTPS Rewrites feature ON.

Cloudflare Automatic HTTPS Rewrites

You are all set, If applying this method solves your mixed content warning problem. Or you can follow other methods described in this post. Or, if there are only a few issues, you can fix them manually as well.

02: Use Really Simple SSL Plugin

First you need to browser to your WordPress website Admin Panel and enter your admin credentials to log in. There are several ways of fixing the Mixed Content issue. But I’ll show you the simplest and easy way fix mixed content error.

Go to the right side admin menu and click Plugins. Next, click Add New and Search for the Really Simple SSL plugin.


Install and activate the plugin. Once the plugin is activated, it will automatically fix the mixed content issues for all the URLs on the website.

Now that the plugin has resolved the Mixed Content issue, it is easy to verify that your WordPress website no longer faces this issue.

03: Using The Manuel Method

Previously in this article, we discussed the process to identify the HTTP base contents. For manually fixes, you need to find which contents are loaded via non-HTTPS sources. Use your browser developer tools, and edit the hard-coded URLs to put HTTPS into them.

Hopefully this will help you to solve the issue. If not, you should talk someone who expert. You also can post on the WordPress.org support forum.

Wrapping Up!

Ignoring the mixed content warning is a bad idea. We hope you will find this post helpful while moving from HTTP to HTTPS. Please share your experience and thoughts via comments. Thanks for being with Themepiko!

Leave a Reply