WordPress SSL mixed content errors appear when your site has an SSL certificate installed but is still serving some resources — images, scripts, stylesheets — over the old insecure HTTP connection. The result is a broken padlock or "Not Secure" indicator in the browser address bar, even though your website investment includes a valid SSL certificate. The fix is straightforward once you know which of the five causes applies to your site, and most SA WordPress owners can clear the warning without calling a developer.

This is one of the most common issues that surfaces after a South African hosting provider enables free SSL on an existing WordPress site. The certificate activates, but years of hardcoded http:// URLs remain in the database, theme files, and page-builder layouts. Understanding the cause first saves you from installing the wrong fix and wondering why the padlock is still broken. If you are also thinking about what a properly secured, well-maintained site costs to run, the annual website running cost guide breaks that down too.

Quick Answer

WordPress SSL mixed content errors occur when an HTTPS page loads one or more resources over HTTP. Active mixed content (scripts, stylesheets, iframes) is blocked by default in most modern browsers — including current Chrome, Firefox, and Safari — though behaviour can vary by version; passive content (images, video) is auto-upgraded to HTTPS or blocked if unavailable. The fix depends on what is causing the problem: update your WordPress URL settings first, then use a plugin or database search-replace tool for hardcoded URLs, and edit theme files or replace external resources for anything the plugins cannot reach.

Is the padlock broken on your WordPress site?

Send us your site URL and we will identify which resources are loading over HTTP and tell you the fastest fix for your setup — no obligation.

Get a free mixed content check

What Causes WordPress SSL Mixed Content Errors

A mixed content error means your HTTPS page is requesting at least one resource from an http:// address. The certificate is not the problem — the hardcoded URL pointing to an insecure resource is. There are five common sources of these hardcoded URLs on a WordPress site.

SourceWhere It LivesTypical Trigger
WordPress URL settingsSettings → GeneralSSL enabled but WordPress and Site Address still set to http://
Database contentPosts, pages, widgets, custom fieldsMigrated from HTTP — old absolute URLs never updated
Page builder dataElementor/Divi tables, generated CSSBuilder stores HTTP URLs in its own layout data, outside standard post tables
Theme and plugin files.php, .css files on the serverHardcoded asset paths written with http:// instead of https:// or a protocol-relative URL
External embedsEmbedded maps, fonts, scriptsThird-party resource served only over HTTP (rare post-2022 but still encountered)

In South Africa, the most common trigger is a hosting provider enabling a free Let's Encrypt SSL certificate on an existing WordPress site. The certificate activates immediately; the database full of http:// URLs does not update itself.

This is why the WordPress HTTPS mixed content warning appears on sites with a valid certificate — the certificate is fine; the content references are not. Most SA shared hosting providers — HOSTAFRICA, GP Hosting, Truehost and others — now include free SSL with every plan, so this scenario is increasingly common for businesses migrating older sites.

Active vs Passive Mixed Content — Why the Distinction Matters

Not all mixed content produces the same browser behaviour, and understanding the difference tells you how urgently to act.

TypeExamplesBrowser Behaviour (2026)Site Impact
ActiveJavaScript files, CSS stylesheets, iframesBlocked by default in most modern browsers — resource does not loadBroken layouts, broken forms, broken checkout flows
PassiveImages, video, audioAuto-upgrade attempt to HTTPS; blocked if HTTPS version unavailableMissing images, broken padlock, trust warning in address bar

Why active mixed content is the emergency: A blocked script means a button may stop working, a form may not submit, and a payment element may not render. Web.dev's published definitions of mixed content (the accepted definitional baseline) describe active mixed content as allowing an attacker who intercepts the HTTP request to take full control of the page — which is why most modern browsers block it by default. Passive mixed content is a trust problem; active mixed content is a security and functionality problem.

How to Find Mixed Content Warnings on Your WordPress Site

Before you fix anything, confirm exactly which resources are loading over HTTP — otherwise you may clear one warning and miss three others. The tools below make this straightforward; you do not need to be a developer to use them.

Method 1 — Browser DevTools (free, most accurate): Open Chrome or Firefox, navigate to the page displaying the mixed content warning WordPress is generating. Right-click anywhere → Inspect → Console tab. Reload the page. Any warning displays the exact file URL loading over HTTP. Copy those URLs — they tell you exactly where to focus your fix.

Method 2 — Why No Padlock scanner: Visit whynopadlock.com, enter your URL, and the tool lists every HTTP resource it detects. This is useful if you prefer not to use DevTools, or need a shareable report.

Check more than the homepage. A mixed content warning WordPress flags in the browser often hides on specific page types — old blog posts with embedded images, forms, WooCommerce checkout pages, or login screens. Run the diagnosis on each template type before concluding the problem is solved.

Method 3 — Browser Security tab: In Chrome DevTools, the Security tab lists whether the page is secure and identifies certificate details. The Issues tab (DevTools → Issues) logs both active and passive mixed content with file paths and suggested fixes.

Which Fix to Use — WordPress Mixed Content Error Decision Table

The right fix depends on three constraints: what is causing the problem, how many URLs are affected, and what server access you have. Run through the table from top to bottom — the first row that matches your situation is your starting point.

SituationRecommended FixTechnical level
WordPress Address still shows http:// in Settings → GeneralUpdate both URLs to https:// in Settings → General; saveLow — any WordPress admin can do this
A handful of isolated pages/posts with HTTP imagesEdit each page/post in the WordPress editor — update the image block URL directlyLow
Site-wide database URLs (many posts, widgets, custom fields) — no SSH accessInstall Better Search Replace → dry run → replace http://yourdomain.com with https://yourdomain.com across all tablesMedium — requires admin access and a backup first
Site-wide database URLs — SSH/WP-CLI access available (developer or managed host)Run: wp search-replace 'http://yourdomain.com' 'https://yourdomain.com' --all-tables --dry-run first, then without --dry-runMedium — requires SSH and WP-CLI
Page builder (Elementor, Divi) content showing HTTP URLs after database replaceUse the builder's built-in "Regenerate CSS" or URL replacement tool; or re-save templatesMedium
HTTP URLs hardcoded in theme PHP or CSS files (confirmed via DevTools)Edit the child theme file directly — replace http://yourdomain.com with https:// or a relative path starting with //High — edit files via SFTP or the theme editor; use a child theme
External resource (font, map, embed) only available over HTTPFind the HTTPS version of the resource, update the URL, or remove the embedMedium
Mixed content persists after all of the aboveInstall SSL Insecure Content Fixer (Simple level first) as a runtime mitigation while you locate remaining sourcesLow — plugin install only

Always back up before touching the database. Better Search Replace and WP-CLI both handle WordPress serialized data safely (unlike a raw SQL find-and-replace), but a backup means any mistake is recoverable in minutes. Most SA cPanel hosts offer one-click backup via Softaculous or Jetbackup — take one before you run any search-replace operation.

Step-by-Step: Four Ways to Clear the Broken Padlock

Step 1 — Update WordPress URL settings

This should always be the first action. In your WordPress admin, go to Settings → General. Confirm both the WordPress Address (URL) and Site Address (URL) fields begin with https://. If either still shows http://, update it, save, and reload the site. This alone resolves the warning on many freshly SSL-enabled sites where the certificate was added after installation.

Step 2 — Database search-replace for hardcoded URLs

If the warning persists after Step 1, your database contains posts, pages, or widget text with hardcoded http://yourdomain.com URLs. Use Better Search Replace (available free on WordPress.org, with 1,000,000+ active installations):

  1. Back up your database first (cPanel → Backup Wizard, or your host's backup tool)
  2. Install and activate Better Search Replace (Tools → Better Search Replace)
  3. Search for: http://yourdomain.com (your exact domain, not a wildcard)
  4. Replace with: https://yourdomain.com
  5. Select all database tables
  6. Tick Run as dry run first — review the count of replacements before committing
  7. Untick dry run, run again to execute
  8. Clear all caches (WordPress cache, CDN cache, browser cache) and retest

If you have SSH access, WP-CLI achieves the same result and is the preferred method on developer or managed-hosting environments:

WP-CLI command (dry run first):
wp search-replace 'http://yourdomain.com' 'https://yourdomain.com' --all-tables --dry-run

Execute when dry run output is as expected:
wp search-replace 'http://yourdomain.com' 'https://yourdomain.com' --all-tables

Do not run a raw MySQL UPDATE or text-editor search-replace on the database file. WordPress stores some values as serialized PHP arrays. A raw find-and-replace breaks the array structure silently — forms stop working, widgets disappear, page builder layouts become unreadable. Always use Better Search Replace or WP-CLI, which are serialization-aware.

Step 3 — Add an HTTPS redirect in .htaccess

On Apache-based hosting (the standard on most SA shared hosting), add a permanent redirect to ensure all HTTP traffic is sent to HTTPS. Open your .htaccess file (in the WordPress root directory) via cPanel File Manager or SFTP, and add these lines above the WordPress rewrite block:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

This redirect prevents the browser from making the initial HTTP request in the first place — reducing the chance of any cached HTTP URL reaching a visitor.

Step 4 — Handle page builder content

Elementor and Divi store layout data in their own database tables and generate CSS files separately. After running the database search-replace, regenerate the builder's CSS cache: in Elementor, go to Elementor → Tools → Regenerate CSS and Data. In Divi, Divi → Theme Options → Builder → Clear CSS File Cache. Check the affected pages in DevTools again afterwards.

Step 5 — Fix theme and plugin file references

If DevTools shows an HTTP URL that points to an asset in your theme (e.g. http://yourdomain.com/wp-content/themes/yourtheme/style.css), the hardcoded URL is in a PHP or CSS file — not the database. Edit the relevant file via SFTP or the WordPress Theme Editor (Appearance → Theme File Editor). Replace the absolute http:// URL with either the https:// version or a protocol-relative URL (//yourdomain.com/...). Always make changes in a child theme, not the parent, to prevent an update from overwriting your fix.

Not sure which fix applies to your site?

Share your URL and we will identify the source of the warning and walk you through the right fix for your hosting setup — no obligation.

Get a site diagnosis

What Plugins Cannot Reach — and What to Do Instead

Plugins like SSL Insecure Content Fixer and Really Simple Security work by intercepting the page output and rewriting HTTP URLs before the browser sees them. This resolves the visible warning without touching the underlying source. It is a useful emergency measure, but three categories of mixed content sit outside what a plugin can reach.

ProblemWhy the plugin cannot fix itWhat to do instead
HTTP URL hardcoded in a theme PHP filePlugin rewrites HTML output, not PHP source filesEdit the file via SFTP or Theme Editor (child theme)
External resource that genuinely does not support HTTPSPlugin cannot change the third party's server configurationReplace with an HTTPS-capable alternative or remove
Server-level redirect loopPlugin-level redirect conflicts with server redirect → loopUse one redirect method only: server (.htaccess) OR plugin, not both

Plugin = mitigation, not a permanent source fix. SSL Insecure Content Fixer (100,000+ active installations on WordPress.org) is reliable as a mitigation layer, but if the underlying database still contains thousands of HTTP URLs, a caching conflict or a plugin update can expose them again. The database search-replace is the right way to fix mixed content WordPress sites carry from an HTTP migration; the plugin buys time while you do it.

Why South African Businesses Choose Growth Pulse Media for Web Design and Technical Fixes

SSL configuration issues — mixed content warnings, redirect loops, certificate mismatches — are among the most common technical problems SA businesses encounter after moving to a new host or enabling SSL on a legacy WordPress site. Growth Pulse Media's web design work is built and maintained in-house, by the same people who set up the site. There are no junior developers handed a ticket and a brief; when a problem surfaces on a site we manage, the same operator who built the architecture resolves it.

Dirk van Greuning, who founded Growth Pulse Media after scaling a large South African ecommerce business, applies the same operator logic to technical problems that he does to commercial ones: find the root cause, fix it at the source, and build the system so it does not recur. Our web design service covers not just the build but the ongoing technical health of the sites we manage — including HTTPS configuration, database integrity, and plugin hygiene.

We work with a deliberately limited client load to maintain the level of attention that catches these problems before a visitor does. If you are evaluating what a properly built and maintained WordPress site costs, the website cost South Africa guide covers the full picture — from build to annual maintenance.

Who This Is NOT For

Not for sites still running on HTTP with no SSL certificate installed. This guide assumes your SSL certificate is active and valid. If your hosting control panel shows no SSL installed, enable Let's Encrypt via cPanel first — most SA hosting providers include it free — then return here to clear the remaining mixed content.

Not for businesses who need to make no changes to their site. Every fix method in this guide requires at minimum an admin login to WordPress, and the database-level fixes require a backup, an installation, and a deliberate search-replace run. If your preference is for someone else to handle all technical work, the right move is to brief a developer or agency, not to follow a self-serve guide.

Not for WooCommerce stores with complex checkout flows who want to run the database fix without staging first. A search-replace on a live WooCommerce database that is actively processing orders is risky. Clone the site to a staging environment, run and validate the fix there, then replicate on production. Most managed WordPress hosts (including Kinsta and WP Engine, which have SA-facing clients) include staging as standard.

Not for sites where the mixed content source is a legacy third-party embed that cannot be updated. If your site loads a widget, payment frame, or data feed from a third party that only supports HTTP and cannot be switched to HTTPS, no WordPress-side fix will clear the warning. The resource must be removed or replaced with an HTTPS-capable equivalent before the padlock will stay clean.

Want a senior eye on your HTTPS setup?

Tell us about your WordPress site and we will audit your SSL configuration, mixed content sources, and redirect structure — and tell you exactly what needs fixing before a visitor sees the warning.

Request a free SSL audit

Frequently Asked Questions

Why does my WordPress site still show "Not Secure" after installing SSL?

Installing an SSL certificate secures the connection between the server and the browser, but it does not update the URLs inside your WordPress database. If posts, widgets, or theme files still reference http:// versions of images or scripts, the browser detects mixed content and displays the "Not Secure" warning regardless of the certificate. The fix is to update those URLs — starting with Settings → General, then the database — not to reinstall the certificate.

Is a WordPress mixed content error bad for SEO?

Google confirmed HTTPS as a ranking signal in 2014 — described at the time as a lightweight signal affecting fewer than 1% of global queries, carrying less weight than content quality and authority signals. The more immediate concern is user trust: visitors who see the "Not Secure" indicator in Chrome or Firefox are more likely to leave before completing a form or purchase. Active mixed content (blocked scripts) can also prevent conversion elements — forms, buttons, payment widgets — from functioning, which has a direct commercial impact that compounds any search visibility effect.

What is the difference between active and passive mixed content in WordPress?

Active mixed content — JavaScript files, CSS stylesheets, iframes — is blocked by default in most modern browsers (including current Chrome, Firefox, and Safari, though behaviour can vary by version) because an attacker intercepting an HTTP script request can inject malicious code into your page. Passive mixed content — images, video, audio — is less dangerous, and browsers attempt to auto-upgrade these requests to HTTPS; if the HTTPS version is unavailable, the resource is blocked. Active mixed content requires immediate attention; passive mixed content should also be fixed, but the urgency is lower unless it is breaking visible page elements.

Can I fix WordPress mixed content without touching the database?

Yes, for some causes. If the problem is only in Settings → General (WordPress Address not updated to HTTPS), updating that setting alone resolves the warning. If the issue is hardcoded HTTP URLs in the post and page database — which is the most common cause after an HTTP-to-HTTPS migration — you need either a database search-replace plugin (Better Search Replace) or a WP-CLI command. A plugin like SSL Insecure Content Fixer masks the warning at the output level without changing the database, but the underlying URLs remain.

What free tools can I use to find mixed content on my WordPress site?

Chrome and Firefox DevTools (right-click → Inspect → Console tab) display the exact HTTP resource URL causing the warning at no cost. The Why No Padlock tool (whynopadlock.com) scans a URL and lists all HTTP resources without requiring developer tool access. For a logged-in WordPress admin session, the browser console is the most reliable option because it sees content that requires authentication — such as backend pages or staging environments — that an external scanner cannot reach.

Need your WordPress SSL mixed content fixed properly?

Growth Pulse Media handles the full HTTPS setup — database fixes, redirect configuration, and page builder cleanup — in-house, with senior attention on every engagement. No obligation. We will get back to you within 24 hours.

Contact Growth Pulse Media
Dirk van Greuning — Founder, Growth Pulse Media
Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn