Fix Mixed Content: Fully Deliver HTTPS
HTTP resources on HTTPS sites weaken security and browser trust.
HTTP resources on HTTPS pages weaken security and browser trust The error should never be assessed in isolation. What matters is which URL group is affected and whether it creates a crawling, indexing, snippet, performance or quality problem.
Track the causal involvement to the source
An HTTPS page can still request HTTP resources through a template, a CSS file or a third-party script. Check the browser console and the initiator of the request. The visible error can be a missing image, while the outdated address is in a reused background style.
Example: Recognizing the Result
Illustrative example: An HTTPS page integrates a script via http://. Browsers can block this insecure resource; a form may not work then.
Limit cause and implement correction
Use a working HTTPS resource or replace the integration. Merely rewriting the protocol does not help if the target does not have a suitable certificate. After the correction, also test delayed loaded content and interactive states. An inconspicuous first screen does not capture all later requests.
What makes you recognize a suitable correction
Switch the responsible integration to an actually functioning HTTPS resource and re-check the browser console and the affected function.
Classification and boundaries
When is this indication not a clear error?
Simply replacing the http string with https does not help if the target does not offer a valid HTTPS.
Mixed Content According to CMS and Cause
Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where mixed content has a clear cause or fixed route in the respective system.
Frequent causes of this error
Related SEO Errors
Appropriate Seitenreport checks
This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.