A secure page that loads an insecure script or image is mixed content. Browsers block or warn on it, and it undermines the trust the HTTPS was meant to provide. Secure page references insecure resources. Browsers may block resources, breaking render; weakens security posture.
Why does mixed content (https page loading http) matter for AI search?
Browsers may block resources, breaking render; weakens security posture.
How do you fix it?
Serve all resources over HTTPS.
How do you find it on your site?
- Open the page and check the browser console for mixed content warnings.
- Search the page source for http:// references in scripts, images and styles.
- Crawl the site for insecure resource references at scale.
- Update every reference to https or a protocol-relative path.
Which ranking and citation factors does it touch?
Mixed content can break functionality and erodes the HTTPS trust signal. Clean secure loading supports both security and user-experience signals.
What is the impact?
Medium-high; render and trust. Direct.
What is the evidence?
Mixed content undermines HTTPS and can block resources. Google Search Central, Secure your site with HTTPS
Frequently asked questions about mixed content (https page loading http)
What does "Mixed content (HTTPS page loading HTTP)" mean?
Secure page references insecure resources.
How do you fix mixed content (HTTPS page loading HTTP)?
Serve all resources over HTTPS.