How does domain change SEO work?
Domain change SEO works by moving your existing signals, such as links, rankings and brand searches, from the old domain to the new one with permanent redirects. Google treats a well-redirected domain move as the same site at a new address. A badly redirected one looks like a new site starting from zero.
A domain change is the riskiest kind of migration because every single URL changes. That's why it deserves its own plan on top of our website migration SEO checklist. Most domain changes happen during a rebrand, so this guide is written for that case: new name, new domain, and often a new site.
Forum threads about a 90% traffic drop after a domain move are a familiar sight on platform forums. The answer is nearly always the same: the redirects weren't page to page, or the old domain stopped redirecting.
How do you change your domain without losing SEO?
You change domain without losing SEO by mapping every old URL, launching page-level 301s on the day of the switch, and then confirming Google sees the move. The order below keeps risk low.
Benchmark the old domain
Export Search Console performance, a full crawl, top linked pages and analytics before anything changes.
Verify both domains
Add the new domain to Search Console as a domain property, and make sure you still own the old one.
Build the redirect map
One row per old URL with its new URL. Keep paths identical where you can, so old-domain/pricing becomes new-domain/pricing.
Launch the new site
Publish on the new domain with correct canonicals, sitemap and internal links that all use the new domain.
Switch on redirects
Make the old domain return 301s for every path, to the matching path on the new domain.
File the Change of Address
In the old domain's Search Console property, use the Change of Address tool to point Google to the new domain.
Monitor and fix
Re-crawl old URLs, watch both properties, and fix 404s and chains quickly.
The redirect map is the core asset. Our 301 redirect map template gives you the columns, and it's worth building even when paths stay the same, because it's the list you'll test against.
When should you use Google's Change of Address tool?
Use Google's Change of Address tool when your whole site moves from one domain to another, such as oldname.com to newname.com. It tells Google the move is intentional, which helps it transfer signals faster. It only works once the old domain's homepage already redirects with a 301.
Situation | Change of Address? | What to do instead |
|---|---|---|
Whole site, old domain to new domain | Yes | Use it, plus page-level 301s |
HTTP to HTTPS | No | 301s and an updated sitemap |
www to non-www | No | Pick one version and redirect the other |
Blog subdomain to subfolder | No | Page-level 301s from the subdomain |
Only some pages move to a new domain | No | Page-level 301s for those pages |
Platform change, same domain | No | Redirect map for changed paths |
Google documents the full process in its guide to site moves with URL changes, which is worth reading before you start. Moving a blog off a subdomain is a different job, and our subdomain to subfolder migration guide covers it.
Should you change domain and redesign at the same time?
Change domain and redesign at the same time only if the rebrand forces it, and keep URL paths and page content as close as you can. Every extra change adds a possible cause when you're trying to explain a drop.
Pros
- One launch, one announcement, one round of brand confusion
- Customers see the new name and the new site together
- No throwaway work on an old design with a new name
Cons
- If traffic drops, you can't tell which change caused it
- Copy rewrites can remove the words pages ranked for
- More URLs change, so the redirect map gets longer
- QA load grows with every extra change
If you do both, freeze the paths. Keep /pricing as /pricing and /blog/slug as /blog/slug on the new domain, so the redirect is a straight domain swap. Our guide on rebranding without losing SEO covers the brand side in more depth.
What else needs updating after a rebrand domain migration?
After a rebrand domain migration, update every place that points at the old domain, starting with the ones that send traffic. Redirects catch visitors, but direct links are faster and cleaner.
- Backlinks: ask the sites behind your strongest links to update them. Partners and directories usually will.
- Your own profiles: social bios, app store listings, marketplace and review profiles, Google Business Profile.
- Product and email: transactional email links, signatures, in-app links, docs and help center.
- Forms and tracking: form endpoints, analytics properties, ad final URLs and conversion tags. Our guide to migrating forms without losing leads covers the form side.
- Brand search: mention the old name on the new site, such as an about-page line that says the company was formerly known by it.
How long does a domain change take to settle?
A domain change takes longer to settle than a same-domain migration because Google has to recrawl and reprocess every URL. Expect rankings to move around for a while before they stabilize, and expect the old domain to keep showing in some results during that time.
Watch both Search Console properties weekly: impressions should fall on the old domain as they rise on the new one. If the new domain isn't picking up what the old one loses, re-check the redirects first. Our guide to traffic drops after a website migration gives the diagnosis order.
Hypothetical example: a seed-stage startup changing its name
For example, suppose a startup rebrands and moves from oldname.io to newname.com. The team keeps every path the same, so oldname.io/pricing becomes newname.com/pricing, and the redirect is one domain-level rule that preserves the path.
They launch the new site, switch the old domain to redirect, file the Change of Address in the oldname.io property, and email their top 20 linking sites. The about page names the old brand as the company's former name, so people searching the old name still find the right company. The old domain stays registered on auto-renew.
