“Why is my site saying it’s not secure?” A client may ask this even after you install an SSL certificate. A browser warning such as “Your connection to this site is not fully secure.” can point to resources still requested over HTTP.
In this example, the site has mixed content: images, scripts, or stylesheets requested over HTTP instead of HTTPS.
What Is Mixed Content?
Mixed content is when a website served over HTTPS loads resources like images, scripts, or stylesheets over HTTP. This weakens security, as attackers can intercept unprotected elements, leading to compromised data integrity, and potential security vulnerabilities.
There are two main types of mixed content.
- The first is passive mixed content, which includes elements like images and videos. These do not directly impact the site’s functionality, but they still trigger security warnings in browsers, eroding visitor trust.
- The second type is active mixed content, which includes scripts, iframes, and stylesheets. These pose a greater security risk because they have the potential to be manipulated, leading to compromised site behavior or even malicious attacks.
You want neither.
Why Does Mixed Content Happen?
An SSL certificate does not update every resource URL in WordPress. Theme files or plugins may still contain hardcoded HTTP addresses.
Third-party scripts may request resources over HTTP. A migration to HTTPS can also leave old URLs in links, images, and scripts. Check WordPress’s site URL settings for HTTP references as well.
New content can reintroduce HTTP references, so check the resource URLs when publishing it.
How to Identify Mixed Content
Open your browser’s Developer Tools by pressing F12 or right-clicking and selecting “Inspect”. Check the console for mixed content warnings and the resource URLs they identify.
Another way to detect mixed content is by using an online scanner. Tools like Why No Padlock, SSL Labs’ SSL Test can quickly analyze your site and point out any non-secure elements that need to be addressed.
Fixing Mixed Content Issues
Once you have identified the problem areas, the next step is fixing them. The first thing you should check is your WordPress settings. Navigate to the General Settings page, and make sure that both the WordPress Address (URL) and Site Address (URL) fields are using a URL that starts with https://, not http://.
If they are not, updating those two values will resolve a large portion of mixed content issues. And it’s as easy as changing that URL to the https:// version and hit Save Changes.

If old HTTP URLs remain in the database, locate the affected references before replacing them.
Those old HTTP URLs could be leftover from when your site was running under HTTP, for instance. A plugin like Better Search Replace is designed to help with this, allowing you to swap out all HTTP references with HTTPS in one go.
Note: make sure you back up your database before you change things in your database with this plugin.
For those still facing issues, enabling automatic HTTPS rewrites is another option. Some plugins like Really Simple SSL offer this functionality, ensuring that any lingering HTTP requests are redirected to HTTPS before they cause a problem.
When you end up having to use a plugin like this, this generally means your theme or plugin have a HTTP version of an internal URL to an asset, for instance. You may need to manually update theme files or plugin configurations that contain hardcoded HTTP URLs.
External scripts (from plugins) can be trickier to manage. If a third-party service still loads over HTTP, you have limited options. You can reach out to the provider and ask if they support HTTPS, or find an alternative secure service to replace it. If neither option is possible, then consider whether you truly need that external resource on your site.
The Problem with Really Simple SSL
Many site owners turn to Really Simple SSL as a quick fix for mixed content issues. While it can be useful for enforcing HTTPS across your site, it comes at a cost. Plugins like this work by dynamically rewriting insecure URLs on every single page load, adding overhead to your site’s performance.
Resolve the HTTP references at their source where possible, so the site does not depend on runtime rewrites.
The right approach is to update all URLs directly in the database, theme files, and plugins. This ensures that your site is clean, fast, and not dependent on unnecessary processing. Solving mixed content issues at the source is always the better long-term strategy.
Preventing Mixed Content Issues
New content or configuration changes can reintroduce mixed content. Include these checks in your publishing and maintenance work:
- Always make sure that all resources you add to your site use HTTPS.
- When embedding third-party resources, verify that the service supports HTTPS before integrating it.
- Regularly audit your website and scan for mixed content issues before they become a problem.
- Only use
https://versions of URLs.
Review new content, plugins, and scripts before they go live, then scan the published site for mixed content.