What is mixed content?
Rubric check: mixed content (check id mixed_content)
Mixed content is an https page that loads some of its files, such as scripts, images or frames, over plain http. Browsers block the risky ones and may drop the padlock, so parts of the page can break.
Why it matters for SEO
Google renders pages much like Chrome does, so a script or stylesheet the browser blocks may also be missing when Google renders the page. Images loaded over http are usually upgraded or shown with a warning. Visitors who see "Not secure" or a broken layout tend to leave.
Does this matter for ChatGPT and AI Overviews?
Most AI tools read the HTML text, not the files a page loads, so mixed images matter little to them. Content added by a blocked script is a different matter: it won't appear in a browser, and browser-based agents won't see it either. The main reason to fix this is a working, secure page.
How Rubric scores it
StandardStandard checks are the baseline every other tier is measured against.
Why this tier: Mixed content breaks the padlock.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 14 of 300 sites where Rubric could judge it (4.7%). That is 14 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 16 of its findings by hand and 3 were wrong (19%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Latest review round: 0 of 21 findings judged were still wrong after the last fix.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Check Settings > General: both WordPress Address (URL) and Site Address (URL) should use
https://. - Update old
http://links to your own images and files with a search-and-replace plugin such as Better Search Replace. Back up the database first. - For third-party scripts or embeds, change their addresses to https or replace them with current embed code.
Shopify
Shopify serves the store and its files over https. Mixed content usually comes from code you added:
- Search Online Store > Themes > Edit code for
http://in theme files and change those addresses to https. - Check images and embeds pasted into pages, blog posts and product descriptions (use the editor's Show HTML view).
Webflow
Webflow serves its assets over https. Mixed content usually comes from custom code:
- Check Site settings > Custom code, page custom code and Embed elements for
http://addresses. - Check images pasted by URL into Rich text fields. Change them to https and publish.
Custom code
Change every resource address to https or a relative path:
<img src="https://cdn.example.com/boot.jpg" alt="Brown hiking boot">
<script src="/js/app.js"></script>To catch stragglers, add the header Content-Security-Policy: upgrade-insecure-requests, which asks browsers to load http resources over https.