Check explainer · v1
Mixed content: http:// subresources on an https page
Last reviewed
The page is served over https, but some of what it loads is not. Browsers treat those subresources as hostile — some are upgraded, some are blocked outright.
How this check works
For each analyzed page, the crawl counts subresource references that use http:// while the page itself is served over https. Any count above zero fails the page, with the number of offending references stated: browsers may block those images, scripts or styles, and rendering degrades exactly where the page depends on them.
What does a failure look like?
Legacy image CDN URLs hard-coded before the https migration; a third-party widget still served over http; absolute http references in a template that survived the switch — pages where the markup looks fine until the browser refuses the asset.
How to fix it, step by step
- Replace http:// references with https:// at the template or CMS field that emits them.
- Audit third-party embeds: vendor scripts are the most common survivors of an https migration.
- Re-run the crawl and confirm every page’s http subresource count is zero.
What does a pass or fail look like?
Good
Zero http:// subresource references across all analyzed pages.
Fail
An https product page references 4 http:// images — browsers may block them, and the gallery renders broken.
Frequently asked questions
Do browsers block all mixed content?
Not all, but the trend is strict: active content such as scripts and styles is blocked outright, and passive content like images is often auto-upgraded or blocked too. Counting every http:// reference avoids betting on which browser is lenient.
Why does this matter for search?
Because rendering happens in browsers. A blocked stylesheet or script changes what the page looks like to crawlers and to users; the check catches the cause of rendering that silently diverges from the code.
Is the page itself failed, or just the resource?
The page is failed, with the count of offending references. The resource is where the repair happens, but the defect belongs to the page that depends on it.
This rule is one of the checks the audit runs. Run the full site audit
Free preview; no account needed.