Domain migration SEO is the process of moving a website from one domain to another, for a rebrand, merger or country expansion, while carrying its rankings, links and traffic across. Done properly, search engines transfer signals to the new domain with only a short dip. Done carelessly, a business can lose years of organic visibility overnight.
If a domain change is already on your roadmap, tell us your launch date and current setup early. The most important decisions happen weeks before the switch, not on the day.
Why a domain change is riskier than a redesign
A redesign on the same domain keeps its history; only some URLs change. A domain change asks Google to treat a brand-new hostname as the continuation of the old one. Every page, image, backlink and brand mention points to the old address. Unless each old URL redirects precisely to its new equivalent, the authority built up over time leaks away.
Domain changes also tend to coincide with other changes: a new CMS, a new design, new URL structure, merged content from two companies. Each extra variable makes it harder to diagnose problems afterwards. Where possible, keep the URL paths and content identical and change only the domain, then tackle other improvements once the move has settled. For migrations that include a rebuild, our broader guide to SEO migration services covers redesign risks.
Planning your domain migration SEO
Inventory every URL that matters
Combine a full site crawl, XML sitemaps, analytics landing pages, Search Console performance data and backlink exports. Pages that earn traffic or links but no longer appear in navigation are easy to miss, and they are exactly the ones that hurt when they break.
Build a one-to-one redirect map
Each old URL should return a permanent (301 or 308) redirect to its closest new equivalent in a single hop. Avoid sending everything to the new home page; Google tends to treat mass redirects to irrelevant pages like soft 404s. Include old redirect targets too, so existing chains are collapsed rather than extended.
Prepare the new domain
- Verify both domains in Search Console, ideally as domain properties.
- Check the new domain's history for past spam or penalties before committing to it.
- Update canonical tags, hreflang annotations, structured data, internal links and XML sitemaps to use the new domain.
- Confirm SSL certificates, CDN settings and analytics are ready on the new hostname.
Staging checks before launch
Run the redirect map against staging or a test list to confirm every rule returns the right status and destination. Check that the staging site is not indexable, and that robots.txt on the new domain will not block crawling once live.
Launch day and the first weeks
- Switch on redirects at the server or CDN level so they respond quickly and consistently.
- Use the Change of Address tool in Search Console from the old property. It requires both properties to be verified and the old home page to redirect to the new one.
- Submit the new XML sitemap, and keep a sitemap of old URLs available for a while so crawlers revisit them and discover the redirects.
- Update the links you control: social profiles, business listings, email signatures, ad campaigns, partner sites and app store listings.
- Reach out for key backlinks from your most valuable referring sites and ask them to update to the new domain.
Some ranking fluctuation in the first weeks is normal while Google recrawls and processes the move. Watch for crawl errors, unexpected 404s, redirect loops and pages indexed on the old domain long after launch.
What to measure after the move
Agree on a baseline before launch so everyone judges the migration against the same numbers. Useful measures include organic clicks and impressions for both properties in Search Console, indexed page counts on the old and new domains, organic landing page sessions and conversions in analytics, and rankings for a fixed set of priority queries.
In the weeks after launch, compare the new domain's performance with the old domain's baseline at page level, not just site level. A healthy migration shows the old property's impressions falling as the new one's rise. If a section lags, check its redirects, canonical tags and internal links first. Server logs are especially helpful here, because they show whether crawlers are actually following the redirects on the pages that matter.
Keeping the old domain working
Google advises keeping redirects in place for at least a year, and longer is safer, because links and bookmarks keep pointing to old URLs for years. Never let the old domain lapse: renew it, keep its DNS and certificates valid, and keep the redirects running. A lapsed domain can be bought by someone else, who then inherits your old links.
How iJurug Soft runs domain migrations
Domain moves sit at the meeting point of SEO and infrastructure: DNS, certificates, server rules, CDNs and application configuration. iJurug Soft handles both sides with senior engineers, using fixed milestones (Discover, Design, Build, Launch and grow) and a rollback plan prepared before launch. We map redirects, test them, coordinate the cutover with your team and monitor crawling and indexing afterwards. Explore our SEO and cloud services to see how this fits with wider technical work.
Frequently asked questions
How long does it take Google to process a domain migration?
It varies with site size and how often Google crawls it. Smaller sites often settle within weeks, while large sites can take months for every URL to be recrawled. Clean one-to-one redirects make the process faster and more predictable.
Will we lose traffic when changing domains?
A temporary dip is common, but a well-planned domain migration SEO process keeps losses small and short. Bigger drops usually trace back to missing redirects, changed content or technical errors introduced at the same time.
Can we merge two websites into one new domain?
Yes, but it needs extra care. Overlapping pages must be consolidated, the strongest version kept, and both old domains redirected page by page to the right destinations.
Planning a rebrand or domain move? Share your current domain, the new one and your target date through our project contact form, or write to info@ijurugsoft.com. We will review your site, outline the risks and propose a milestone-based migration plan.