Troubleshooting
Why Is My WordPress Site "Not Secure"? How to Fix It

Short answer
A browser shows “Not secure” on a WordPress site when the page loads over plain HTTP instead of HTTPS. The usual causes are a missing or expired SSL certificate, WordPress settings still using http:// addresses, no redirect from HTTP to HTTPS, or mixed content loading images and scripts over HTTP. Install SSL, switch the site URLs to https and redirect all traffic.
Key takeaways
- “Not secure” is about the connection, not about malware; it means the page is not served over HTTPS.
- Most hosts offer free SSL certificates, so the fix rarely costs money.
- Both WordPress Address and Site Address in Settings > General must start with https://.
- A 301 redirect sends every HTTP visitor to the HTTPS version of the same page.
- Mixed content, such as images still linked with http://, can stop the padlock from showing.
What does “Not secure” mean on a WordPress site?
It means the browser loaded the page over unencrypted HTTP, so anything typed into it, such as a password or form, could be read or changed in transit.
Chrome, Edge, Firefox and Safari all flag HTTP pages this way. Chrome explains the labels in its help page on checking if a site's connection is secure.
The warning does not mean your site is hacked. It is about how the page is delivered, not what is inside it. A hacked site may still show a padlock, and a clean site can show “Not secure”.
It still matters a lot. Visitors trust the site less, browsers warn harder on forms and logins, and HTTPS is a light ranking signal in Google search.
How do you find which cause applies to your site?
Look at the address bar and the exact browser message, because each points to a different fix.
| What you see | Likely cause |
|---|---|
| “Not secure” and the address starts with http:// | No SSL, or no redirect to HTTPS |
| https:// works if typed, but http:// stays insecure | Missing HTTP to HTTPS redirect |
| https:// address but no padlock, or a warning icon | Mixed content on the page |
| Full-page “Your connection is not private” | Expired, wrong or missing certificate |
| Padlock on some pages, warning on others | Hard-coded http:// links in certain posts, widgets or theme files |
Type your domain with https:// in front. If it loads with a padlock, the certificate works and the problem is redirects or settings.
Do you have an SSL certificate installed?
If the https:// version shows an error or does not load at all, the site has no valid SSL certificate, and installing one is the first step.
Most hosts include a free certificate from Let's Encrypt or their own provider. Look for SSL, Security or TLS in your hosting panel and turn it on for the domain.
Certificates need the domain to point to the host. If DNS was changed recently or still points elsewhere, issuing or renewing can fail.
Our step-by-step guide on installing an SSL certificate on WordPress covers cPanel, managed hosts and Cloudflare setups.
If you wonder whether a paid certificate is worth it, see our comparison of Let's Encrypt vs paid SSL. For most sites the free one gives the same encryption.
Are your WordPress URLs still set to http?
If the WordPress Address and Site Address still start with http://, WordPress keeps generating insecure links even when SSL works.
Go to Settings > General and change both fields from http:// to https://, then save. You will be logged out and need to log in again.
If the fields are greyed out, the addresses are set in wp-config.php with WP_HOME and WP_SITEURL. Change them there instead.
The official guide to HTTPS for WordPress covers these settings and how to force the admin area onto HTTPS.
Is HTTP traffic redirected to HTTPS?
Without a redirect, people who type your domain or follow old links still land on the insecure HTTP version, so add a permanent 301 redirect for every page.
Many hosts offer a “Force HTTPS” switch in the hosting panel. That is the simplest option and runs before WordPress loads.
On Apache servers you can add a rule to .htaccess above the WordPress block:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [L,R=301]
If you use Cloudflare, use its Always Use HTTPS setting and pick the correct SSL mode. A wrong mode can cause a redirect loop, which our guide to Cloudflare SSL settings for WordPress explains.
Test a few old http:// links afterwards and make sure each lands on the matching https:// page, not the homepage.
Is mixed content breaking the padlock?
If the page loads over HTTPS but some images, scripts or styles still load over HTTP, browsers remove the padlock or block those files.
Mixed content is common after a site moves to HTTPS, because older posts store full http:// links to images in the database.
To find it, open the page, press F12 and check the Console for mixed content warnings. MDN explains the two kinds in its guide to mixed content.
To fix it, run a search and replace in the database from http://yourdomain.com to https://yourdomain.com, after a backup. Then fix leftovers in theme settings, widgets and custom code.
Our detailed guide to fixing mixed content warnings walks through the tools and the safest order of steps.
What does the warning do to forms, logins and sales?
On HTTP pages, browsers warn people as they type into forms and password fields, which drives away sign-ups, logins and sales even when nothing else is wrong.
Chrome shows a stronger “Not secure” message as soon as someone starts typing into a field on an HTTP page. Many visitors stop at that point and leave.
The effect is biggest on pages that collect data:
- Contact and quote forms
- Newsletter sign-ups
- The WordPress login page and member areas
- Checkout and account pages in a store
Payment providers also require HTTPS. Card gateways such as Stripe and PayPal will not work on a checkout served over HTTP, so a store without SSL cannot take card payments at all.
Browsers keep tightening these rules. Recent versions try HTTPS first and warn before loading plain HTTP sites, so the cost of staying on HTTP keeps rising.
How long does it take to move a WordPress site to HTTPS?
On most hosts the whole move takes under an hour: a few minutes to issue the certificate, then time to update settings, add redirects and fix mixed content.
The certificate itself is usually issued within minutes once DNS points to your host. New domains may need a little longer while DNS spreads.
Fixing mixed content takes the most time on older sites with many posts. A database search and replace handles most of it at once, and a few manual fixes in theme settings or widgets finish the job.
After the move, add the HTTPS version of your site in Google Search Console and submit your sitemap again, so search engines pick up the new addresses quickly.
Why is only one page or the login page not secure?
When just some pages warn, the cause is usually hard-coded http:// links in that page's content, a widget, a form plugin, or an embed from a site without HTTPS.
Open that page's browser console and look for the specific file causing the warning. It is often an old image, a form script, a font or an embedded map.
If an external service does not support HTTPS at all, replace it. Modern browsers block insecure scripts on secure pages, so it would not work properly anyway.
For the login page, make sure the site addresses use https:// and that no plugin forces an http:// login URL.
How do you keep the site secure after fixing the warning?
Make sure the certificate renews automatically, keep the HTTPS redirect in place, and add basic security measures, because HTTPS protects the connection but not the site itself.
Set a reminder to check the certificate's expiry date if renewal is not automatic. Many “Not secure” problems return when a renewal fails silently.
Then look beyond HTTPS: strong passwords, two-factor login, regular updates and backups. Our article on whether WordPress is secure covers the bigger picture.
Frequently asked questions
Does "Not secure" mean my WordPress site is hacked?
No. It means the page loaded over HTTP instead of HTTPS. A hacked site can still show a padlock. If you suspect a hack, look for spam pages, unknown admin users or security warnings from Google instead.
Is an SSL certificate free for WordPress?
Usually yes. Most hosts include free certificates from Let's Encrypt or their own provider and renew them automatically. Paid certificates add warranties or business validation, but the encryption is the same.
Why does my site still say not secure after installing SSL?
The certificate may be installed but not used. Change both site addresses to start with HTTPS in Settings > General, add an HTTP to HTTPS redirect, and fix mixed content where images or scripts still load over HTTP.
Will moving my WordPress site to HTTPS hurt SEO?
Not when done correctly. Use permanent 301 redirects from every HTTP page to its HTTPS version, update internal links, and add the HTTPS version in Search Console. Rankings usually settle within a few weeks.
Can I fix the not secure warning without a plugin?
Yes. Install SSL in your hosting panel, update the site addresses in Settings > General, add a redirect in .htaccess or your host's settings, and run a database search and replace for old HTTP links.
Sources
- Check if a site's connection is secure Google Chrome Help
- HTTPS WordPress Developer Resources
- Mixed content MDN Web Docs
- Let's Encrypt Internet Security Research Group
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


