Why do HTTPS and redirects matter for SEO?
Because your site can answer at four different addresses (http, https, with www and without) and Google treats them as different URLs. With HTTPS everywhere, permanent redirects to one version and HSTS, you concentrate signals on one URL and protect your visitors.
Google announced in 2014 that HTTPS is a ranking signal. More important than the signal itself: a single version avoids duplicate content and split links.
Which redirect should you use in each case?
| Code | Type | When to use it |
|---|---|---|
| 301 / 308 | Permanent | Lasting change: http to https, new domain, a URL that changed for good |
| 302 / 307 | Temporary | Promotions or maintenance; Google does not treat it as a canonical signal |
| meta refresh / JavaScript | Client side | Only if you cannot configure the server |
According to Google's redirects documentation, a permanent redirect signals that the target should be canonical, and a server-side redirect has the highest chance of being interpreted correctly.
How do you check your site step by step?
One version
- 01
Try all four addresses
Open http://, https://, with www and without. All four should end at the same URL.
- 02
One hop
Each variant should reach the target with a single redirect, not a chain of two or three.
- 03
Permanent, not temporary
Make sure the redirect returns 301 or 308, not 302.
- 04
Consistent canonical
Each page's canonical tag should point to the final https version.
- 05
Links and sitemap up to date
Your sitemap and internal links should use the final URL, not the one that redirects.
- 06
Turn on HSTS
Once everything works on HTTPS, add the Strict-Transport-Security header.
What is HSTS and how do you enable it safely?
HSTS is an HTTP header that tells the browser to always use HTTPS for your domain for the time you set, never going through http. The MDN documentation explains its three options:
Strict-Transport-Security: max-age=31536000; includeSubDomains
- max-age: seconds the browser will remember to use HTTPS only (31536000 is one year).
- includeSubDomains: also applies to every subdomain. Enable it only if all of them have HTTPS.
- preload: asks to join the list browsers ship with. Getting off it is slow; read hstspreload.org first.
Which mistakes cost rankings?
The ones we see most: redirecting everything to the home page instead of the equivalent URL, using 302 for a permanent change, leaving redirect chains after several migrations and canonicals pointing to the http version. Check them in the SEO audit; an extra redirect also adds load time, as covered in Core Web Vitals.
The Market OS HTTPS, headers and redirects tool follows your domain's redirect chain, checks HSTS and canonical and tells you what to change. Meanwhile, see the other free tools on the way.
Tell me when it is ready →Frequently asked questions
Will I lose rankings moving from http to https?
With page-by-page 301 redirects and updated canonicals and sitemap, Google consolidates signals on the new version. Expect some movement while it recrawls.
Is www or non-www better?
Google does not mind. What matters is choosing one and permanently redirecting the other.
301 or 308?
Both are permanent for Google. 308 keeps the request method; for regular pages 301 is the most common.
Does HSTS improve SEO?
It is not a documented ranking signal. It avoids trips through http and protects your visitors.
How long should I keep a redirect?
As long as there are links or visits to the old URL. For a domain change, keeping it for a long time is recommended.
Sources
- Google Search Central: Redirects and Google Search
- Google Search Central: Consolidate duplicate URLs
- Google Search Central Blog: HTTPS as a ranking signal (2014)
- MDN: Strict-Transport-Security
- hstspreload.org: HSTS preload list
Written by Samuel Hinojosa, WITS · Updated November 1, 2026 · Markdown




