Change Your Domain Without Tanking Your SEO
Right, so you’re finally pulling the trigger on the rebrand. New name, new domain, fresh start — I get it. But before you point that domain and call it done, I want to walk you through exactly what I do for clients when this comes up, because the difference between doing this properly and doing it carelessly is usually about six months of rankings you’ll never get back.
I’ve been handling these migrations since 2009. The horror stories I could tell you. One client came to me after their developer “just changed the URL” in WordPress settings, deleted the old domain, and wondered why their traffic fell off a cliff within two weeks. No redirects. No Search Console update. Nothing. We spent three months clawing back what was lost.
Don’t be that client.
What’s Actually at Stake When You Change Your Domain
Here’s the thing — Google doesn’t automatically know your old domain and your new one are the same website. From its perspective, the old domain could be going dark and some new site just appeared. Every backlink pointing to your old URLs, every indexed page, every bit of authority you’ve built up — all of that is attached to the old domain. Without a proper domain migration SEO strategy in place, you’re essentially starting from scratch in Google’s eyes.
That doesn’t mean you’ll lose everything. Done right, most of that equity transfers. I’d say a well-executed migration typically sees a dip of maybe 10–20% in organic traffic for four to eight weeks, then a recovery. A poorly executed one? I’ve seen sites drop 70% and stay there.
The other thing people underestimate is time. DNS propagation, Google’s recrawl schedule, backlink updates — none of this happens overnight. Plan for a full three months before you can call the migration truly settled.
The Technical Steps — In the Order They Actually Matter
Step 1: Set up the new domain first, completely
Before you touch anything on the old domain, get the new one fully live. Same content, same structure, same URLs — just swap the domain. If you’re running WordPress, this means updating your WordPress site URL change in two places: Settings → General, and often the database itself, because WordPress bakes the domain into every internal link it stores.
I use WP-CLI for this on most jobs because it’s clean and fast:
wp search-replace 'https://olddomain.com' 'https://newdomain.com' --all-tablesRun that on a staging copy first. Always. I’ve seen that command cause mayhem when run directly on production without a fresh database backup sitting right there.
Step 2: 301 redirects — every single URL
This is the non-negotiable part. 301 redirects for a domain change tell both users and search engines that the move is permanent, and they pass the vast majority of link equity from the old URL to the new one. You want a redirect for every page that has ever been indexed or linked to — not just the homepage.
The cleanest way to do this on Apache hosting is via .htaccess on the old domain:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?olddomain\.com$ [NC]
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]That single rule handles the whole domain, preserving the URL path so /services/ on the old domain redirects to /services/ on the new one. Google appreciates that. Random redirects to your homepage are lazy and you’ll lose ranking signals on every inner page.
If you’re on a host that doesn’t give you .htaccess access — and some managed hosts don’t — a plugin like Redirection can do this, though I prefer server-level rules wherever possible. They’re faster and don’t depend on WordPress loading.
Step 3: Google Search Console — the Change of Address tool
Most tutorials mention this. Few explain that it only works if you’ve already verified both properties in Search Console. So do that first — verify the old domain and the new domain as separate properties. Then, inside the old domain’s property, go to Settings and you’ll find the Search Console change of address option right there.
Submit it. Google will use this as an explicit signal that this is an intentional rebrand website domain move, not a hack or an error. It doesn’t replace your 301s — it works alongside them. Think of it as raising your hand and telling Google directly, rather than waiting for the crawler to figure it out.
Keep both Search Console properties active for at least six months after the migration. You’ll want to monitor the old one for crawl errors, and the new one for how quickly indexing is picking up.
My Honest Take on Timing and Expectations
I’ll be direct with you: there is no such thing as a zero-impact domain migration. Anyone who promises you your rankings won’t move at all is either lying or has never actually done one of these at scale. What you’re aiming for is a managed, temporary dip rather than a freefall — and the difference is almost entirely in your preparation.
My rule is to never launch a rebrand website domain change during your busiest business season. A retailer in October, an accountant in January — wait until things are quieter. You want headroom to troubleshoot without your phone ringing off the hook.
Submit an updated sitemap for the new domain in Search Console the same day you go live. Update your Google Business Profile if you have one. Reach out personally to two or three of your highest-authority backlink sources and ask them to update their links — most will, and a live link is always better than a redirected one, even a 301.
I did a migration last year for a B2B client moving from a hyphenated domain they’d had since 2011 to a cleaner brand name. Eleven years of history on that old domain. We did every step I’ve described here, and within ten weeks their new domain was outranking the old one had ever managed. The redirects held, Search Console processed the change of address within about three weeks, and their main keywords barely flinched. That’s what a clean migration looks like.
If you’re also moving hosts at the same time — which some people do during a rebrand — I’d strongly suggest reading Move WordPress to a New Host Without Losing a Thing before you start. Combining a host move and a domain change in one go multiplies the variables, and you want to know exactly which lever to pull if something goes wrong.
One more thing. Keep the old domain registered and the redirects live for a minimum of two years. Domains are cheap. The cost of losing those redirects early is not.
After the Migration: What to Watch
Check your redirect chains. It’s very easy to end up with a situation where your old domain redirects to the new domain, but the new domain then has its own internal redirects, creating chains that slow everything down. Screaming Frog is my go-to for auditing this — run it on the new domain after launch and look for any URLs returning a 3xx instead of a clean 200.
Watch your Core Web Vitals in Search Console for the new property. Sometimes a migration exposes performance issues that were always there but never noticed. If you want a deeper look at how hosting choice affects performance, Shared vs VPS vs Managed WordPress Hosting: The Honest Answer is worth your time.
And watch your email. If your old domain had email addresses on it, you need MX records and forwarders sorted before you let that domain go quiet. I’ve saved more than one client from a mail blackout by catching this the day before launch. It’s the kind of thing that feels obvious in hindsight and catastrophic when missed.
What Most Guides Get Wrong About Domain Migration SEO
I’ve seen teams obsess over 301 redirects and then completely forget to update their canonical tags — and that’s exactly where domain migration SEO falls apart quietly, weeks after launch when rankings start sliding and nobody connects the dots. When I moved a Wilmington e-commerce client from an aging shared host to Google Cloud, I ran a full crawl in Screaming Frog before touching a single DNS record, just to map every canonical, every hreflang, every hardcoded internal link. That pre-migration snapshot saved us three hours of guesswork post-cutover. Don’t skip it — your redirects mean nothing if your canonicals are still pointing at the old domain.
If you’d like someone to handle this end-to-end — migrations, redirects, Search Console setup, the lot — I take on this kind of work regularly at swsDreams. Happy to take a look at your specific situation.
