HTTPS
Secure, encrypted version of HTTP that protects data in transit.
What is HTTPS?
HTTPS (Hypertext Transfer Protocol Secure) is the secure version of HTTP, using SSL/TLS encryption to protect data transmitted between a user's browser and your website. It's indicated by a padlock icon in the browser and the https:// URL prefix.
Google confirmed HTTPS as a ranking signal in 2014. Today, it's essentially required - browsers warn users about non-HTTPS sites, and most SEO best practices assume HTTPS.
Why HTTPS matters
HTTPS is a confirmed Google ranking factor and user trust signal. Chrome and other browsers mark HTTP sites as "Not Secure," which damages credibility and increases bounce rates. HTTPS is required for many modern features like service workers and geolocation.
How to implement
Obtain SSL/TLS certificate (free from Let's Encrypt)
Install certificate on web server
Redirect all HTTP URLs to HTTPS
Update internal links to HTTPS
Update canonical tags and sitemaps
Check for mixed content warnings
Common mistakes to avoid
- Having mixed HTTP/HTTPS content on pages
- Not redirecting HTTP to HTTPS properly
- Letting SSL certificates expire
- Using outdated TLS versions
Examples
http://example.com → https://example.com (301 redirect)
Mixed content: HTTPS page loading HTTP images (warning)
Valid SSL: Green padlock in browser
Frequently asked questions
Practically yes. While technically a minor ranking factor, the trust and security implications make HTTPS essential. Users and browsers expect it.
Modern HTTPS with HTTP/2 is actually faster than HTTP/1.1. Initial SSL handshake adds minimal latency, offset by protocol improvements.