How to Fix Mixed Content Warnings (HTTPS Not Fully Secure)

You installed SSL, yet the padlock is missing or parts of the page are broken. Mixed content – files still loaded over http:// – is almost always the reason.

⚠️Free Mixed Content Checker
Find http:// files that break the padlock on https pages.
Open tool →

Find the insecure files

Run your page through the Mixed Content Checker. It lists every http:// script, stylesheet, image, frame and form, and flags the ones browsers block outright.

Fix on WordPress

Set both addresses in Settings > General to https://. Then run a database search-and-replace from http://yourdomain.com to https://yourdomain.com (a plugin like Better Search Replace does this). Check theme and page-builder settings for hard-coded http:// links.

Fix anywhere else

Change each listed URL to https:// or to a relative path. If a third-party file isn't available over HTTPS, replace it or host a copy yourself.

Prevent it

Add the header Content-Security-Policy: upgrade-insecure-requests to automatically upgrade stray http:// requests.

Frequently asked questions

Is mixed content dangerous?

Insecure scripts and forms can be tampered with on public Wi-Fi.

Why are some files blocked?

Browsers block insecure scripts, styles, frames and forms on HTTPS pages.

Does it affect SEO?

Indirectly – broken pages and missing padlocks hurt trust.

⚠️Free Mixed Content Checker
Find http:// files that break the padlock on https pages.
Open tool →

More guides