Mixed Content: Why Your HTTPS Site Shows "Not Secure" and How to Fix It
Updated October 22, 2026
Mixed content means an HTTPS page loads something, such as an image, script, font or form, over plain http://. Browsers upgrade or block those requests, so images disappear, scripts break and the padlock may show a warning. Fix it by changing every http:// resource link to https:// and adding a Content-Security-Policy upgrade rule.
Quick diagnosis
- Images missing on an HTTPS site: they are linked with http:// and the browser blocked them.
- Padlock has a warning or "Not secure" appears: a form posts to http:// or passive content is mixed.
- Scripts or styles broken after moving to HTTPS: hard-coded http:// links in the theme.
- Warning only on one page: content pasted into that page links to http:// files.
Causes and fixes
Hard-coded http:// links in content
Most commonImages and files added before the site moved to HTTPS still point at http:// addresses in the database or page content.
Fix: Search and replace http://yourdomain.com with https://yourdomain.com across the database or content (back up first), then clear caches.
Theme or template files with http:// URLs
Scripts, stylesheets and fonts linked with http:// in theme files break for every page that uses the template.
Fix: Update the links to https://, or use protocol-relative paths for resources on the same domain.
Third-party resources that do not support HTTPS
An old widget, image host or tracking pixel that only serves over http:// cannot be upgraded.
Fix: Switch to the provider's HTTPS endpoint, host the file yourself, or remove the resource.
Forms that submit to http://
A form whose action points at an http:// URL makes browsers warn visitors that the information is not secure.
Fix: Point form actions at https:// URLs, or use relative URLs.
Site URL setting still on http://
Content management systems build links from a site address setting. If it still says http://, new links are generated insecure.
Fix: Change the site address to https:// and force HTTPS with a 301 redirect at the server or host level.
CDN or image service configured for http://
Some sites serve images through a CDN or image-resizing service whose base URL was set up as http:// years ago. Every image built from that base URL is mixed content, even though the page itself is secure.
Fix: Update the CDN or media base URL to https:// in your settings or environment variables, confirm the CDN has a certificate for that hostname, and purge its cache.
How to find it on your site
- 1
Open the console
Load the page with DevTools open. Mixed content requests appear as warnings or errors that name the exact http:// URL.
- 2
Check the Security panel
Chrome's DevTools Security panel summarises whether the page loaded any insecure resources.
- 3
Search your content
Search the database or content export for
http://to find every hard-coded link at once. - 4
Add an upgrade rule
Add the header
Content-Security-Policy: upgrade-insecure-requestsas a safety net so browsers request any remaining http:// resources over HTTPS.
Fixes by platform
WordPress
The most common platform for mixed content after an HTTPS move. Update the WordPress Address and Site Address settings, then run a search-and-replace with a plugin such as Better Search Replace on a backup.
Shopify
Shopify serves stores over HTTPS automatically, so mixed content comes from http:// links in theme code, custom Liquid, or content pasted into product descriptions.
Wix and Squarespace
Both serve HTTPS by default. Mixed content comes from embedded code blocks or iframes pointing at http:// sources; update or remove those embeds.
Custom code
Set the upgrade-insecure-requests CSP header, enable HSTS once HTTPS is stable, and fail builds on http:// resource URLs.
Frequently asked questions
What is mixed content?
Mixed content is when a page loaded over HTTPS includes resources such as images, scripts, stylesheets or forms loaded over insecure http://. Browsers block or upgrade those requests and may warn visitors.
Why does my site say "Not secure" when I have an SSL certificate?
Because something on the page still loads or submits over http://, or the certificate is expired or does not cover the exact domain. Check the browser console for mixed content warnings and an SSL checker for certificate problems.
How do I fix mixed content?
Change every http:// link to https:// in your content, theme and settings, replace resources that are not available over HTTPS, and add a Content-Security-Policy: upgrade-insecure-requests header as a safety net.
Can mixed content stop images from loading?
Yes. Modern browsers automatically upgrade http:// images to https://, and if the image server does not support HTTPS the image fails to load. Scripts and iframes over http:// are blocked outright.
Does mixed content affect SEO?
HTTPS is a lightweight Google ranking signal, and mixed content can make browsers show warnings that reduce trust and conversions. Blocked scripts can also break parts of the page that Google renders, so fixing it is worth doing either way.