Before you touch anything
Record the current state. Crawl the site to list every page address, title, description and status. Export top pages and queries from Search Console and your analytics. Take full backups of files and the database. Write down DNS records, email setup, forms, integrations and who holds each login.
Decide what will stay the same, since fewer changes mean fewer risks. Keep addresses identical wherever possible.
Build and test in a private copy
Set up the new site on a staging address blocked from search engines. Check page content, images, internal links, forms, redirects, menus, and mobile layout. Compare the new crawl with the old and look for missing pages or changed titles. Test speed, accessibility basics and structured data.
Make sure the staging copy is not indexed, and plan how that block will be removed at launch.
Map redirects
Where addresses change, build a one-to-one redirect map from each old address to its closest new counterpart. Use permanent redirects. Include old image and file links that have many references. Avoid sending everything to the home page.
If the domain is changing, keep the old domain registered and redirecting for a long time.
Launch day
Choose a quiet time. Lower DNS TTL beforehand. Switch DNS or deploy, then immediately verify the home page, key service pages, forms, SSL, redirects and email. Remove the staging noindex and check the robots file. Submit the new sitemap and, for a domain change, use the change of address tool in Search Console.
Keep the old site available as a fallback for a couple of weeks, but avoid editing both.
The first thirty days
Watch Search Console for crawl errors, coverage warnings and drops in impressions. Monitor analytics for traffic and conversion changes, and fix broken links you find. Some fluctuation is normal while search engines reprocess the site. A sharp, lasting fall points to a missing redirect, a noindex, or a blocked crawl.
Update external listings, social profiles, email signatures and your Google Business Profile to the final address.
Ask for help where it counts
If your site earns leads from search, a mistake costs money. Consider a professional review of the redirect map and launch checklist before going live. A short audit beforehand is cheaper than a recovery afterwards.
A useful rule of thumb is to treat the migration as two projects: the technical move and the content review. Do the move with as little change as possible, confirm everything works, and only then start improving pages. Mixing a redesign, new copy and a new host into one weekend makes any drop in traffic nearly impossible to diagnose. Write the plan down and assign an owner for each step, including who confirms email is working after launch.
Keep screenshots of key pages and a copy of the old title tags. If something looks different after launch, you can compare quickly rather than relying on memory.
Common questions
How long does recovery take if traffic dips?
If the cause is fixed, many sites stabilize within weeks, though timing varies.
Should I change the design at the same time as moving?
Doing both increases risk. Separating them makes problems easier to trace.
Do I need to tell Google about a hosting-only move?
No special notice is needed if the addresses stay the same.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.