How to Fix Not Secure Website in Chrome: A Complete Guide

Seeing a “Not Secure” warning in Chrome can be alarming for both website owners and visitors. If you’re wondering how to fix not secure website in Chrome, you’ve come to the right place. This comprehensive guide will explain why these warnings appear and provide actionable solutions to secure your website properly.

Table of Contents

• Understanding the “Not Secure” Warning
• Why Chrome Shows “Not Secure” Warnings
• How to Fix Not Secure Website in Chrome (For Website Owners)
• What to Do If You See “Not Secure” (For Visitors)
• Preventing Future Security Warnings

Understanding the “Not Secure” Warning

When Chrome displays a “Not Secure” warning, it means the connection between the user’s browser and your website isn’t encrypted. This typically appears when:

• Your site uses HTTP instead of HTTPS
• There are mixed content issues (some elements load over HTTP)
• The SSL certificate is expired or invalid

How Chrome Displays the Warning

Chrome shows this warning in two ways:

1. A gray “Not Secure” text next to the URL in the address bar
2. A red warning page for particularly sensitive pages (like login forms)

Why Chrome Shows “Not Secure” Warnings

Google implemented these warnings to encourage web security best practices. Here are the main reasons your site might trigger this warning:

• Missing SSL Certificate: Your site doesn’t have an SSL/TLS certificate installed
• Mixed Content: Some resources (images, scripts) load over HTTP on an HTTPS page
• Expired Certificate: Your SSL certificate has passed its validity period
• Certificate Errors: Configuration issues with your SSL setup

How to Fix Not Secure Website in Chrome (For Website Owners)

Follow these steps to resolve the “Not Secure” warning on your website:

1. Install an SSL Certificate

The most permanent solution is to migrate your site to HTTPS:

1. Purchase an SSL certificate from your hosting provider or a certificate authority
2. Install the certificate on your web server
3. Configure your server to use HTTPS by default

2. Fix Mixed Content Issues

After moving to HTTPS, ensure all resources load securely:

• Update all internal links to use HTTPS
• Use protocol-relative URLs (// instead of http://)
• Check third-party scripts and plugins for HTTP references

3. Set Up Proper Redirects

Implement 301 redirects to send HTTP traffic to HTTPS:

For Apache servers (.htaccess)
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

4. Update Your HSTS Settings

HTTP Strict Transport Security (HSTS) forces browsers to use HTTPS:

1. Add the HSTS header to your server configuration
2. Submit your site to Chrome’s HSTS preload list

What to Do If You See “Not Secure” (For Visitors)

If you’re seeing the warning as a visitor:

• Don’t enter sensitive information on the page
• Check if the site has an HTTPS version available
• Contact the website owner about the security issue
• Consider using a VPN for additional protection

Preventing Future Security Warnings

Keep your website secure with these best practices:

1. Monitor certificate expiration: Set reminders to renew before expiry
2. Use automated tools: Services like Let’s Encrypt offer auto-renewal
3. Regular security audits: Check for mixed content periodically
4. Keep software updated: Ensure your CMS and plugins are current

Conclusion

Understanding how to fix not secure website in Chrome is essential for maintaining user trust and search rankings. By implementing HTTPS, resolving mixed content issues, and following security best practices, you can eliminate those worrying warnings and provide a safe browsing experience for your visitors.

Ready to secure your website? If you need professional assistance with SSL implementation or website security, contact our team of experts today for a free consultation.