Domain Migration and Redesign Planning: Moving Content Without Losing Value

Moving a website from one domain to another — or fundamentally redesigning an existing site — carries real SEO and business risk. Done poorly, a migration can wipe out months or years of organic search rankings, break inbound links, and destroy the traffic that makes a developed domain valuable. Done correctly, it preserves existing value and can even improve performance. The difference comes down to planning, execution, and monitoring.

When Domain Migration Makes Sense

Not every domain change is necessary. Migrations introduce risk, so you should only migrate when the benefit clearly outweighs the cost.

Legitimate reasons include rebranding to a shorter or more brandable domain, consolidating multiple domains into one authority property, moving to a more relevant TLD (such as switching from a .net to the .com you just acquired), or selling a developed domain where the buyer needs content moved to their infrastructure.

Migrations that rarely justify the risk include switching domains purely because you found one that is slightly better (marginal improvements rarely compensate for the ranking disruption), or changing URLs for cosmetic reasons like removing dates or category prefixes when the existing URL structure works.

Pre-Migration Checklist

Before touching any DNS settings, complete this preparation.

Crawl your existing site. Use Screaming Frog, Sitebulb, or a similar crawler to export every URL on the current domain. This includes HTML pages, images, PDFs, and any other resources that might have inbound links or search engine indexing. You need a complete inventory so nothing gets missed during the redirect mapping.

Create a redirect map. Build a spreadsheet mapping every old URL to its corresponding new URL. Every page on the old domain needs a 301 redirect to the equivalent page on the new domain. If a page on the old domain has no equivalent on the new domain, redirect it to the most topically relevant alternative rather than dumping everything to the homepage.

Benchmark current performance. Record your current organic traffic, keyword rankings, and inbound link counts. Use Google Search Console, Google Analytics, and a tool like Ahrefs or Semrush to capture baseline metrics. You need these numbers to measure the migration’s impact and identify any recovery issues.

Set up Google Search Console for the new domain. Verify ownership of the new domain in Search Console before the migration. This allows you to use the Change of Address tool, which explicitly tells Google that your site has moved from one domain to another. This is the single most important step for preserving search rankings during a domain change.

Reduce DNS TTL. At least 48 hours before the migration, reduce the TTL on your DNS records from the typical 3600 or 14400 seconds down to 300 seconds (five minutes). This ensures that when you update DNS to point to the new server, the change propagates quickly and users stop seeing the old site faster.

Executing the Migration

On migration day, follow this sequence.

First, deploy the new site on its new domain with all content in place and verified. Test every page before making the switch live. Second, implement 301 redirects from every old URL to its mapped new URL. Use server-level redirects (in .htaccess for Apache, nginx config, or Cloudflare rules) rather than JavaScript redirects, which search engines handle less reliably. Third, use Google Search Console’s Change of Address tool to notify Google of the domain change. Fourth, update your XML sitemap to reflect new URLs and submit it through Search Console for the new domain. Fifth, update internal links throughout the site to use the new domain’s URLs rather than relying on redirects for internal navigation.

301 Redirects: The Critical Detail

The 301 redirect is the load-bearing element of any domain migration. It tells search engines that a page has permanently moved to a new address and that all ranking signals (backlinks, PageRank, topical authority) should be transferred to the new URL. Google has confirmed that 301, 302, and other server-side redirects do not cause PageRank loss, but 301 is the correct signal for permanent moves.

Redirect every URL individually. Do not redirect everything to the new homepage. A blanket redirect throws away all the page-level ranking signals you have built. Each old URL should point to its specific new equivalent.

Avoid redirect chains. If the old URL already redirects somewhere, update it to point directly to the final destination rather than chaining through an intermediate URL. Redirect chains slow down crawling and can cause search engines to lose patience before reaching the final page.

Keep redirects active indefinitely. There is no safe point to remove redirects after a migration. Inbound links from other websites will continue pointing to the old URLs for years. Maintain the redirects as long as you control the old domain.

Post-Migration Monitoring

The first four to twelve weeks after migration are critical. Expect some ranking fluctuation as search engines process the change.

Monitor Google Search Console for both the old and new domains daily during the first two weeks, then weekly for the next three months. Watch for crawl errors (pages returning 404 that should be redirecting), indexing drops (pages being removed from the index faster than new pages are being added), and ranking shifts on your key terms.

Check your redirect map against actual crawl data. Use Screaming Frog to crawl the old domain’s URL list and verify that every URL returns a 301 to the correct new destination. Fix any 404s or incorrect redirects immediately.

A typical migration experiences a 10 to 20 percent traffic dip in the first two to four weeks, followed by a recovery to baseline by week eight to twelve. If you see a deeper or more prolonged drop, audit your redirect map for errors, check that the Change of Address tool was properly configured, and verify that the new site’s content matches what was on the old domain.

Selling a Developed Domain: Buyer Handoff

When you sell a developed domain, the buyer often needs help migrating the content to their own hosting infrastructure. Providing a complete redirect map, a copy of the site’s content and database, and access to historical Google Search Console data makes the transition smoother and protects the domain’s value through the handoff.

Include a migration support clause in your sales agreement if the domain has significant organic traffic. Offering 30 to 60 days of redirect support (keeping the old domain pointing to the buyer’s new setup) adds value to the sale and can justify a higher price.

For DNS configuration during migration, see domain CNAME and A records explained. For technical SEO considerations that affect migration success, check out technical SEO for developed domains.