Fix mixed content after switching to HTTPS with AI

Restore the padlock by finding and rewriting the leftover http:// links an SSL move left behind.

Difficulty Intermediate

Time ~10 min

Tools run_wp_cli

Prerequisites

A connected site and a recent backup. This rewrites the database directly, so a backup is required before you run it.

The prompt

My WordPress site shows a broken padlock or a "not secure" warning after I switched to HTTPS. Some old http:// URLs are still loading somewhere on the site.

My site address is: [https://yourdomain.com]

Please find and fix the leftover insecure references by replacing http://yourdomain.com with https://yourdomain.com across the database, including inside serialized data like theme and page-builder settings. Only replace my own domain and leave external links alone.

First run this as a dry run and show me how many replacements will be made and in which tables. Do not change anything until I confirm. I have already taken a backup. After the live run, tell me exactly what changed so I can reload the site and check the padlock.

Already connected to WPVibe?

Skip the copy-paste. Just ask your AI for the “Fix mixed content after switching to HTTPS with AI” recipe, or describe the task, and WPVibe runs these steps on your own site.

You moved your site to HTTPS, but the padlock still shows a warning or a “not secure” label. Somewhere an old http:// image, script, or link is still loading, and the browser flags the whole page as insecure because of it. Hunting through every post, widget, and setting by hand is miserable, and the offending URL is often buried inside serialized theme or page-builder data you cannot even see in the editor.

WPVibe runs a database-wide search and replace that swaps your old http:// address for https://, and it handles serialized data (theme options, page-builder layouts) correctly so nothing breaks in the process. It replaces only your own domain and leaves external links alone. Most importantly it runs a dry run first and shows you exactly how many places will change and in which tables, so you see the full scope before a single row is touched.

Take a backup before you start, because this rewrites the database directly. Paste the prompt with your domain, review the dry-run count the AI shows you, then approve the live run. WPVibe pauses for your explicit approval before it changes anything, so nothing happens until you say go.

Outcome

Every http:// reference to your own domain is rewritten to https://, including inside serialized data, and the padlock returns.