You can change your domain without losing SEO long term, but only if you treat it as a redirect project and not a quick DNS change. Redirect every old URL with a permanent 301 to its exact match on the new domain, file a Change of Address in Google Search Console for every variant of the old domain, keep email working on both domains, and keep the redirects and the old domain for at least a year. Google says a medium-sized site can take a few weeks or more to settle, so a short ranking dip is normal. What you control is how deep it goes and how long it lasts.
I handle hosting and DNS migrations for clients, including moves across Hostinger and GoDaddy. When a domain move goes wrong, it's usually one of a few well-known gaps that Google's guidance warns about: redirects that all point to the home page, or a forgotten www variant. The other is email that quietly stops arriving.
Can you change your domain without losing SEO?
Yes, as long as the redirects are complete, though some short-term disruption is normal. Google's site move guide warns that rankings can move around while Google recrawls your site, and says 301 and other permanent redirects don't cause a loss in PageRank, so your link value carries over.
A Search Engine Journal study of 892 domain migrations found the new domain took 523 days on average to reach the old domain's estimated organic traffic. The fastest took 19 to 33 days, and 17% still hadn't recovered after 1,000 days. These are third-party traffic estimates, but the spread is the point: a careful move can recover in weeks, a careless one can drag on for years.
Google's guide also says to change one thing at a time. If you want a new domain, a new design and a new CMS, move the domain first and redesign later. Bundle them, see traffic drop, and you'll have no idea which change caused it. If a platform change comes next, read how to move from WordPress to Next.js without losing SEO.
How much does a domain migration cost in the US?
In the US, agencies typically charge from about $1,500 for a small site to $50,000 or more for a large e-commerce catalogue, mostly depending on URL count. These are US mid-market agency ranges for "SEO migration" work from Beta Tech's breakdown of SEO migration pricing:
| Site size | Typical price range | What is usually included |
|---|---|---|
| Small (under 100 URLs) | $1,500 to $3,500 | Audit, redirect map, staging review, post-launch check |
| Mid-size (100 to 1,000 URLs) | $3,500 to $8,000 | Full migration work plus 30 to 60 days of monitoring |
| Large (1,000 to 10,000 URLs) | $8,000 to $18,000 | Adds content audit, backlink mapping, 90-day monitoring |
| Enterprise or e-commerce (10,000+ URLs) | $18,000 to $50,000+ | Adds schema, international SEO, dedicated monitoring |
Beta Tech describes its small tier as a same-domain move, so a domain change on a small site can cost more. It puts senior technical SEOs at $100 to $250 an hour and says offshore teams typically charge 30 to 50% less. HigherVisibility gives a range of $3,000 to $15,000 for a website migration.
What is the safe order for a domain change?
Audit the old domain, build the redirect map, prepare the new domain, switch on the 301s, file the Change of Address, then monitor for at least three months.
- 1
Audit the old domain
Export every URL from the sitemap, a crawl and Search Console.
- 2
Build the redirect map
Map each old URL to its exact match on the new domain.
- 3
Prepare the new domain
Verify both domains in Search Console and copy DNS and email records.
- 4
Switch on the 301s
Turn on 301s and update canonicals, internal links and the sitemap.
- 5
File the Change of Address
Submit it from every verified variant of the old domain.
- 6
Update links and monitor
Update key links, then check indexing and traffic weekly for three months.
How do you build a 301 redirect map?
It's a spreadsheet: every old URL in one column, its exact replacement on the new domain in the other. Pull the old URLs from several sources, because each one misses something:
- Your XML sitemap and a full crawl of the live site.
- A Search Console Performance export of every page with clicks or impressions, which catches URLs you no longer link to.
- The Links report in Search Console for your most-linked pages.
- Images and PDFs, which Google says can already be getting search traffic and links.
If paths stay the same, one pattern rule can redirect old.com/anything to new.com/anything, and most of your time goes on the exceptions.
Google's site move guide sets the rules:
- Use server-side permanent redirects (301 or 308) wherever you can.
- Don't send lots of old URLs to the new home page. Google may treat that as a soft 404. Redirect merged pages to their replacement, and let deliberately dropped content return a 404 or 410.
- Avoid chains. Googlebot follows up to 10 redirects, but Google recommends keeping chains short (ideally no more than 3). Rewrite older redirects, like HTTP to HTTPS or old slugs, to point straight at the new domain.
I built the free Redirect Map Builder for this step. Paste in old URLs, or old and new pairs. It flags chains, loops, duplicates, trailing slashes, query strings and links to other domains, and gives you a redirects() array for next.config.js that goes straight into a Next.js site. On WordPress or Apache, use the cleaned old-to-new list to write your .htaccess or host redirect rules.
The variants that get missed most:
| Old address | Redirect to | Why it gets missed |
|---|---|---|
| http://old.com/page | https://new.com/page | Only the HTTPS version was tested |
| https://www.old.com/page | https://new.com/page | www is treated as a separate host |
| https://blog.old.com/post | https://new.com/blog/post | The subdomain runs on a different server |
| https://old.com/files/brochure.pdf | https://new.com/files/brochure.pdf | Files sit outside the CMS |
| https://old.com/page?ref=email | https://new.com/page?ref=email | Query strings get dropped |
Test a sample of each type with curl -I. You want a single 301 pointing straight at the final URL.
How do you use Search Console's Change of Address tool?
Google Search Console's Change of Address tool tells Google your whole domain has moved and asks it to prioritise crawling the new one. You submit it from the old property once your 301s are live. What it needs:
- At minimum, a 301 from the old home page to the new home page. Google also recommends redirecting the canonical pages.
- You have to own both the old and new properties, using the same Google account.
- It only works on domain-level properties like example.com, not paths like example.com/shop/.
- It doesn't move subdomains, and that includes www. Google's Change of Address help says to submit one for every variant of the old domain (www, non-www and any subdomains), even ones you don't use, with all of them verified.
- It covers every protocol of the source property, so http and https move together.
Once the critical pre-move checks pass, both properties show a 180-day notice that the move is in progress. You don't need the tool for HTTPS moves or www to non-www switches on the same domain.
Two small jobs while you're there: re-upload any disavow file on the new property, as Google recommends, and check your verification method works on the new domain. An HTML verification file has to be copied across.
How do you keep email working when the domain changes?
Copy every mail DNS record before you switch nameservers, keep the old domain's MX records live, and add the new domain as a secondary domain or alias.
Moving DNS hosting. If the move also takes your DNS to Cloudflare or a new registrar, copy every record first: MX, SPF, DKIM, DMARC, mail CNAMEs like autodiscover, and verification TXT records for Google Workspace, Microsoft 365 and Search Console. Lower the TTLs a day or two before. I cover this in how to move a WordPress site to a new host without downtime.
Old addresses. Customers and suppliers will keep emailing the old addresses for months, which is why the old MX records stay live. Set up SPF, DKIM and DMARC for the new domain before anyone sends from it, or those emails will land in spam. Check website forms and SMTP plugins too, as they often hard-code the old address as the sender.
Don't delete the old DNS zone
Your redirects and old email addresses both depend on the old domain's DNS. Delete the zone or let the domain lapse and both stop at once.
Which backlinks and settings should you update?
Start with your own site, then profiles you control, your top referring sites, ads and any tools that store the old domain, in this order:
- Your own site: internal links, canonicals, hreflang, structured data and the sitemap.
- Profiles you control: Google Business Profile, social accounts and directory listings.
- Your top referring sites: email the owners of the pages that send real traffic.
- Ads: update the final URLs so you aren't paying for a redirect on every click.
- Tools that store your domain: GA4 data streams, GTM triggers that match on hostname, HubSpot tracking, Stripe webhooks and redirect URLs, login callback URLs, and your cookie banner.
Don't forget security headers. A Content-Security-Policy that only allows the old domain will block scripts on the new one, so add the new domain to every directive that lists the old one, then confirm what the new domain sends with the free Security Headers Checker.
What should you check in the weeks after the switch?
You want indexed pages falling on the old property and rising on the new one, and Google says to watch traffic on both domains. I check in three stages:
- Day one: test redirects for every variant, run URL Inspection on key pages, submit the new sitemap, and remove any development-time robots.txt blocks or noindex tags. The free AI Crawler Checker reads your new robots.txt and lists the sitemaps it declares.
- Weeks one and two: the Page indexing report on the new property, new 404s and crawl stats.
- Weeks three to twelve: compare clicks page by page, old and new combined, and dig into any page that's dropped out.
If the new domain is still well below where you were after a few months, it's usually a redirect gap, canonicals still pointing at the old domain, or dropped pages. That's the kind of audit I do under technical SEO and Core Web Vitals.
How long should you keep the old domain and redirects?
Keep redirects for at least a year, as Google's site move guide advises (and consider keeping them forever), and keep renewing the old domain. The Change of Address help sets a 180-day minimum, after which Google treats the old site as unrelated, and recommends paying for the old domain for at least a year so nobody can buy it for malicious purposes. I'd renew it indefinitely; it's cheap next to someone else picking up your backlinks and your customers' emails.
What should you ask a developer before a domain change?
Ask these before anyone touches DNS:
- Will you map every indexed URL, and can I see the map?
- How will you test that every variant redirects in one hop?
- Which DNS and email records will you copy, and who checks mail on both domains?
- Will I own both Search Console properties, and will you file Change of Address for every variant?
- What will you monitor, and for how long?
- Is anything else changing at the same time? The answer should be no.
Planning a domain change? Run your URL list through the free Redirect Map Builder first. If you'd rather I handled the whole move, from redirects to DNS, email, Search Console and monitoring, see hosting migrations, DNS and maintenance or book a call.
