How to Fix Mixed Content After Installing SSL
Your certificate is valid, but the browser still warns visitors. Find and replace insecure images, scripts, fonts and API calls safely.

Mixed content occurs when an HTTPS page requests a resource over HTTP. Browsers may upgrade, block or warn about that request depending on its type. The certificate itself can be perfectly valid while the page remains partially insecure.
Find the insecure requests
Open browser developer tools, reload the page and inspect Console and Network entries containing http://. Common sources are old image URLs, theme files, web fonts, analytics snippets, CSS backgrounds and API endpoints.
Fix the source
- Update the site's canonical URL and database references.
- Use root-relative or HTTPS asset URLs.
- Replace third-party services that do not support HTTPS.
- Clear application, server and CDN caches.
WordPress caution
Use a serialization-aware search-and-replace tool rather than editing SQL blindly. Then enforce one HTTPS redirect at the server or CDN—not several competing redirects.
Confirm the certificate and chain with our SSL checker. Enet's WordPress hosting includes HTTPS configuration, and our team can handle a complete secure migration.
Share this article
Was this article helpful?
Your vote helps us write better guides.
