Does HTTPS still give a ranking edge or is it just baseline?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 3
Treat it as baseline. Google announced HTTPS as a ranking signal in August 2014 and called it then “a very lightweight signal”, affecting “fewer than 1% of global queries”. Its current page experience documentation still asks “Are your pages served in a secure fashion?”, but it names Core Web Vitals as the page experience aspect its ranking systems use and says “Beyond Core Web Vitals, other page experience aspects don’t directly help your website rank higher in search results.” So do not expect a switch to HTTPS to move a page up noticeably on its own. Not having it costs you in ways that have nothing to do with ranking.
What HTTPS does and does not do
| Effect | |
|---|---|
| Ranking | Announced in 2014 as a very lightweight signal; Google's current page experience guidance describes no direct lift beyond Core Web Vitals |
| Visitors | Encrypts the connection, so forms and logins are not sent in plain text, and avoids security warnings browsers show on insecure pages |
| Features | Modern browser features and some third-party services require a secure connection |
| Canonicalization | When both HTTP and HTTPS versions exist, Google's guidance on consolidating duplicates points to redirecting HTTP to HTTPS and listing HTTPS URLs in sitemaps |
Where sites still get it wrong
The problem to check for today is not missing HTTPS but a messy setup:
- both HTTP and HTTPS versions load, with no redirect between them, so Google sees duplicates;
- internal links, canonicals, or the sitemap still use
http://addresses after the move; - pages load over HTTPS but pull images or scripts over HTTP, which browsers can block or flag;
- the certificate does not cover every hostname in use, such as the
wwwand non-wwwversions.
Each of these is a configuration fix. Redirect every HTTP URL to its HTTPS equivalent in one hop, without stacking it on older redirects, a risk explained in when a redirect chain becomes a real problem, update internal links and canonicals, and make sure the certificate covers each host.
How to think about it
HTTPS is a requirement for a site that visitors and browsers trust, not a ranking lever to count on. Google’s site move guidance notes that you do not need the Change of Address tool for HTTP to HTTPS moves, but the move is still a URL change with a recrawl behind it. If you are still on HTTP, move for your visitors’ sake and expect stability rather than a jump; if you are already on HTTPS, spend your ranking effort on the page itself.
Add a comment