About the Mixed Content Checker
Mixed content happens when an HTTPS page loads images, scripts, stylesheets, iframes, media or form targets over plain http://. Browsers block active mixed content such as scripts and iframes, which can break features, and may upgrade, block or warn about passive content such as images. This mixed content checker fetches a public HTTPS page and lists every insecure resource it finds, separating active from passive items.
Mixed content usually appears after moving a site to HTTPS, when old absolute URLs remain in posts, theme files or widgets. Fix it by changing the references to https://, ideally with a search-and-replace in your database, and confirm each resource is available over HTTPS. A Content-Security-Policy with upgrade-insecure-requests can act as a safety net while you clean up.
How to use it
- Enter the HTTPS page URL you want to scan.
- Run the check to list every http:// resource the HTML references.
- Fix active mixed content first, since browsers block it.
- Update remaining URLs to https:// and re-run the check.
Frequently asked questions
What is the difference between active and passive mixed content?
Active mixed content, such as scripts, stylesheets and iframes, can change the whole page, so modern browsers block it. Passive mixed content, such as images, audio and video, cannot alter other parts of the page; browsers increasingly upgrade these requests to HTTPS automatically or block them if HTTPS is unavailable. Both should be fixed.
Does mixed content affect SEO?
Mixed content is not a direct ranking factor, but it can cause broken layouts, missing images or failed scripts, and browsers may show a weaker security indicator. Those problems affect user experience and trust. Since HTTPS is a lightweight ranking signal, a clean HTTPS setup without mixed content is the safe baseline.
Why does this tool miss some mixed content I see in the browser?
The checker reads the HTML the server returns. Resources added later by JavaScript, loaded from CSS files such as background images and fonts, or injected by third-party widgets may not appear in that HTML. Use your browser's developer console, which logs mixed content warnings, to catch those dynamic cases.