After installing an SSL certificate, your WordPress website may still display security warnings or fail to show the secure padlock icon in the browser. This usually happens when part of the website is still being loaded via HTTP instead of HTTPS, resulting in what is known as mixed content.
This guide explains the steps required to fully migrate your WordPress website to HTTPS.
Make sure that:
You can update your WordPress URLs using one of the following methods.
http://example.com to: https://example.com
for both:
If the URLs are defined through code, add the following lines to your wp-config.php file:
PHP
define('WP_HOME','https://example.com');
define('WP_SITEURL','https://example.com');
This ensures that all visitors are automatically redirected to the secure HTTPS version of your website.

Alternatively, add the following rules to your .htaccess file:
Apache Config
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
After performing the previous steps, you will need to replace any old HTTP URLs stored in your WordPress database.
It is highly recommended to create a backup before proceeding.

Search for: http://example.com
Replace with: https://example.com
to perform a test search.
The Replace GUIDs option is not required in most HTTP-to-HTTPS migration scenarios. Only use it if you specifically know it is required for your WordPress installation.
If you have SSH access and are familiar with command-line tools, you can use WP-CLI.
For a test run:
wp search-replace 'http://example.com' 'https://example.com' --dry-run
For the actual replacement:
wp search-replace 'http://example.com' 'https://example.com'
After completing the previous steps:
You can then check your website using mixed content testing tools such as Why No Padlock.
If the problem persists:
If an external source does not support HTTPS, you will need to replace it with a secure alternative or remove the affected resource from your website.
Once your HTTPS migration is complete, monitor your website for a few days to ensure that there are no remaining security warnings, loading issues, or HTTP links stored in content, widgets, themes, or plugins.
Contact our experts, they will be happy to help!
Contact us