Black FridayCyber Monday 2026
13Days
14Hrs
16Mins
35Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Mixed Content Warnings After Installing SSL: Fix “Not Secure”

After moving to HTTPS, some pages still load images or scripts over HTTP. Learn how to find mixed content and fix the URLs safely.

wpallsolution 6 min read

WordPress mixed content is what happens when a page loaded over HTTPS still asks for something over plain HTTP, such as an image, a script or a stylesheet. Browsers then show “Not secure”, a warning in the console, or quietly block part of the page so the layout breaks. It usually appears right after you install an SSL certificate or switch the site to HTTPS, because old addresses are still stored in posts, settings and theme files. This guide shows how to find each insecure URL and fix it at its source.

Quick answer

Open the browser’s developer console and list the http:// resources. Make sure the WordPress and Site addresses start with https://. Replace old http:// links in your content with https:// using a safe search and replace (with a dry run first), then fix hard-coded URLs in the theme, builder and plugin settings, and switch third-party resources to their HTTPS versions. A Content Security Policy header can upgrade leftover requests, but it is a safety net, not a substitute for fixing the URLs.

How this guide was prepared: it is research-based. We used MDN’s mixed content guide, the WordPress documentation and the WP-CLI documentation listed under Sources, checked on October 23, 2026. We did not scan your site, and the fix depends on where your insecure URLs are stored.

What mixed content is

MDN defines mixed content as a page loaded securely over HTTPS that fetches resources over HTTP or another insecure protocol, which an attacker could view or modify. Browsers treat two kinds differently. “Upgradable” content, such as images, audio and video, is automatically upgraded to HTTPS by modern browsers. “Blockable” content, such as scripts, stylesheets, iframes, fetch requests and web fonts, is blocked. That is why mixed content can break a layout or a feature even when the page looks mostly fine: the blocked stylesheet or script is simply missing. Blocking also applies when the host is an IP address.

The decision tree: where is the insecure URL?

Flowchart for WordPress mixed content: five questions about console warnings, site addresses, stored links, theme settings and third-party resources
Five questions find the source of every insecure URL.
  1. Console lists http:// resources? Note the exact URLs (Step 1).
  2. Home and Site addresses not https? Fix them (Step 2).
  3. Old http:// links stored in content? Replace them with a dry run (Step 3).
  4. Theme or builder sets http:// URLs? Update them (Step 4).
  5. A third-party resource is only on http? Use its https version or remove it (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Padlock shows a warning, page looks normalImages or media loaded over httpSteps 1 and 3
Layout or fonts broken on HTTPSA blocked http stylesheet, script or fontSteps 1, 4 and 5
Warnings on every pageAddresses still use http, or a theme or global settingSteps 2 and 4
Only older posts affectedOld http:// links stored in post contentStep 3
Only pages with an embed or widget affectedA third-party resource served over httpStep 5

6 steps to fix WordPress mixed content

Step 1: Find the insecure URLs

Open the page in your browser, open the developer console (usually F12) and read the mixed content messages. MDN suggests checking the console, testing with mixed content disabled, or crawling the site with a mixed content checker. Write down each URL and the page where it appears, so you can tell whether it comes from content, the theme or a third party.

Step 2: Make sure the WordPress and Site addresses use https

Check Settings → General: both addresses should start with https:// and have no trailing slash, according to the WordPress documentation. Also check that your server or host redirects HTTP to HTTPS, and look at Site Health, whose Info tab shows whether the site is using HTTPS. If a redirect loop appears, read ERR_TOO_MANY_REDIRECTS in WordPress.

Posts, pages, widgets and settings may contain absolute http:// links. After a backup, WP-CLI’s wp search-replace 'http://yourdomain.com' 'https://yourdomain.com' --dry-run shows what would change; run it again without --dry-run when the report looks right. WP-CLI handles serialised data safely, whereas a plain text replace in the database can corrupt it. See is your WordPress backup really safe before you edit the database.

Step 4: Fix theme, builder and plugin settings

Hard-coded URLs also live in theme files, customiser settings, page builder templates and plugin options, and a database replace may not catch values generated at run time. Search your theme and builder settings for http://, update the logo, background images and custom CSS, and regenerate any builder CSS cache. If your page builder is Elementor, see Elementor changes not showing for clearing generated files.

Step 5: Fix third-party resources

Embeds, fonts, scripts and images from other sites should use their https:// versions. If a provider only supports HTTP, replace it, host the file yourself where the licence allows, or remove it. Test pages with embeds and widgets individually.

Step 6: Add a safety net, then test again

MDN describes the Content Security Policy directive upgrade-insecure-requests, which tells the browser to upgrade requests to HTTPS, including blockable content. Your host or a security plugin may offer it. Treat it as a net under the fixes above, since it cannot repair a resource that does not exist on HTTPS. Then test again in a private window and clear caches.

Version and hosting differences

  • Browsers differ slightly in what they upgrade or block, so test in more than one.
  • A CDN may serve cached http:// copies of files, so clear it after changes.
  • Multisite stores addresses per site, so repeat the fixes for each site.

How to verify the fix

  • The console shows no mixed content messages on your main pages.
  • The padlock shows a secure connection, and layouts and fonts load.
  • Embeds, forms and the checkout page also work over HTTPS.

How to prevent it from happening again

  • Always paste https:// URLs and prefer relative links for your own files.
  • Check the console after adding a plugin, widget or embed.
  • Test HTTPS after a migration; see how to move WordPress to a new host.

Frequently asked questions

Is mixed content dangerous?

It weakens the security of an HTTPS page, since an insecure resource can be read or changed. Browsers warn or block for that reason.

Why does the layout break after SSL?

Browsers block insecure stylesheets, scripts and fonts, so the page loses them.

Can a plugin fix everything?

Some plugins rewrite URLs on the fly, but fixing the stored URLs at their source is cleaner.

Do I need to fix images?

Yes. Modern browsers often upgrade them automatically, but you should not rely on that.

What to do next

List the insecure URLs, fix their sources and test again. If you would like help with an SSL or migration clean-up, wpallsolution offers an emergency WordPress fix and WordPress maintenance packages. We cannot promise a result without seeing your site.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us