--- title: "HTTPS" description: "HyperText Transfer Protocol Secure — the encrypted version of HTTP that secures data transmission between a user's browser and a web server using TLS/SSL certificates, protecting against data interception and man-in-the-middle attacks." url: "https://skribra.com/glossary/https" type: "glossary-term" category: "Technical SEO" updated: "2026-06-09" --- # HTTPS **Definition.** HyperText Transfer Protocol Secure — the encrypted version of HTTP that secures data transmission between a user's browser and a web server using TLS/SSL certificates, protecting against data interception and man-in-the-middle attacks. **In short.** HTTPS encrypts the connection between your site and visitors. Google uses it as a ranking signal (since 2014) and Chrome flags HTTP sites as 'Not Secure.' There is no reason not to use HTTPS — free certificates are available via Let's Encrypt. ## Key points - Google confirmed HTTPS as a lightweight ranking signal in 2014; it became a stronger signal over time as adoption increased - Chrome marks all HTTP pages as 'Not Secure' since 2018, creating a UX and trust problem independent of SEO impact - HTTPS migration requires proper 301 redirects from all HTTP URLs to their HTTPS equivalents to preserve link equity - HTTP/2 and HTTP/3 (which offer significant performance improvements) require HTTPS — HTTP-only sites are locked out of these protocols ## HTTPS as a Ranking Signal Google confirmed HTTPS as a ranking signal in August 2014, initially describing it as a 'lightweight' signal affecting fewer than 1% of queries[1]. The signal has been strengthened over time as HTTPS adoption became widespread — what was once a differentiator is now effectively table stakes. The more significant impact for most sites isn't the direct ranking boost from HTTPS itself, but the ranking cost of not having it: HTTP sites trigger browser security warnings that increase [bounce rates](https://skribra.com/glossary/bounce-rate), users distrust non-secure sites for form submissions, and [backlinks](https://skribra.com/glossary/backlink) from HTTPS pages to HTTP pages create mixed-content concerns. Any new site or migration should default to HTTPS — the Let's Encrypt certificate authority provides free, auto-renewing TLS certificates. ## HTTPS Migration Checklist Migrating from HTTP to HTTPS requires careful execution to avoid losing organic rankings[1][2]. The required steps: (1) Obtain and install an SSL/TLS certificate. (2) Update all [canonical tags](https://skribra.com/glossary/canonical-url) and [sitemap URLs](https://skribra.com/glossary/sitemap) to use HTTPS. (3) Implement [301 redirects](https://skribra.com/glossary/301-redirect) from every HTTP URL to its HTTPS equivalent — this transfers link equity and prevents [duplicate content](https://skribra.com/glossary/duplicate-content) issues. (4) Update all [internal links](https://skribra.com/glossary/internal-linking) to HTTPS URLs. (5) Update [Open Graph tags](https://skribra.com/glossary/open-graph), robots.txt, and any hardcoded absolute URLs. (6) Verify the HTTPS version in [Search Console](https://skribra.com/glossary/google-search-console) and submit the HTTPS sitemap. (7) Update external backlinks where possible (contact webmasters of major linking sites). Monitor [Crawl Errors](https://skribra.com/glossary/crawl-errors) in Search Console post-migration to catch any missed redirects. ## HTTPS and Performance HTTPS enables significant [performance improvements](https://skribra.com/glossary/page-speed) beyond security[2]. HTTP/2, the successor to HTTP/1.1, requires HTTPS and provides multiplexing (multiple requests over one connection), header compression, and server push — features that can dramatically reduce page load time on asset-heavy pages. HTTP/3 (based on QUIC) similarly requires HTTPS and provides better performance especially on mobile networks with packet loss. TLS handshake overhead (the extra round-trip to establish an encrypted connection) is offset by session resumption and TLS 1.3 improvements that make encrypted connections negligibly slower than unencrypted ones. In practice, sites that migrate to HTTPS and HTTP/2 typically see page load time improvements, not increases, compared to HTTP/1.1. ## Related terms - [301 Redirect](https://skribra.com/glossary/301-redirect): An HTTP status code that permanently redirects one URL to another, telling browsers and search engines that the original page has moved and passing the majority of its link equity to the new destination. - [Canonical URL](https://skribra.com/glossary/canonical-url): An HTML tag that tells search engines which version of a page is the preferred, authoritative URL when multiple URLs serve the same or very similar content. - [Page Speed](https://skribra.com/glossary/page-speed): The amount of time it takes for a web page to load and become usable for a visitor — a direct Google ranking factor measured by Core Web Vitals metrics including Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. - [Crawl Errors](https://skribra.com/glossary/crawl-errors): Problems that search engine crawlers encounter when attempting to access and process pages on a website — including HTTP errors (404, 500), redirect issues, and DNS failures — which prevent pages from being properly indexed. ## Sources 1. [Google Search Central — HTTPS as a Ranking Signal](https://developers.google.com/search/blog/2014/08/https-as-ranking-signal) 2. [Semrush — HTTP vs. HTTPS: Why It Matters for SEO](https://www.semrush.com/blog/http-vs-https/) ## Machine-readable index - HTML version of this page: https://skribra.com/glossary/https - Site index for agents: https://skribra.com/llms.txt - Sitemap: https://skribra.com/sitemap.xml - Public REST API: https://skribra.com/api/v1 - OpenAPI specification: https://skribra.com/openapi.json