When this applies
Domain migrations happen for rebranding, mergers, moving from a subdomain to the main domain, switching country domains or consolidating several sites. Search engines treat the new domain as a different site. A well-run migration transfers most of the old site’s signals, but dips are common, and a poorly run one can be damaging for a long time.
This checklist focuses on the domain change itself. Redesigns and platform changes at the same time multiply the risk, so separate them if possible.
Before you start
- Decide whether you must migrate. Understand the business reason and the SEO cost.
- Choose the new domain carefully. Check its history. A domain with a spam past or penalties can hold you back.
- Benchmark. Export organic traffic, rankings, top pages, conversions, backlinks and crawl data from the old site.
- Set a launch window outside peak season.
- Verify ownership of both domains in Search Console, covering all properties, including http and https and with and without www.
- Lower DNS TTL ahead of launch so changes propagate faster.
URL mapping
- Crawl the old site to list all URLs, including images and documents with value.
- Combine with URLs from analytics, Search Console and backlink data to catch pages not found in the crawl.
- Map each old URL to its new equivalent, one-to-one wherever possible.
- Keep paths identical across domains where you can, so the mapping becomes a simple host change.
- For removed pages, redirect to the closest relevant page, not the homepage.
- Document the map and review it with stakeholders.
Build and test the new site
- Replicate content, titles, headings, meta descriptions, structured data and internal link structure.
- Set canonical tags to the new domain.
- Update hreflang tags if used.
- Update internal links and absolute URLs to the new domain.
- Create new XML sitemaps.
- Prepare the new robots.txt, and make sure it does not block crawling.
- Block the staging environment from indexing, and confirm those blocks are removed at launch.
- Test redirects in bulk on staging, and check for chains and loops.
- Configure HTTPS with a valid certificate and security headers.
Launch day
- Deploy the new site on the new domain.
- Implement server-side 301 redirects from every old URL, preserving paths and query strings where needed. Avoid JavaScript or meta refresh redirects.
- Verify a sample of redirects across page types.
- Submit the change of address in Search Console for the old property, where the tool applies.
- Submit new sitemaps, and consider keeping the old sitemap temporarily to help discovery of redirects.
- Check analytics, tag manager and conversion tracking on the new domain.
- Confirm robots.txt and indexing directives.
- Crawl the live site, and fix issues quickly.
Update external references
- Ask owners of the highest-value backlinks to update their links. Redirects pass signals, but direct links are cleaner.
- Update social profiles, Google Business Profile, directories, app listings, email signatures and advertising destinations.
- Update third-party services that include your URL, such as payment gateway return URLs, email authentication records, OAuth redirect URIs and webhooks.
- Update print and offline materials over time.
Email and DNS considerations
If your email addresses change domain, plan the transition separately, including SPF, DKIM and DMARC records and forwarding from old addresses. Keep the old domain’s email working during the transition.
Monitor closely
| Timeframe | What to check |
|---|---|
| First days | Crawl errors, redirect behavior, indexing of new URLs, server errors, tracking |
| First weeks | Impressions, clicks and rankings on both properties, coverage reports, 404s from external links |
| First months | Traffic recovery, new vs old domain indexation, backlink updates |
| Long term | Keep redirects for at least a year, preferably longer or indefinitely for important URLs |
Expect temporary fluctuation as search engines process the move. Persistent drops point to missed redirects, blocked crawling or content differences.
Keep the old domain
Do not let the old domain expire, and keep it pointed to servers that serve the redirects. If you lose it, someone else could register it and benefit from its links.
Common mistakes
- Redirecting everything to the homepage.
- Forgetting the staging noindex or leaving robots.txt blocking the new site.
- Canonicals pointing to the old domain.
- Leaving redirect chains.
- Not verifying every protocol and subdomain variant in Search Console.
- Ending the redirects too soon.
- Changing content, structure and domain simultaneously without a plan.
FAQ
Will I lose rankings if I change domains?
Some fluctuation is common. With correct redirects, matching content and good monitoring, most sites recover most of their visibility, but there are no guarantees.
How long should I keep redirects?
At least a year, and indefinitely for pages that still receive traffic or links, as long as you control the old domain.
Should I use the change of address tool?
Yes, when moving between domains where it applies. It signals the move to Google. It does not replace redirects.
Can I move in phases?
Yes, for large sites. Moving section by section reduces risk, but requires careful tracking and consistent redirect rules.
TURN INSIGHT INTO ACTION
Let’s talk about your next step.
Share your workflow, your current systems and what you want to improve. We’ll help shape a practical way forward.
Discuss your project ↗