Changing your domain name, after a rebrand, a merger, or to move from a hyphenated .co to a clean .com, is one of the riskiest things you can do to your search traffic. It's also routine when done carefully. The key is that every old address must lead to its exact new equivalent, and Google must be told clearly what's happening.

Here's the plan we use for client domain migrations.

Before you start

Choose the new domain carefully

Check its history (has it been used for spam?), trademark conflicts and social handles. Our domain registration check shows registration details. Read how to name a business and how to trademark your business name.

Pick a quiet time

Avoid your busiest season. For shops, never migrate in November or December.

Benchmark everything

Record current traffic, rankings for key terms, top landing pages, conversions and indexed pages from Search Console. You'll need these to judge recovery.

Step 1: Crawl and export every URL

Collect every URL on the old site from:

  • A full site crawl.
  • Your XML sitemap.
  • Search Console's Pages and Performance reports.
  • Analytics landing pages (last 12 months).
  • Pages with backlinks (from Search Console's Links report or an SEO tool).

Old campaign URLs and PDFs count too.

Step 2: Build a redirect map

A spreadsheet with every old URL and its new equivalent:

Old URLNew URLNotes
oldbrand.co.uk/services/web-designnewbrand.com/services/web-designSame path
oldbrand.co.uk/blog/seo-tips-2024newbrand.com/articles/seo-tipsPath changed
oldbrand.co.uk/old-offernewbrand.com/offersClosest equivalent

If paths stay the same, a single pattern rule can handle most pages. Where paths change, map them individually. Only redirect to the home page when there's genuinely no equivalent, and consider letting truly obsolete pages return 410.

Read 301 vs 302 redirects: domain moves need permanent 301 (or 308) redirects.

Step 3: Prepare the new site

  • Same content and URL structure where possible.
  • Canonical tags pointing to the new domain.
  • Internal links updated to the new domain (not relying on redirects).
  • Hreflang tags updated if you have international versions. See hreflang explained.
  • Structured data, Open Graph tags and sitemaps using new URLs.
  • Robots.txt allowing crawling (a common mistake is launching with a staging block still in place).
  • HTTPS working on every version (with and without www).

Step 4: Verify both domains in Search Console

Add and verify the new domain as a property before launch. Keep the old property verified.

Step 5: Launch and redirect

  1. Put the new site live.
  2. Switch on redirects from every old URL to its new URL, with a single hop (no chains).
  3. Test a sample of URLs from each section with our redirect checker.
  4. Submit the new XML sitemap in Search Console. Keeping the old sitemap available for a few weeks can help Google find and follow the redirects.

Step 6: Use the Change of Address tool

In the old domain's Search Console property, go to Settings → Change of address and select the new property. Google checks that the home page and some sample pages redirect correctly, then prioritises processing the move. This is one of the most important steps and often forgotten.

Step 7: Update everything else

  • Google Business Profile website link.
  • Google Ads and other ad platforms' final URLs.
  • Social media profiles and bios.
  • Email signatures and templates.
  • Directory listings and partner sites. Ask important linking sites to update their links.
  • Payment providers, app stores, OAuth callback URLs and integrations.
  • Email sending domain authentication (SPF, DKIM, DMARC) if email moves too. Check with our DNS and email health checker.

Step 8: Monitor for three months

CheckWhen
Crawl errors and 404s in Search ConsoleDaily for two weeks, then weekly
Indexed pages: old declining, new risingWeekly
Traffic and conversions vs benchmarkWeekly
Rankings for key termsWeekly
Redirects still workingAfter any server change

Fix any 404s by adding missing redirects. Our broken link checker helps find leftovers.

Step 9: Keep the old domain forever

Keep renewing the old domain and keep redirects in place for at least a year, ideally indefinitely. If it expires, someone else can buy it and your old links will point to them. Read domain name security.

How long recovery takes

Small sites often settle within a few weeks. Larger sites can take several months for Google to fully process every URL. A temporary dip is normal; a sustained drop usually means missing redirects, blocked crawling or content changes.

The short version

Benchmark first, crawl every old URL, map each to its exact new equivalent, launch with single-hop 301 redirects, use Search Console's Change of Address tool, update every external reference and monitor closely for three months. Keep the old domain and its redirects indefinitely.

Planning a rebrand or domain move? Our web development team handles migrations end to end. Moving shop platforms too? Read migrating e-commerce platforms without losing SEO.