Insights — Technical SEO
How It Is Possible To Change Your Domain Without Losing Your SEO Juice
Changing your domain is one of the few decisions that can undo years of SEO work in a single afternoon — or cost you almost nothing, depending entirely on how carefully it's executed.
The gap between those two outcomes isn't luck. Industry analysis suggests roughly 60% of migrations result in measurable organic traffic loss, and one study of nearly 900 migrations put the average time to regain pre-migration traffic at well over a year. Meanwhile, a well-executed move typically stabilises within a few weeks.
Almost every difference between those two scenarios comes down to the same handful of technical decisions — mainly URL mapping and redirect logic. Here's how to get them right.
What "Normal" Looks Like After a Migration
Knowing the difference between expected volatility and a real problem prevents both panic and complacency in the weeks after launch.
| Signal | What It Means |
|---|---|
| 10–30% traffic dip, recovering in 2–6 weeks | Normal migration volatility |
| Ranking stabilisation in 4–12 weeks | Expected, depending on site scale |
| 50%+ drop with no recovery after 4 weeks | Red flag — investigate immediately |
| Immediate, total traffic loss at launch | Check robots.txt and noindex tags first |
"A domain migration isn't a launch event. It's a 90-day project where the launch happens somewhere in the middle."
— Saurabh Mishra, KKJ Advisory
Export a Complete Baseline Before You Touch Anything
You cannot diagnose a problem after launch if you have no record of what "healthy" looked like before it. This is the step teams skip most often, and regret most later.
What to capture
- A full crawl of the existing site, listing every indexed URL.
- Google Search Console performance data — queries, impressions, clicks, and average positions — for a fixed 30-day window.
- GA4 traffic and conversion data for the same window.
- Your current backlink profile, with the highest-authority referring domains flagged separately.
Why it matters: Every post-launch decision — is this dip normal, did this page lose rankings, which links still need updating — depends on having this baseline to compare against.
Map Every Single URL to a Topically Equivalent New One
This is the decision that determines the outcome of your migration more than any other. Every indexed URL on the old domain needs a mapped destination on the new one — not a generic redirect to the homepage.
Mapping rules that matter
- Map each old URL to its closest topical equivalent, not to the homepage. Bulk homepage redirects are treated as soft 404s and waste the equity you're trying to preserve.
- Keep the mapping in a spreadsheet so it can be tested, reviewed, and audited after launch.
- Where no equivalent exists, decide deliberately: redirect to the nearest relevant page, or return a 410 for genuinely retired content.
Why it matters: A URL that isn't mapped is a URL whose accumulated authority simply disappears at launch.
Use 301 Redirects — and Confirm Nobody Substituted a 302
Every mapped URL needs a permanent 301 (or 308) redirect. Using a 302 instead is among the most common technical mistakes in migrations, because a 302 signals a temporary move and doesn't consolidate ranking signals the same way.
What to check before DNS cutover
- Every redirect returns a 301 status, verified with a redirect checker or curl — not assumed.
- No JavaScript-based redirects standing in for server-level ones.
- No redirect chains: flatten any URL that hops through two or three intermediate stops into a single direct redirect.
- No redirect loops.
Why it matters: Chains and 302s both leak link equity and slow crawling, turning what should be a clean signal transfer into a partial one.
Clear the Launch-Day Technical Checklist Before Flipping DNS
Most catastrophic migration failures aren't subtle SEO problems — they're a staging setting that made it to production.
The non-negotiables
- Remove staging noindex tags and password protection.
- Verify robots.txt on the live site allows crawling — no leftover Disallow: /.
- Confirm canonical tags on every template point to the new live URLs, not the old domain.
- Lower DNS TTL to around 300 seconds at least 24–48 hours in advance.
- Check CSS and JavaScript assets load correctly from the new domain or CDN.
Why it matters: If traffic drops to nearly zero immediately after launch, a stray noindex tag or a blocked robots.txt is almost always the cause — and it's trivially fixable if you catch it in hours rather than weeks.
File the Change of Address Request — After Redirects Are Live
Google Search Console's Change of Address tool tells Google to prioritise crawling the new domain and forward ranking signals accordingly. It applies to domain-level moves specifically — not to HTTPS-only migrations or URL restructuring on the same domain, which is the most commonly confused distinction in this whole process.
Sequence matters: Submitting the request before your 301s are live is a frequent cause of significant ranking loss. The tool runs pre-move checks and expects to find working redirects from the old domain. Redirects first, then the request.
Also submit your updated XML sitemap to both Google Search Console and Bing Webmaster Tools on launch day.
Update Internal Links to Point Directly at New URLs
Redirects are a safety net for external traffic, not a permanent substitute for correct internal linking. Leaving your own site's internal links pointing at old URLs that then redirect is a documented cause of avoidable ranking loss.
What to update: Navigation menus, in-content links, canonical tags, structured data, hreflang references if applicable, and any hardcoded URLs in templates or theme files.
Then work outward: Reach out to the highest-authority sites still linking to your old domain and ask them to update. The redirect will pass most of the value, but a direct link is always cleaner.
Don't Forget AI Search Visibility
This is the step most older migration checklists still miss. In 2026, a botched migration can quietly remove your brand from AI-generated answers on ChatGPT, Perplexity, and Google's AI Overviews just as quickly as it drops your traditional rankings.
What to include
- Confirm AI crawler permissions in robots.txt reflect your intended policy on the new domain.
- Migrate structured data and schema markup completely, not partially.
- Spot-check whether AI engines still cite your brand correctly in the weeks after launch, since language models associate entities with specific addresses and a domain change can break existing citation patterns.
Monitor Daily for Two Weeks, Then Keep Watching for 90 Days
The migration isn't finished when the site goes live. Problems tend to surface — and compound — in the weeks that follow.
What to watch
- Index coverage in Search Console: which new URLs have been indexed, and which haven't.
- Crawl errors, anomalies, and any manual actions.
- Organic sessions compared against your pre-migration 30-day baseline.
- Whether old and new URLs are both being served, which splits signals through duplicate content.
- That conversion points — forms, checkout, tracking tags — actually fire on the live site.
Cadence: Daily for the first two weeks, weekly through the first month, then every two weeks through the 90-day window.
The Three Phases, Simplified
If the checklist above feels long, the underlying structure is straightforward — and keeping these three phases distinct is what separates a controlled migration from a chaotic one.
Audit the existing site, export your full performance baseline, and map every URL to its new equivalent.
Activate and test 301s, clear the technical checklist, flip DNS, then file the Change of Address request and submit sitemaps.
Monitor indexing, rankings, and conversions against baseline, fix issues fast, and keep redirects live for at least 12 months.
Frequently Asked Questions
Keep 301 redirects live for at least 12 months, and ideally longer. Also keep ownership of the old domain rather than letting it lapse — otherwise you lose any remaining redirect equity and someone else can register it and redirect your former traffic elsewhere.
No. Bulk redirects to the homepage are typically treated as soft 404s, which means the accumulated authority of those individual pages doesn't transfer. Each URL needs a topically equivalent destination for the signals to carry over properly.
No. The Change of Address tool applies specifically to domain-level moves. HTTPS-only migrations and URL restructuring within the same domain don't use it — they rely on 301 redirects and updated canonicals alone. This distinction trips up a lot of teams.
A dip of roughly 10–30% that stabilises within two to six weeks is normal. A drop of 50% or more with no sign of recovery after four weeks indicates a real technical problem — most commonly missing redirects, a stray noindex tag, or canonicals still pointing at the old domain.
Incomplete or incorrectly configured 301 redirects. Close behind: submitting the Change of Address request before redirects are live, leaving internal links pointing at old URLs, and simply not monitoring Search Console in the weeks after launch.
Ideally not. Changing the domain and restructuring URLs simultaneously doubles the variables and makes diagnosing any post-launch problem considerably harder. If both are needed, sequence them as separate projects with a stable period in between.
Check robots.txt and noindex tags first, then test redirects for loops or missing entries. If errors are catastrophic and can't be resolved within a few hours, execute a rollback — which is why having a documented rollback plan before launch is part of the preparation, not an afterthought.
Planning a Domain Move? Get It Right the First Time
At KKJ Advisory, we help businesses plan and execute site migrations that protect hard-earned search visibility instead of resetting it.
Book a Strategy Call