Short answer: Having an SSL certificate is not enough to make a site secure. Site AI Audit raises two warnings for the gaps that remain: “http:// does not redirect to https://” means the insecure version of your site still opens, and “Pages load insecure (http://) resources” means that secure pages still pull in images or scripts over plain http. Fix the first with a permanent redirect and the second by changing the resource links to https://.
Why a certificate alone is not enough
When owners install a certificate, they often assume the job is done. The padlock appears on the home page and everything seems fine. Two things can still go wrong. A visitor who types the address without https:// or follows an old link may land on the insecure version and stay there. And a secure page can still load some of its parts, such as an image, a script or a style sheet, over the old insecure connection. In both cases the visitor’s protection is weaker than the padlock suggests, and the browser may show warnings.
The audit reports these two gaps in the security area. They sit right after the certificate findings, which are covered in the article on SSL certificate findings, and they follow the same logic: find what a visitor would see and say how to fix it.
The redirect warning in detail
The finding reads “http:// does not redirect to https://” and it is a warning. The audit tests it by opening the plain http:// version of your address and checking whether the server sends the visitor to the https:// version. It reports the finding only when the site works over HTTPS but the insecure version is still reachable. The explanation is that visitors and search engines can still open the insecure version, which splits your rankings and exposes data. The advice is to add a permanent (301) redirect from http:// to https://.
Two consequences are worth understanding. First, for visitors: anything typed or sent on the insecure version, such as a form entry or a login, travels in the open. Second, for search engines: two addresses for the same page look like two different pages, and your ranking signals are shared between them instead of being concentrated on one. The article on redirecting HTTP to HTTPS the right way shows how to avoid loops and other mistakes.
How to add the redirect
- Use the control panel if it has one. Many hosts have a “force HTTPS” switch that adds the redirect for you.
- Or add a rule on the server. On Apache, a rewrite rule in the site configuration or .htaccess; on Nginx, a server block for port 80 that returns a 301 to the https:// address.
- Or use the CDN. Most content delivery networks have a setting to always use HTTPS.
- Test it. Open the http:// version of several pages, not only the home page, and confirm that each one lands on its https:// equivalent in a single step.
- Update your own links. Change internal links, the sitemap and the canonical tags to the https:// addresses, so the redirect is the safety net, not the main route.
A word of caution about CDNs: some have an encryption mode that talks to your server over plain HTTP, which can create an endless redirect when combined with a server-side rule. The guide to CDN SSL modes explains how to avoid that.
The mixed content warning in detail
“Pages load insecure (http://) resources” is the second warning. It appears when the audit finds, on pages served over HTTPS, references to resources that load over http://. Browsers react in different ways: they may block the resource, show a warning in the address bar or simply load it and mark the page as not fully secure. The explanation in the report says that browsers block or warn about images and scripts loaded over http:// on a secure page, and the advice is to change these resource links to https://. The report lists the pages where the crawler found them.
The effect on visitors depends on the kind of resource. A blocked image leaves a hole in the page. A blocked script can break a menu or a form. A blocked style sheet can make the page unreadable. Even when the resource loads, the padlock may disappear, which makes a visitor wonder whether it is safe to enter their details.
Where mixed content hides
- Old posts and pages. Images inserted years ago with an http:// address, often from a time when the site was not yet secure.
- Theme and plugin settings. A logo, a background or a script URL entered with http://.
- Hard-coded addresses in the database. After moving a site to HTTPS, many addresses remain unchanged; the article on mixed content errors shows how to find and replace them.
- Embedded third-party content. Widgets, maps and videos pasted as code with insecure links.
- CSS files that reference fonts or images with absolute http:// addresses.
The fastest repair for the database case on a WordPress site is a careful search and replace of the http:// version of your domain with the https:// version, after taking a backup. For the other cases, edit the specific setting or snippet that the report points to.
How the two findings relate
The redirect and the mixed content are two halves of the same job: make sure that every request, from the first click to the last image, uses HTTPS. Once both are fixed, you can consider HSTS, which tells browsers to use HTTPS on their own and makes the redirect unnecessary for returning visitors; see the guide to enabling HSTS safely. Do the redirect first and HSTS last, because HSTS makes mistakes harder to undo.
A related finding in the SEO area, “The site opens on more than one address”, appears when www and non-www or http and https all load separately. If you see it next to the redirect warning, one set of redirect rules can fix both, as the article on choosing one URL version explains.
Testing the result
After you fix both findings, test as a visitor would. Type the http:// version of your address in a private browser window, then watch where it goes and how many steps it takes. Open your most important pages and look at the padlock. Open the console in the developer tools and look for mixed content messages. The audit gives you the final confirmation, but a two-minute test of your own catches obvious mistakes such as a redirect that works for the home page and fails for inner pages.
Third-party services that insist on http
Occasionally a widget or a script comes from a provider that still offers only an http:// address. The right answer is to replace the service. An insecure resource on a secure page is a standing weakness, and it will produce the same warning in every check until it is gone. Most providers now support HTTPS, so look for a current embed code first. If none exists, consider hosting a copy of the file on your own server, or removing the feature.
Why search engines care
Google has treated HTTPS as a small ranking signal for years, and more importantly, its crawler prefers a single consistent version of each page. If the insecure and secure versions both answer, the crawler has to guess which one to keep. A clean redirect removes the guesswork. It also protects the links that other sites have pointed at your old http:// addresses, because the redirect passes visitors, and the value of those links, to the secure page.
A worked example
A family-run hotel moved its website to HTTPS two years ago. The audit report shows two warnings: the http:// version does not redirect, and 14 pages load insecure resources. The hotel’s webmaster adds a redirect in the hosting panel with a “force HTTPS” setting, and tests four random pages. Then he opens the first page in the mixed content list and finds a gallery photo inserted with an http:// address. He runs a search and replace in the database, which fixes 11 of the 14 pages. The other three have an old booking widget pasted as code, which he replaces with the provider’s current snippet. A new check shows both warnings gone, and the padlock now stays on every page.
To find out whether your own pages are fully secure, check your website with Site AI Audit. The check needs a free account; the plans unlock the full report with the exact pages.
Related reading
- 301 or 302? Choosing the Right Redirect for Your Website
- How to Find and Fix Broken Links on Your Website
- Is Your Website Protected From Hacking? What the Audit Checks
- How to Add Security Headers on Apache, Nginx, WordPress and CDNs
The bottom line
A certificate protects only the connections that use it. Redirect every http:// request to https://, change insecure resource links and run the check again, so that every part of every page is loaded securely.
الأسئلة الشائعة
Is mixed content dangerous?
It weakens the protection of the page and can break parts of it, because browsers block or warn about insecure resources on secure pages.
Should the redirect be 301 or 302?
Use a permanent 301 redirect. It tells browsers and search engines that the secure address is the real one.
Do I still need a redirect if I use HSTS?
Yes. HSTS only works after a browser has visited your site once over HTTPS. The redirect covers the first visit.
How can I find mixed content myself?
Open the page in a browser, look at the console in the developer tools and search the page source for http:// links. The audit’s list saves you the search.
Why does the finding list pages I thought were fixed?
Caches may serve an older version of the page. Clear them and run the check again.



