How a site migration works
A migration is any change to what your addresses are or where they live. Moving to a new domain is one. So is switching from HTTP to HTTPS, rebuilding on a different platform, restructuring folders, merging two sites into one, or launching a redesign that quietly rewrites addresses along the way. The visible work is design and content; the search work is address mapping.
Rankings, links and history attach to individual addresses, not to a brand. When an address changes, everything it earned has to be transferred deliberately, with a permanent redirect from the old address to the page that now does the same job. Search engines then re-crawl, re-map and gradually treat the new address as the successor. None of that happens on its own.
Why site migrations matter
This is the fastest way to lose traffic that took years to build. A launch that goes badly does not degrade gently — visibility falls within days, and recovery takes far longer than the loss did. A redesign can be an improvement in every visible respect and still stop the enquiries, simply because the old addresses had nowhere to land.
It also matters commercially because the risk is invisible to almost everyone involved. Designers, developers and copywriters can each do excellent work while the thing that actually carries your search visibility breaks in the background, and nobody notices until the first quiet week.
Where site migrations go wrong
Nearly always in the same places. No inventory taken beforehand, so nobody knows which addresses existed. Old pages sent to the homepage in bulk instead of to their real equivalents, which search engines increasingly treat as the page having gone. Redirect chains left behind after a second change, so a request hops through several stops before it lands. Sitemaps, internal links and canonical tags still pointing at addresses that no longer exist.
Two more catch people out regularly. Launching with the staging site’s blocking rules still in place, so the new site politely asks search engines to stay away. And changing addresses, design, content and platform in a single release, which means that when something goes wrong there is no way to tell which change caused it.
Getting it right
Start with a full crawl of the existing site and a list of the pages that genuinely earn traffic, links and enquiries. Map every old address to one new address, page by page, to the closest real equivalent — never to the homepage as a catch-all. Decide before launch which pages are being retired on purpose, and let those return a gone status rather than redirecting them somewhere irrelevant.
On launch day, check the blocking rules first, then the redirects, then the tracking, in that order. Afterwards keep watching: server logs and Search Console will show which old addresses are still being requested and which redirects are failing, usually for weeks. Planning that sequence in advance is the point of website migration SEO, and it is worth agreeing who owns it before the build starts rather than in the week after go-live.
