You added SSL and your site loads over https, but the padlock is missing or the browser says the connection “is not fully secure.” That’s mixed content: the page itself is secure, but some images, scripts or stylesheets still load over plain http. It’s common right after adding SSL or moving a site from a development domain. Here’s how to find it and fix it for good.
Find what’s loading over http
Open the page in Chrome, right-click, choose Inspect, and open the Console tab. Each mixed content warning lists the exact file. Note whether the files are your own images, theme or plugin files, or something hard-coded in a widget or page builder layout.
Fix 1: Make sure WordPress itself uses https
Go to Settings → General and check that both WordPress Address and Site Address start with https://. If they’re greyed out, they’re set in wp-config.php; update them there.
Fix 2: Replace old URLs in the database
Old http:// links live inside your posts, widgets and settings. Take a backup, then replace them. With WP-CLI, run a dry run first to see what would change:
wp search-replace 'http://example.com' 'https://example.com' --all-tables --dry-run
wp search-replace 'http://example.com' 'https://example.com' --all-tables
Without command-line access, the Better Search Replace plugin does the same job from the dashboard. Both handle serialized data correctly, which a raw SQL replace does not.
Fix 3: Page builders keep their own copies
Page builders often store URLs and generated CSS files separately, so a database replace can miss them. In Elementor, go to Elementor → Tools, use Replace URL to swap http for https, then click Regenerate CSS & Data on the General tab. Other builders and block plugins with generated CSS usually have a similar “regenerate” option.
Fix 4: Clear every cache
Clear your caching plugin, your host’s server cache and your CDN (Cloudflare, for example). Old cached pages keep serving the http links until you do.
Fix 5: Catch anything left over
- Hard-coded links in the theme: search your child theme files for
http://and update them. - Third-party embeds (old widgets, badges, iframes): replace the embed code with the provider’s current https version.
- Force https at the server so every http request redirects. Most managed hosts have a one-click setting for this.
Want it handled?
Mixed content is one of the most common jobs for our $79 one-time fix. See also how to add an SSL certificate to WordPress properly.