That One CrawlerDaddy mode

Security check

Mixed content: http files on an https page

Mixed content happens when a secure https page loads images, scripts, styles or frames over plain http. Browsers block insecure scripts and frames outright, so parts of the page break, and they may mark the page as not fully secure. The fix is to load every file over https, usually by updating old hard-coded addresses.

By Updated · 1 min read

Why it matters

It usually appears after a site moves to https: old posts still embed images with http:// in their address, or a theme loads a font or script from an http URL. Visitors see broken images or a warning in the address bar, which costs trust, and anything the browser blocks simply doesn't work.

How to fix it

  1. Open the page details to see each http:// file we found.

  2. Change each address to https:// and check the file still loads.

  3. In WordPress, run a search-and-replace on old http:// image addresses in your posts.

  4. If a third party doesn't offer https, host the file yourself or drop it.

  5. Add the Content-Security-Policy “upgrade-insecure-requests” header as a safety net.

How That One Crawler checks it

  • Mixed contentWarning

    This https:// page loads files over plain http://. Browsers block insecure scripts and frames outright and may show a "Not secure" warning for the rest.

    Fix: Change each http:// link to https:// (or a relative URL). If a file isn't available over https, host it yourself.

Frequently asked questions

Does mixed content affect SEO?

Indirectly. Google prefers secure pages, and blocked scripts or images make the page worse for visitors, which is what rankings follow.

Are plain http links to other sites mixed content?

No. Linking to an http site is fine. Mixed content is only about files the page itself loads, such as images, scripts, styles and frames.

Find every page with this problem

Free, no signup, results in a couple of minutes. Your scans stay in your browser.