Moving to HTTPS without splitting your site in two
You are adding HTTPS and want to be sure you end up with one site rather than two copies competing.
Short answer
The risk in an HTTPS move is not the certificate, it is ending up with both versions reachable and indexed, splitting links and history across two copies of every page. Redirect every http URL to its https equivalent permanently, make canonicals and internal links absolute on https, and confirm no page serves on both.
The actual risk
Search engines treat http and https as different sites. If both respond, you have two of everything, each with a share of your links and none with all of them. The certificate is the easy part; consolidation is the part that goes wrong.
Redirect at the server, once
A permanent redirect from http to https for every path, applied at the edge or the server rather than in application code. Not a meta refresh, not JavaScript. One hop straight to the https version of the same path, preserving the path and query.
Fix the things that still say http
Canonicals, internal links, sitemap entries, structured data URLs, and any absolute link in your content. Each one that still points at http forces a redirect that did not need to happen and quietly signals that you consider http the real address.
Mixed content
A page served over https that loads an image, script or stylesheet over http is either blocked or flagged. This is a user-facing correctness problem before it is an SEO one, and it usually traces to hardcoded absolute URLs in old content.
Search Console treats it as a new property
The https version is a separate property in the URL-prefix model. Add and verify it, submit the https sitemap, and keep the http property so you can watch the old URLs being recrawled. A Domain property covers both, which is one good reason to use one.
HSTS, once you are confident
Telling browsers to only ever use https removes the redirect hop entirely for repeat visitors. Add it after you are certain everything works on https, because it is difficult to undo quickly if something is still broken.
What to expect
Minor and short-lived turbulence during recrawl. HTTPS itself is a lightweight ranking signal and nobody should expect a visible lift from it. The reason to do it is that browsers increasingly mark http as insecure, which is a conversion problem long before it is a ranking one.
Questions
- Is HTTPS a ranking factor?
- Yes, and a small one, confirmed years ago as a lightweight signal. Nobody should migrate expecting a rankings lift. Migrate because browsers flag http as not secure and because it is table stakes for trust.
- Will I lose rankings during the switch?
- Usually a brief dip during recrawl, then recovery. Sustained loss points to a specific fault: both versions still reachable, canonicals still on http, or a redirect that skipped a directory.
- Do I need to resubmit my sitemap?
- Yes, with https URLs, and update the Sitemap line in robots.txt. Leaving an http sitemap in place keeps pointing crawlers at URLs that now only redirect.
Measured, not asserted
The two-copies problem is not hypothetical. On ihatepdf.cv, which reached 100,542 users, the www and non-www versions of the homepage both appear as separate rows in the same Search Console export, each with its own clicks. Host and protocol variants split a page exactly the same way.
Free tool for this: SERP Audit. No account, nothing uploaded.
Where this goes deeper
Every number on this page comes from one complete dataset: one product taken from zero to 100K+ users on search alone, with nothing spent on advertising. The full argument is Chapter 10 and Chapter 22 of the book. Five chapters are free to read.