Fix a "not secure" warning on a site that has a certificate.
If your certificate is in place but the browser still warns, some part of the page is loading over plain http.

One page, mixed addresses.
Mixed content means the page itself loads over https, but an image, script, stylesheet, or font on it is requested over http. Browsers flag this because that one item is not encrypted. The certificate is fine. The page just points at old http addresses, often left over from before the certificate was added.
Finding and fixing it, step by step.
- Open the affected page in your browser. Right-click, choose Inspect, and open the Console tab.
- Reload the page. Messages mentioning mixed content list the exact http addresses.
- Open the matching file in File Manager, or the page in your site editor, and change each http:// address to https://. If the file is on your own domain, you can use /images/photo.jpg without any prefix.
Step by step, continued.
- If the item comes from another website, check that the site offers an https address. If not, host the file yourself or remove it.
- On WordPress, set both addresses under Settings, General to https://, then search your content for old http:// links. A reputable search-and-replace plugin handles this; make your own copy of the database first.
- Save, reload the page, and check the Console again.

Make it stick.
Add a redirect so every visitor lands on https; see force your site to load over https. Clear any caching plugin, since it may keep serving old pages. Then confirm the certificate in check your SSL certificate.
Common questions.
Why does my site say not secure when I have a certificate?
The page probably loads at least one image, script, or stylesheet over http. That is called mixed content. Open your browser's Console tab to see which addresses are involved, then change them to https:// in your files or your site editor.
How do I find mixed content on my site?
Right-click the page, choose Inspect, and open the Console. Reload the page and read the mixed-content messages, which name each http address. Fix those, reload, and repeat until the messages stop.
More questions.
Can WordPress cause mixed-content warnings?
Yes. Old posts often keep http:// image links from before the certificate. Set your WordPress Address and Site Address to https://, then update the old links with a search-and-replace tool. See WordPress hosting.
Stuck on a setting? Open a ticket or call (828) 770-9428.




