Yes, you can change domain without losing most SEO, provided you map every URL, implement permanent server-side redirects, verify both domains in Google Search Console and monitor indexing closely. The three non-negotiables are complete URL mapping with 301 or 308 redirects, correct use of Search Console’s Change of Address tool, and a rollback plan that keeps your old domain and hosting live until the new one proves stable.
TL;DR:
- Complete URL mapping and redirects are crucial to prevent ranking loss, especially for high-value pages attracting organic traffic and backlinks.
- Server-side 301 or 308 redirects must be tested thoroughly and kept active for at least several months to maximize relevance transfer.
- Verifying both domains and submitting the new sitemap in Search Console helps Google recognize the move and supports reindexing efforts.
- Avoid redirect chains and ensure internal links point directly to the new URLs to maintain crawl efficiency and relevance signals.
- Post-launch, continuously monitor indexing, crawl errors, and keyword positions for at least three months to catch issues and confirm successful migration.
Table of Contents
- Inventory and planning: export URLs and build your redirect map
- How to implement redirects without losing relevance
- Search Console tasks: verify, submit and use Change of Address
- Pre-launch testing and the exact sequence at DNS cutover
- What to monitor after launch and how to diagnose a drop
- Frequent migration mistakes and a safe rollback checklist
- How a domain change affects paid search campaigns
- Updating social media profiles and other digital assets
- Long-term SEO monitoring beyond the first few weeks
- Why experienced support matters for a domain move
- Get a free review before you move your domain
- Where to check the official guidance
- Sources
- FAQ
Inventory and planning: export URLs and build your redirect map
A domain change succeeds or fails before launch day. The planning stage is when most SEO value gets protected, or lost through a rushed spreadsheet.
Start by exporting every indexed URL on your current site, along with your top-performing landing pages from your analytics platform. These are the pages bringing in organic sessions and ranking for keywords worth defending, so they need priority treatment in your redirect map. Pull a backlink export too. You will need it later for outreach, and knowing which pages attract the most external links tells you where a mistake would hurt most.
Here is the sequence that keeps this stage manageable:
- Export a full URL list from your CMS, XML sitemap and crawl tool, then cross-reference against Google Analytics for traffic volume.
- Identify your highest-value pages by organic sessions and keyword rankings, and flag these for manual review rather than automated redirect matching.
- Build a redirect map pairing every old URL with its exact new equivalent, including subdomains, trailing slashes and protocol variants (http versus https, www versus non-www).
- Lower your DNS time-to-live (TTL) a week before launch so the cutover propagates faster.
- Confirm SSL certificates are active on the new domain and remove any staging-site noindex tags or robots.txt blocks before go-live.
- Take a full backup of the current site, database and DNS configuration.
Google’s own migration guidance stresses changing only one major variable at a time. Bundling a domain move with a redesign or a CMS switch makes it far harder to diagnose what caused a ranking dip, so resist the urge to relaunch everything at once. A website SEO audit checklist is a useful companion for this inventory stage if you want a structured starting point.
Pro Tip: Keep your redirect map in a shared spreadsheet with columns for old URL, new URL, priority and status, so nothing gets missed when multiple people are involved.
How to implement redirects without losing relevance
Server-side permanent redirects, specifically 301 or 308, are the correct tool for a domain change. Google’s documentation on redirects confirms that a 301 or 308 tells search engines a page has moved for good, which is exactly the signal you want to send when every URL on your site is shifting to a new address.
The single biggest mistake at this stage is the homepage catch-all, where every old URL redirects to the new homepage instead of its matching page. This breaks the relevance signal search engines rely on and tends to tank rankings for pages that would otherwise have transferred cleanly. Each old URL needs to point to its closest equivalent on the new domain.
- Implement redirects at server level using .htaccess rules on Apache, server blocks on Nginx, or your CDN’s redirect configuration, rather than relying on JavaScript or meta refresh redirects.
- Test every redirect with an HTTP status checker to confirm it returns a 301 or 308, not a 302 or a soft 404.
- Crawl the full redirect map with a tool such as Screaming Frog before launch to catch chains, where one redirect points to another redirect instead of the final destination.
- Update every internal link across your site, navigation, footer and content to point directly to the new URLs rather than relying on the redirect to carry the weight.
Keep redirects live for a minimum of several months, ideally up to a year if you have the hosting capacity, since Google notes that recrawling and reindexing a moved site takes time that scales with its size.
Pro Tip: Never redirect to a 302 “temporary” status out of convenience. It tells search engines the move might reverse, which slows signal transfer considerably.
Search Console tasks: verify, submit and use Change of Address
Search Console is where you formally tell Google the move is happening, and skipping or rushing this step undermines everything else you have done.
- Verify both your old and new domain properties in Google Search Console, including any subdomain variants such as www and non-www, since the Change of Address tool does not move subdomains automatically.
- Submit your new XML sitemap the moment the new domain goes live, so Google has a complete map of what to crawl.
- Use the URL Inspection tool on a sample of high-priority pages to check indexing status and confirm Google can see the new, canonical version.
- File the Change of Address request only after redirects are live and verified. The tool works at domain level only and runs pre-checks to confirm redirects are in place before it will proceed.
Once accepted, Change of Address prompts Google to prioritise crawling the new site and forwards signals for 180 days. That window is your main runway for recovery, so the redirect map needs to be solid before you file.
Pre-launch testing and the exact sequence at DNS cutover
Testing on staging catches the failures that would otherwise surface in production, where they are far more expensive to fix.
- Confirm every redirect on the staging environment resolves correctly, with no chains and no accidental 302s.
- Check that noindex tags used during staging have been removed from the live new domain.
- Verify canonical tags point to the new domain’s own URLs, not the old ones.
- Confirm structured data (schema markup) carries over correctly and validates without errors.
- Check the SSL certificate is valid and correctly configured for the new domain before cutover.
On launch day, flip DNS, then immediately spot-check a sample of redirects on the live new domain to confirm they behave as tested. Submit the new sitemap, run URL Inspection on your highest-priority pages, and watch server logs for crawl activity and error spikes in the following hours.
If a critical failure appears, such as redirects returning errors or the new domain failing to resolve, reverse DNS back to the old setup and re-enable old hosting immediately rather than trying to patch live. Keep the old hosting account active and ready for exactly this scenario.
Pro Tip: Run your launch during a low-traffic window and keep your team on standby for the first few hours, since early errors are far cheaper to fix than ones discovered days later.
What to monitor after launch and how to diagnose a drop
The weeks after a domain change are about watching the right signals and resisting panic over normal fluctuation.
- Check Index Coverage reports in Search Console daily for the first fortnight to track how many new URLs are indexed versus excluded.
- Run URL Inspection on key pages periodically to confirm Google has processed the move for each one individually.
- Review crawl errors and server logs to catch redirect failures or unexpected 404s early.
- Track organic sessions and core keyword positions against your pre-move baseline, not against a single day’s snapshot.
Google does not promise instant recovery from a domain move, and processing speed depends partly on your site’s URL volume and server response time. Most URLs on small to medium sites get recrawled within days to a few weeks, but full signal transfer across a larger site with a complex backlink profile can take longer.
If traffic drops beyond normal fluctuation, work through a fixed triage order: confirm every redirect still returns the correct status, check canonical tags haven’t reverted, verify robots.txt isn’t blocking the new domain, and review whether your highest-value backlinks still point somewhere useful. Redirects help Google associate old and new URLs, but they do not update the links themselves, so reaching out to your most important referring sites to ask for a direct link update is still worthwhile. A practical migration checklist from Semrush covers this backlink outreach step in more detail. For ongoing tracking once the dust settles, a guide to monitoring SEO performance is a useful reference point.
Frequent migration mistakes and a safe rollback checklist
Most domain migrations that go wrong fail for the same handful of reasons, and most of them are avoidable with the checklist above followed properly.
- Redirect chains, where an old URL passes through two or three redirects before reaching its destination, slow crawling and dilute signal strength.
- Using 302 redirects instead of 301 or 308, which tells search engines the move might not be permanent.
- Forgetting a www or non-www variant, or a subdomain, leaving a chunk of the old site unredirected.
- An expired SSL certificate or a leftover noindex tag from staging, both of which can quietly block indexing on the new domain.
Watch closely in the first 48 to 72 hours. Spikes in crawl errors, a sudden drop in indexed pages, or redirects returning unexpected status codes are early warning signs that need same-day correction, not a wait-and-see approach.
If rollback becomes necessary, reinstate the old DNS records and old hosting, add temporary redirects from the new domain back to the old one if any traffic has already shifted, and cancel the Change of Address request in Search Console to avoid sending conflicting signals.
How a domain change affects paid search campaigns
A domain change does not pause automatically for your paid campaigns, so Google Ads and other platforms need their own checklist running in parallel with the SEO work.
Update every final URL in active campaigns to point to the new domain before or immediately at cutover, since paid landing pages redirecting through an SEO redirect chain can trigger landing page quality warnings and hurt Quality Score. Check that conversion tracking, including any tags or pixels embedded in landing page code, has been migrated and is firing correctly on the new domain before you let campaigns resume at full spend.
Domain-level verification in Google Ads, where required for certain ad formats, needs updating too. If your account uses domain-level sitelinks or location extensions tied to the old domain, review and reassign these rather than assuming they carry over.
Run paid campaigns at reduced budget for the first few days after launch while you confirm landing pages, tracking and Quality Scores are behaving normally on the new domain. A PPC budget planning guide is a useful reference if you need to recalculate spend around this transition period, and a look at PPC landing page practice is worth revisiting once your new domain’s pages are live, since migration is a natural moment to tidy up pages that were never quite converting well.
Updating social media profiles and other digital assets
Your website is rarely the only place your old domain lives. Social profiles, email signatures, business directories and third-party listings all need updating, and missed ones quietly leak traffic and trust for months.
Update the website link on every social media profile, bio and pinned post, since these are often a steady source of direct and referral traffic that a redirect will catch but a direct link avoids friction entirely. Check Google Business Profile and any other local or industry directory listings, as these frequently carry the old domain and are easy to overlook once the website itself is live.
Review email signatures, invoicing software, printed materials still in circulation and any QR codes pointing to the old domain. A practical guide to social media management covers the broader upkeep of these profiles if you want a fuller checklist beyond the domain-specific updates. Finally, check third-party integrations, booking widgets, payment processors and analytics tools for hardcoded references to the old domain, since these can silently break rather than redirect.
Long-term SEO monitoring beyond the first few weeks
The first fortnight gets most of the attention, but the signals that confirm a migration truly succeeded take longer to settle. Treat the following weeks and months as a distinct monitoring phase, not an afterthought.
Continue tracking organic sessions and keyword positions monthly against your pre-move baseline for at least two to three months, since full signal transfer on larger sites with complex backlink profiles takes longer than the initial Change of Address window suggests. Watch for any late-appearing crawl errors, particularly on deeper pages that take longer to get recrawled than your homepage or top landing pages.
Keep an eye on your backlink profile over time, not just immediately after launch, since outreach to update links is often a slow trickle rather than a one-off task. Revisit your redirect map every few months during this period to confirm nothing has broken due to CMS updates, plugin changes or server configuration drift. A guide to monitoring SEO performance is worth bookmarking for this ongoing phase, and pairing it with a broader SEO best practices review once the migration has settled helps confirm the new domain is performing at least as well as the old one across the board, not just on the metrics you checked in week one.
Why experienced support matters for a domain move
Doing this yourself is entirely possible for a small site with a modest number of URLs and a team comfortable with DNS, server configuration and Search Console. The calculation changes once you are dealing with hundreds of URLs, a complex backlink profile, active paid campaigns or simply no spare capacity to watch server logs for a fortnight.
An experienced digital marketing agency treats a domain migration as a planning exercise first and a technical task second: building the redirect map, testing it thoroughly, coordinating the DNS cutover, and watching indexing and traffic for the weeks that follow rather than disappearing after launch day. That combination of planning, attention to detail and follow-through is what prevents the common mistakes covered above from happening in the first place.
A typical engagement covers the full inventory, the redirect map itself, pre-launch testing, DNS coordination on launch day, and remediation support if anything needs correcting once the new domain is live.
— tibor
Get a free review before you move your domain
If you would rather hand the technical risk to someone else, Some digital marketing agencies offer free website and SEO reviews that work well as a first step before any domain change, giving you a clear picture of your current rankings, your highest-value pages and what a redirect map for your site would actually need to cover. The practical first deliverable is a migration audit: a prioritised redirect map alongside a risk assessment flagging which pages, backlinks and paid campaigns need the most careful handling.
From there, you can request a migration quote covering planning, redirect implementation, DNS coordination and post-launch monitoring, or explore the full SEO services on offer if your domain change is part of a broader site refresh. Get in touch through Fylde Digital to book your free review and find out what a properly planned migration would look like for your business.
Where to check the official guidance
For implementation detail beyond this checklist, see Google’s site move documentation, recrawl guidance, and a deeper technical SEO audit checklist.
Sources
- Site moves and migrations | Google Search Central
- Move your site from one domain to another — Change of Address
- Changing your domain name (Semrush)
FAQ
Does changing a website’s domain affect SEO?
Yes, a domain change affects SEO because search engines need to recrawl and reindex every URL under the new address. The impact can be minimal if you implement permanent redirects, verify both domains in Search Console and use the Change of Address tool correctly, but some temporary fluctuation is normal while reindexing completes.
What does “domain change” mean in an SEO context?
A domain change means moving a website from one domain name to another, such as switching from an old company name to a new one, while keeping the content and URL structure broadly the same. It is treated as a formal “site move” by search engines, which requires redirects and explicit signals to transfer ranking value to the new address.
Is domain flipping illegal?
Domain flipping, buying and reselling domain names for profit, is a legal practice in most markets and is unrelated to the domain change process covered here. It only becomes a legal issue when it involves trademark infringement or deliberately misleading buyers, which falls outside standard SEO migration practice.
Is SEO dead now that AI is more widely used in search?
No, SEO is not dead. Search engines still rely on crawling, indexing and ranking signals such as redirects, canonical tags and backlinks, all of which remain directly relevant to how a domain change is handled and how quickly rankings recover.
How long should I keep redirects live after a domain change?
Keep permanent redirects live for a minimum of several months, and ideally up to a year if your hosting allows it, since Google’s guidance notes that reindexing a moved site takes time that scales with its size. Removing redirects too early can strand any traffic or crawlers still arriving via the old URLs.
