External links and mixed HTTP content
Start with blocked scripts, missing images or incorrect destinations that affect real tasks, then replace insecure references where a working HTTPS equivalent exists.
What the findings mean
PubSEO can record images hosted on another domain, external links using HTTP and HTTP resources referenced by an HTTPS page. Depending on resource type and browser behaviour, mixed content may be blocked or upgraded.
What the evidence cannot establish
A separate image domain or CDN is not itself a fault. A source-code HTTP reference does not establish the complete network outcome or the cause of a performance problem. Confirm the actual resource and destination before making a replacement.
How to prioritise
Start with blocked scripts, missing images or incorrect destinations that affect real tasks, then replace insecure references where a working HTTPS equivalent exists.
What to do
- Open the recorded source and resource or link address. Confirm whether it is intended and whether the resource currently works.
- Verify that the HTTPS equivalent provides the correct content with a valid certificate before updating references.
- Correct relevant href, src, srcset, CSS, embedded-content or API references in the shared component that generates them.
- Keep intentional delivery services. Move images only when there is a valid delivery or rights reason, preserving relevant variants and cache behaviour.
Check the result
Load the page and inspect browser network and console results. Confirm the edited images and links work with the expected content and no remaining mixed-content error. Browser security exceptions are not a visitor-facing fix.
Need help with a particular finding?
Contact us →