HTTPS

HyperText Transfer Protocol Secure — the encrypted version of HTTP that protects data in transit and is a Google ranking signal.

Definition

HTTPS (HyperText Transfer Protocol Secure) is the encrypted version of HTTP, using TLS (Transport Layer Security) to encrypt data transmitted between a user's browser and the web server. From an SEO perspective, HTTPS became a ranking signal in August 2014 when Google announced it as a lightweight ranking factor. Today it is effectively a baseline requirement — Google's "Page Experience" quality signals explicitly include HTTPS as a criterion.

Sites still serving content over HTTP display a "Not Secure" warning in Chrome (affecting approximately 65% of global browser market share), which increases bounce rates and reduces trust signals. Google Search Console reports HTTP pages separately from HTTPS, and mixed content (HTTPS page loading HTTP resources) generates browser warnings and degrades the effective security of the page.

Migration from HTTP to HTTPS involves: obtaining an SSL/TLS certificate (free via Let's Encrypt or a commercial CA), configuring server-side HTTPS, implementing 301 redirects from all HTTP URLs to their HTTPS equivalents, updating internal links and canonical tags to HTTPS, and updating the sitemap and Search Console property to reflect the HTTPS version. Check HTTP response headers to verify HSTS (HTTP Strict Transport Security) is implemented to prevent protocol downgrade attacks.

Frequently Asked Questions

How much of a ranking boost does HTTPS provide?

Google describes HTTPS as a 'lightweight' ranking signal — less significant than content quality or backlinks. However, for sites where all else is equal, HTTPS is the tiebreaker, and the trust/UX impact of the 'Not Secure' warning has real behavioral effects that indirectly harm rankings.

What is a mixed content warning and how does it affect SEO?

Mixed content occurs when an HTTPS page loads resources (images, scripts, stylesheets) over HTTP. Browsers block or warn about mixed content, which can break page functionality. From an SEO perspective, mixed content undermines the HTTPS signal and can prevent Google from rendering the page correctly.