Mixed content on an HTTPS page

VariesDeveloper fixSecurityPer-page checkmixed_content

What this means

An HTTPS page loads one or more sub-resources over plain HTTP. Browsers block or upgrade much of this, which can break the page; severity rises once more than five resources are affected.

How to fix it

Serve every sub-resource over HTTPS — switch the URLs, use a host that supports TLS, or self-host the asset.

Fix effort

This check needs a developer fix: it turns on a routing, hosting or infrastructure decision that no automatic edit can make safely.

Authoritative source

https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes

Related checks

More in Security

Redirect downgrades HTTPS to HTTP Content-Security-Policy is report-only Missing Content-Security-Policy header Missing HSTS header Page not served over HTTPS All checks

Find every page this affects

CrawlX runs this check — and 161 others — across your whole site, ranks the findings by estimated impact, and opens the fixable ones as pull requests. Free for 500 URLs.

Start crawling free Browse all checks