Dec 22, 2025
Jordana A.
5min Read
The mixed content warning is a common WordPress error often caused by incorrect Secure Socket Layer (SSL) settings. It indicates that your WordPress website has insecure assets from non-HTTPS URLs.
Resolving mixed content warnings on your WordPress site should be a priority. It can harm the user experience and cause search engines to flag your site as unsafe, potentially affecting your rankings. More severe cases can also make your site susceptible to unauthorized tracking and on-path attacks.
This tutorial will explore the potential causes of the mixed content error in WordPress and how to identify it. Then, we’ll explain three effective methods to fix mixed content warnings: using a plugin, updating website URLs from HTTP to HTTPS, and modifying the .htaccess file.
Download all-in-one WordPress cheat sheet
The WordPress mixed content warning appears when a website serves both secure (HTTPS) and non-secure (HTTP) content due to incorrect SSL settings. To resolve it, you must force WordPress to display all content from secure HTTPS connections, which can be accomplished by using a plugin, updating HTTP links to HTTPS, or modifying the .htaccess file.
Enabling HTTPS/SSL is a common security practice for WordPress websites. Setting up a WordPress SSL certificate lets you encrypt data between your site and visitors for a secure connection.
Many web hosts, including Hostinger, bundle free SSL certificates with their hosting plans. Alternatively, you can buy an SSL certificate from a third-party provider and install it yourself.
Unfortunately, you may encounter WordPress mixed content warnings even with a valid SSL certificate. They occur when an HTTPS site uses an absolute path to load HTTP scripts. An absolute path specifies the precise location of a directory or file. Here’s an example:
http://domainname.com/featured-image.jpg
The easiest way to spot a mixed content error in WordPress is by looking at your browser’s site address bar.
Depending on your browser, a Not secure warning or a broken padlock icon may appear next to your site’s URL with a message saying, “Your connection to this site is not fully secure.”
Using Developer tools in the Google Chrome browser, you can identify which assets are loading with the HTTP connection.
To access it, click the three vertical dots on Chrome’s top menu bar and choose More tools → Developer tools. Alternatively, press Ctrl+Shift+I for Windows or Linux and Cmd+Option+I for macOS.
Open the Console tab in Developer tools to see all the flagged insecure WordPress content on your website.
We will walk you through three possible solutions to debug your WordPress website for mixed content errors, starting with the simplest method.
If you can access your WordPress admin dashboard, install an HTTPS/SSL plugin to fix the mixed content warning. Many of these plugins offer a free version that has features to resolve insecure content issues with a few clicks.
For this tutorial, we’ll show you how to troubleshoot mixed content errors in WordPress using the SSL Insecure Content Fixer plugin:

If an HTTPS/SSL plugin doesn’t resolve the problem, certain URLs might be hard-coded in your WordPress database or files. In this case, you need to replace all the URLs with HTTPS.
If there are only a couple of insecure links, remove them manually. If there are a lot of them, use a search-and-replace plugin to update all the insecure links in your database tables.
Important! Backup your WordPress website before making any changes to your database.
Follow these steps to perform bulk updates in your WordPress database using the Better Search Replace plugin:
Clear browser cache before testing your WordPress website to ensure it loads the latest data.
The final method to address mixed content warnings in WordPress is to force a secure HTTPS connection through the .htaccess file.
This file configures various functions for websites hosted on several web servers, including Apache. One key function is to enforce WordPress to redirect visitors from insecure HTTP connections to HTTPS.
You can find or create the .htaccess file in your website’s root directory, which houses all the WordPress core files.
This tutorial will show you how to modify .htaccess using Hostinger’s File Manager. However, you can also use an FTP client like FileZilla. Here’s how:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]
Header always set Content-Security-Policy "upgrade-insecure-requests;"If the process is successful, users visiting your website through an insecure HTTP link will be redirected to a secure HTTPS connection.

Do I Need an SSL Certificate? How SSL Can Protect Your Site
Types of SSL Certificates: Which One Should You Pick?
How to Fix WordPress HTTP Error When Uploading Images
How to Improve WordPress Security
A mixed content warning can happen after installing an SSL certificate. If left unresolved, it can hurt your SEO and user experience and create vulnerabilities on your website. Therefore, fixing it at the earliest opportunity is essential.
Thankfully, there are three solutions to fix mixed content errors in WordPress:
We hope this article helps secure your WordPress site and provide a seamless experience for visitors. If you have more questions, check our FAQ section or leave a comment. Good luck!
This section answers some of the most frequently asked questions about troubleshooting mixed content warnings in WordPress sites.
There are three ways to fix the mixed content error in WordPress. The easiest fix is by using a plugin. Alternatively, you can manually update HTTP to HTTPS for hard-coded URLs or modify the .htaccess script to force secure HTTPS connections.
Fixing WordPress mixed content warnings is essential. They can harm your SEO and user experience. It can even lead to security vulnerabilities, making your site susceptible to unauthorized tracking and cyber attacks.
Look for a Not secure warning or a broken padlock icon on your browser’s address bar. In Google Chrome, open the Console tab in Developer tools to identify HTTP-loaded assets.
Comments
April 06 2023
Thanks for these tips, but when linking to plugins to help, it might be worth checking the plugins first as WordPress HTTPS (SSL) hasn't been updated for 5 years, has been closed as of June 13, 2022 and is not available for download. Reason: Security Issue!
April 07 2023
Hello there! Thank you for noticing, I've forwarded this to our team and we will replace the plugin listing as soon as possible.