Mixed content checker
Check an HTTPS page for mixed content, the way an Evisio SEO audit report does: images, scripts and other files loaded over insecure http://, and links that still point to http:// addresses. Enter a page URL to see how many of each it has, with examples, in seconds.
What is mixed content?
Mixed content is when a page served over secure https:// loads some of its parts over insecure http://:
<!-- On https://www.example.com/ -->
<img src="http://www.example.com/uploads/team.jpg" alt="Our team">
<script src="http://cdn.example.net/widget.js"></script>
The page itself is encrypted, but those files aren’t, so anyone on the same network could read or tamper with them. Browsers respond by blocking insecure scripts and stylesheets outright, upgrading or blocking insecure images, and removing the padlock from the address bar.
Why mixed content matters for SEO
Mixed content usually appears after a site moves from HTTP to HTTPS. The address changes, but old image paths, theme settings, hard-coded scripts and links inside posts still say http://. The results range from a missing padlock that makes visitors wary, to a blocked script that breaks a form, a slider or a checkout without any error you’d notice.
Links to http:// addresses on your own site cause a smaller but steady cost: every click and every crawl goes through a redirect before it reaches the page, and search engines see two versions of the address.
How to use this checker
- Enter the full https:// address of one page.
- Read the two counts. For each, the result lists up to five examples, such as
img: http://example.com/a.png, so you can see which kind of file or link is at fault. - Fix the source, then run the check again. A page on plain http:// always shows zero http:// links, since the check only applies to secure pages.
What Evisio checks
Mixed content issues
Counts the resources the page loads over http://: images, scripts, stylesheets, iframes, audio and video. Any count above zero fails.
HTTP links on an HTTPS site
Counts the links on a secure page that point to http:// addresses, and lists up to five. Evisio judges this by the address the page finally landed on, so a page reached through a redirect to https:// is still checked.
How to check by hand
- Open the page in Chrome, Edge or Firefox and press F12 to open the developer tools.
- Go to the Console tab and reload the page.
- Look for warnings that mention “Mixed Content”. Each one names the insecure file and whether the browser blocked it.
How to fix mixed content
- Your own files: change
http://tohttps://in image, script and stylesheet addresses. On WordPress, a search-and-replace tool such as Better Search Replace can update old addresses across the database. Back up first. - Site settings: on WordPress, make sure both addresses in Settings > General start with https://, and check theme and page builder settings for hard-coded logos and backgrounds.
- Third-party files: switch embeds and widgets to their https:// versions. If a provider doesn’t offer HTTPS, replace it.
- Links: update internal links to https:// so they don’t go through a redirect. For links to other sites, use https:// wherever the site supports it.
More detail: fixing issues related to mixed content and how to fix an HTTPS page with internal links to HTTP.
Check every page on your site
Mixed content often hides in old blog posts that nobody opens anymore. A free Evisio SEO audit report checks every page it scans, along with HTTPS, redirects and more than 80 other checks, and turns each problem into a task with step-by-step instructions.
Questions
Will mixed content hurt my rankings?
Not directly, but it can undo what HTTPS gives you. Visitors who see a warning or a broken page leave, and blocked scripts can break the parts of a page that turn visitors into customers.
Can I just use protocol-relative URLs like //example.com?
They work, but they’re outdated. Every modern site should be on HTTPS, so write https:// in full.
Is there a quick fix for the whole site?
Some hosts and CDNs offer an “automatic HTTPS rewrites” setting, and the Content-Security-Policy: upgrade-insecure-requests header tells browsers to upgrade insecure requests. Both help, but fixing the addresses at the source is the lasting solution.