Why Is My Website Showing Mixed Content Errors And How Do I Fix Https?
Summary
This guide helps you troubleshoot and resolve: Why Is My Website Showing Mixed Content Errors And How Do I Fix Https?. Follow the steps below to fix the issue.
Common Causes
Mixed content occurs when a website loads over a secure HTTPS connection but pulls certain resources, such as images, stylesheets, scripts, or iframes, over an unsecured HTTP connection. Modern browsers often block these insecure elements, which can result in missing imagery, broken page layouts, or security warnings that reduce visitor trust. This article explains how mixed content errors occur, the impact on site security and SEO, and the steps required to identify and update insecure resource URLs so that all assets are served over HTTPS.
Identify Mixed Content Errors
- Visit your website using
https://in your browser. - Look for the padlock icon in the address bar. If it shows a warning triangle or says "Not secure," mixed content is likely present.
- Right-click anywhere on the page and select Inspect or press
F12. - Click the Console tab in Developer Tools.
- Refresh the page using
F5orCtrl + R(Windows) /Cmd + R(Mac). - Review the list of errors. Mixed content warnings typically read:
Mixed Content: The page at '...' was loaded over HTTPS, but requested an insecure resource 'http://...'.
Alternative identification methods include using online mixed content scanners or browser extensions designed to detect insecure resources on a page. These tools can help analyse your site if manual inspection does not reveal every insecure URL.
Update Insecure Resource URLs
- Open your website files using an FTP client, file manager, or your content management system.
- Search your HTML, CSS, JavaScript, and template files for instances of
http://. - Change internal resource links from
http://tohttps://. For example:<img src="http://yourdomain.com.au/image.jpg">becomes<img src="https://yourdomain.com.au/image.jpg"><link rel="stylesheet" href="http://yourdomain.com.au/style.css">becomes<link rel="stylesheet" href="https://yourdomain.com.au/style.css">
- Update any hard-coded HTTP URLs in your website database. CMS-driven sites often store content, image paths, and metadata in database tables rather than static files.
- Save your changes and upload the modified files if necessary.
Update Database URLs for WordPress
- Create a full database backup before making any changes.
- Install a reputable search and replace plugin from the WordPress plugin directory.
- Run a search for
http://yourdomain.com.auand replace it withhttps://yourdomain.com.auacross posts, pages, and post meta tables. - Navigate to Settings > General.
- Update the WordPress Address (URL) and Site Address (URL) fields to use
https://. - Click Save Changes.
Update Database URLs for Other CMS Platforms
For Joomla, Drupal, or other database-driven platforms, use the platform's native search and replace tool or run a careful SQL search and replace operation on your database tables. Always back up your database before performing bulk URL replacements, as incorrect changes can break serialized data or site functionality.
Force HTTPS Redirects on Apache Servers
- Access your website's
.htaccessfile via FTP or file manager. - Add the following code at the top of the file to redirect all HTTP traffic to HTTPS:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
- Save the file.
- Test your website by visiting
http://yourdomain.com.au— it should automatically redirect tohttps://yourdomain.com.au.
If you use a different web server, such as Nginx, configure the redirect in your server block or hosting control panel instead.
Update SEO Settings After HTTPS Migration
- Update all internal links, canonical tags, and sitemaps to use
https://to avoid SEO dilution and duplicate content issues. - Submit your updated sitemap to Google Search Console.
- Use the URL Inspection tool in Google Search Console to request indexing of key pages.
- Monitor coverage reports for any crawl errors related to HTTP URLs.
Troubleshooting
Warnings Persist After Updating URLs
- Clear your browser cache. In Chrome or Edge, press
Ctrl + Shift + Delete(Windows) orCmd + Shift + Delete(Mac), select cached images and files, and clear them. - Clear any caching plugins or server-side caching active on your website.
- Check hard-coded links in theme files, widgets, or embedded content that may still reference
http://. - Review your Content Security Policy (CSP) headers. A restrictive CSP may block mixed content reporting or enforce
upgrade-insecure-requests, which can affect how insecure resources are handled.
Third-Party Resources Load Over HTTP
- If images, fonts, scripts, or iframes are hosted on an external domain, confirm that domain supports HTTPS.
- Update the resource URL to
https://or host the asset locally on your own secure server. - Avoid loading resources from domains that do not offer a secure version.
- For embedded third-party content such as iframes, ensure the embed code uses
https://or a protocol-relative URL (//) where supported.
SSL Certificate Issues
- Ensure your SSL certificate is valid and not expired. An expired certificate will trigger security warnings even if mixed content is resolved.
- Confirm the certificate covers both the root domain (
yourdomain.com.au) and thewwwsubdomain if applicable.
.htaccess or theme files can take your website offline.Resolving mixed content errors ensures that every element on your page is delivered securely, protects visitor data, and helps maintain trust and search engine visibility. If you are unable to locate or fix the insecure resources, Open a Ticket for assistance.
Still Having Issues?
💻 Open a Ticket