Home › Knowledgebase › KB-1194

How to Diagnose and Fix a Mixed Content Warning on Your Small Business Website

Summary

This guide helps you troubleshoot and resolve: How to Diagnose and Fix a Mixed Content Warning on Your Small Business Website. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Your website may display a security warning in visitors' browsers even though your SSL certificate is active and installed correctly. This is known as a mixed content warning. It occurs when a secure HTTPS page loads certain resources—such as images, stylesheets, scripts, or fonts—over an insecure HTTP connection. Modern browsers block or flag this content to protect users, which can damage visitor trust and harm your business reputation. Mixed content warnings can also negatively impact your search engine optimisation (SEO), as Google prioritises secure websites in search results and may flag insecure pages to users.

This guide explains how to identify mixed content and update your website so every resource loads securely. If you are not comfortable editing code or files, we recommend testing changes on a staging site first or contacting our support team for assistance.

Quick Fix Steps

  1. Open your website in Google Chrome or Microsoft Edge.
  2. Press F12 to open Developer Tools.
  3. Select the Console tab.
  4. Refresh the page and look for warnings labelled Mixed Content.
  5. Note the insecure HTTP URLs listed in each warning.
  6. Update those URLs from http:// to https:// in your content management system or website files.
  7. Clear your website cache and browser cache.
  8. Reload your website and verify the padlock icon appears in the address bar.

Identify Mixed Content Using Browser Developer Tools

  1. Open your website in Google Chrome or Microsoft Edge.
  2. Press F12 (Windows) or Command + Option + I (macOS) to open Developer Tools.
  3. Click the Console tab at the top of the Developer Tools panel.
  4. Refresh your website page.
  5. Scan the console output for messages beginning with Mixed Content:. Each message will show the insecure resource URL being blocked or downgraded.
  6. Copy the full list of HTTP URLs so you can update them in the next step.
  7. Check your website's RSS feed, XML sitemap, and canonical tags for any remaining HTTP URLs, as these can also trigger security warnings.

Update Insecure Links to HTTPS

  1. Log in to your website's content management system (for example, WordPress or Joomla) or your hosting control panel file manager.
  2. Open the affected page, post, theme file, or template where the insecure resource is embedded.
  3. Locate every instance of http:// in image sources, script tags, stylesheet links, iframe embeds, or font references.
  4. Change http:// to https:// for each resource, ensuring the destination domain actually supports HTTPS.
  5. Save the file or publish the page.
  6. If your website uses a database, search and replace all instances of your site's HTTP URL with the HTTPS equivalent using a trusted search-and-replace tool or plugin.

WordPress Specific Instructions

  1. Log in to your WordPress admin dashboard.
  2. Navigate to Settings > General in the left-hand menu.
  3. Update the WordPress Address (URL) field to use https://.
  4. Update the Site Address (URL) field to use https://.
  5. Click the Save Changes button at the bottom of the page.
  6. Install and activate the Really Simple SSL plugin from the WordPress plugin repository to automatically detect and fix mixed content issues.
  7. Connect to your website via FTP or your hosting file manager and open wp-config.php in a text editor.
  8. Search for any hardcoded http:// URLs, such as WP_HOME or WP_SITEURL definitions, and update them to https://.
  9. Save the file and upload it back to your server if you edited it locally.

Force HTTPS Across Your Website

  1. Check with your hosting provider for the correct method to force HTTPS on your server, as configuration varies between Apache, Nginx, and other web servers.
  2. If your hosting uses Apache with .htaccess support, add a redirect rule that sends all HTTP traffic to HTTPS, or enable the Force HTTPS option if your control panel provides one.
  3. Save the file and test that visiting http://yourdomain.com.au automatically redirects to https://yourdomain.com.au.

Test Changes on a Staging Site First

Before applying changes to your live website, we strongly recommend testing them on a staging site. A staging site is a private copy of your website where you can verify that updating URLs to HTTPS does not break your layout, functionality, or plugins. Once you confirm the padlock icon appears and mixed content warnings are gone, you can push the changes to your live site.

Troubleshooting

Warnings Persist After Updating Links

Padlock Still Not Showing

If you updated your content but still see warnings, check hard-coded links in your theme files, header, footer, and widget areas. These are often overlooked when updating pages through a visual editor.
Do not simply disable mixed content blocking in your browser to hide the warning. Visitors will still see security alerts, and your website remains vulnerable to content injection attacks.

Third-Party Resources That Do Not Support HTTPS

If a third-party service (such as an embedded widget, external script, or older analytics tool) does not support HTTPS, you have three options:

Avoid loading any resource over HTTP on an HTTPS page, as this will continue to trigger mixed content warnings for your visitors.

If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

If you have followed these steps and your website continues to display security warnings, Open a Ticket for further investigation.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket