HTTPS and SEO: Does SSL Help Rankings, and How Do You Switch?

Short answer: HTTPS helps, but only a little, as a ranking factor. Google announced it as a signal in 2014 and called it “very lightweight”, affecting “fewer than 1% of global queries” and carrying less weight than high-quality content. It’s also part of page experience. The stronger reasons to use HTTPS are visitor trust (browsers flag HTTP pages as not secure) and modern browser features that require it. If you’re still on HTTP, switch: treat it as a site move, redirect every http URL to its https version with a 301, and submit an https sitemap.

What Google has actually said

• 2014, “HTTPS as a ranking signal”: HTTPS became a ranking signal, described as very lightweight and weaker than signals such as high-quality content. Google said it might strengthen it over time to encourage everyone to switch.
• Page experience: Google’s page experience guide asks site owners, “Are your pages served in a secure fashion?” It also says there is no single page experience signal and that relevant content still comes first.
• Canonicalization: when the same page exists on http and https, Google prefers the HTTPS URL as the canonical.

So don’t expect a ranking jump from adding a certificate. Do expect problems if your site is still on HTTP: duplicate http/https versions, browser warnings, and visitors who leave.

Check your current setup

curl -sI http://example.com/      | grep -iE '^(HTTP|location)'
# want: HTTP/1.1 301 ... location: https://example.com/
curl -sI https://example.com/page | head -1
# want: HTTP/2 200 (one redirect at most from any http URL)

• Every http URL redirects to the matching https URL in one step (not all to the homepage).
• Canonical tags, internal links and the sitemap use https URLs.
• No mixed content: the https page doesn’t load images, scripts or styles over http.
• robots.txt doesn’t block the https site, and pages aren’t noindexed. Google’s 2014 tips called both out.

How to move from HTTP to HTTPS

Google treats this as a site move with URL changes. In short:

1. Install a valid TLS certificate covering every hostname you use (for example both example.com and www.example.com).
2. Add and verify the https property in Search Console (a Domain property covers both protocols).
3. Update internal links, canonicals, hreflang and structured data to https.
4. Turn on server-side 301 (or 308) redirects from each http URL to its https twin.
5. Fix mixed content so pages load every resource over https.
6. Submit an https sitemap and update the Sitemap: line in robots.txt.
7. Monitor Search Console and your logs while Google recrawls; expect some fluctuation for a few weeks.

Change of Address isn’t used for a protocol change. The full step-by-step is in our SEO migration checklist. If your sitemap still lists http URLs afterwards, see HTTP URLs in an HTTPS sitemap. The free sitemap checker tests 30 sitemap URLs and lists any that redirect.

HSTS: the last step

Once everything works over https, a Strict-Transport-Security header tells browsers to always use https for your domain, which removes the http hop for returning visitors. Start with a short max-age, confirm nothing breaks, then raise it.

Frequently asked questions

Related guides

• SEO Migration Checklist
• HTTP URLs in an HTTPS Sitemap
• www vs non-www Redirect
• Core Web Vitals