Move a WordPress Site Without Losing Rankings

Moving a WordPress site — new host, new domain, or both — is the general migration discipline with WordPress's specific mechanics attached: the database's serialized URLs, the search-replace step that trips manual movers, and the plugin/host tooling that has made the technical transfer nearly routine while the SEO transfer still rewards care. Here's the procedure split by scenario — because a host move and a domain move are different risk classes wearing one phrase.

Scenario one: new host, same domain (the safe one)

URLs unchanged means SEO risk approaches zero when execution is clean — search engines never see the hosting change except through speed and uptime: the transfer via host migration tools or the duplicator-plugin class (files + database, verified on the new host through a hosts-file preview before DNS), the cutover — DNS TTL lowered in advance, switched in a quiet window, old host kept live through propagation (requests hit both for a day — content freezes during the overlap), the verification — certificate live on arrival (the classic cutover gap), forms/carts tested, and the settings sweep's danger items confirmed (a staging-flavoured backup restoring with the visibility box ticked is this scenario's one famous SEO wound). Expected search impact: none, or mildly positive if the new host clears thresholds the old one failed.

Scenario two: new domain (the real migration)

Everything from the master checklist applies — inventory, exact-counterpart mapping, the settling weeks — with the WordPress particulars: the search-replace step — URLs live in the database serialized, so the move uses proper tooling (WP-CLI's search-replace or the migration plugins that handle serialization — naïve SQL replacing breaks widgets and builder content in ways that surface weeks later); the redirect layer lives at the old domain — the old hosting/domain stays alive indefinitely serving 301s (pattern rule: old-domain/* → new-domain/*, path-preserved — same-structure moves make this one server rule), because the equity transfer lasts only as long as the redirects do; Search Console's Change of Address on top of per-property verification; and the reference sweep — internal absolute URLs (the search-replace catches), then the external world per the checklist: profiles, citations, feeds, and the redirect estate from prior migrations re-pointed to skip the dead hop (chain-flattening at domain scale).

The combined move and the aftermath

Host + domain together: sequence within the project — transfer first, verify on the new infrastructure, then flip domains — so each layer's problems surface separately (the don't-stack doctrine compressed into one project's phases). Aftermath for either scenario, per the monitoring routine: Search Console on both properties (old draining, new indexing), the 404-with-referrers hunt for mapping edges, crawl-diff at week two, and the settling patience — domain moves wobble deeper and longer than same-domain work (trust re-association on top of recrawl), with the recovery shape holding when the mapping held.

Frequently asked questions

How long must the old domain stay registered and redirecting?

Years — practically, as long as meaningful external links point at it (check annually; the answer keeps being "still"). Domain renewal is the cheapest equity insurance that exists; letting a redirecting domain lapse hands your link history to whoever registers it.

Do the all-in-one migration plugins handle the SEO parts?

They handle the transfer (files, database, serialization) excellently — the SEO layer (redirect rules, Search Console, the external sweep, monitoring) is process no plugin performs, which is exactly the gap this guide fills. Technical success and SEO success are separate checklists; the horror stories come from conflating them.

Will we lose rankings moving to a new domain even if we do everything right?

Expect the temporary wobble (weeks, occasionally a quarter for full settling) and near-complete recovery when the mapping is exact and redirects permanent, per the equity findings — the lasting losses in the case files trace to mapping gaps and dead redirects, not to moving per se. And a rebrand's real rebuild is the brand-signal layer — searches, mentions, recognition — which transfers on marketing's timeline, not DNS's (the coverage that rebuilds it — our move).