How to switch a WordPress website to https using the Insecure Content Fixer plugin?

Prerequisites:

1. SSL certificate: Your website must have a valid SSL certificate installed and enabled. You can typically get an SSL certificate from your hosting provider.
2. WordPress website: You should have a WordPress website running on your hosting account.

Step 1: Install and activate the Insecure Content Fixer plugin

1. In your WordPress dashboard, go to Plugins > Add New.
2. Search for “Insecure Content Fixer” and install it using the “Install Now” button.
3. Once installed, activate the plugin by clicking the “Activate” button.

Step 2: Configure the plugin

1. Go to Settings > Insecure Content Fixer to configure the plugin’s settings.
2. In the “General” tab, select your preferred redirect method. You can choose between “301 Permanent Redirect” or “302 Temporary Redirect.”
3. In the “Fix Insecure Content” tab, enable the options for images, scripts, and CSS links. This will ensure that all insecure content is converted to HTTPS.
4. Under “Fix Insecure Content Automatically,” enable the “Check and fix on every page load” option. This will ensure that the plugin checks for and fixes insecure content on all pages of your website.
5. You can also enable the “Debug mode” option to view detailed logs of the plugin’s activities.

Step 3: Verify HTTPS connection

1. To check if your website is properly using HTTPS, visit the following URL in your browser:

https://www.your-domain.com

2. If you see a padlock icon in the address bar and the URL starts with “https://,” then your website is successfully using HTTPS.

Step 4: Monitor for mixed content issues

1. After switching to HTTPS, you may still encounter some mixed content issues, where some links or assets on your website are still using HTTP.
2. To identify any remaining mixed content issues, you can use the “Test Links” feature in the Insecure Content Fixer plugin settings.
3. The plugin will scan your website for insecure links and provide you with a list of any issues found.
4. Fix any remaining mixed content issues by manually replacing HTTP links with their HTTPS counterparts.