.jpg)
A B2B SaaS rebrand can change your name, positioning, and the way in which customers are able to understand your company. When it also changes your domain, it can change something less visible: how search engines understand you.
That makes the website migration more than a launch task. Rankings can fluctuate, links can break and parts of your old brand can remain scattered across the web long after the new one goes live.
The goal here is to know what can break, sequence the move properly, and measure what happens next.
A Rebrand is Not a Redesign
Rebrands and redesigns often arrive together, which makes them easier to treat as the same project, but they aren’t. The distinction is important because only one inherently changes the identity and location that search engines will associate with your business.
Only One of These Forces a Domain Move
A redesign changes the way your website looks and works. A rebrand can change what the company is called, where it lives online, and what it claims to be.
That difference is where the migration risk begins.
You can complete the redesign process without having to change domains. A rename that moves oldbrand.com to newbrand.com means every indexed URL potentially requires a new home.
For the growth-stage B2B SaaS companies, we often see the trigger when the product has outgrown the brand. Somewhere around $15-50 million ARR, a company can find that its original identity might no longer reflect the market that the company serves or the customers it sells to. That range is our agency observation rather than an industry benchmark.
At this point, the website is a much larger commercial decision. Understanding what a website costs means you need to account for migration as well as the new brand, and build as opposed to adding this as a pre-launch SEO task.
Change One Thing at a Time
Google recommends changing one thing at a time during a site move.
A rebrand already gives search engines a new domain to process. Combine that with a CMS migration, redesign and new URL taxonomy, and any subsequent traffic loss has several plausible causes.
If the rebrand has a fixed launch date, move the domain first while preserving as much of the existing site structure as possible, and redesign afterwards.
This recommendation can be an unpopular move when the brand team wants one dramatic launch. But separating the changes makes it considerably easier to understand what happened if rankings fluctuate.
There will still be opportunities to apply current enterprise website design thinking. The important thing is not making search engines process every major change simultaneously.
What the Evidence Says About Recovery
How long does a domain migration take to recover? The evidence gives a less reassuring answer than most migration guides: there’s no reliable single number.
The Independent Number
A January 2025 Search Engine Journal study by Dan Taylor examined 892 domain migrations and found an average of 523 days to reach the old domain’s estimated organic traffic. The fastest recovered in 19 to 33 days, while 17% had still not recovered after 1,000 days.
Those numbers need context. The dataset was crowd-sourced, traffic was estimated using Ahrefs as opposed to Search Console, and Taylor is an agency founder, a potential bias that he himself acknowledges.
An earlier 2023 study of 171 migrations found something different: an average 229 day recovery, with 42% never recovering.
Google offers a considerably shorter timeframe. Its documentation says ranking fluctuations are normal and that medium-sized sites can take a few weeks or more for new URLs to replace old ones, with larger sites taking longer.
This leaves an uncomfortable gap between a few weeks and an average of 523 days. The evidence doesn’t justify collapsing that into one reassuring recovery estimate.
Two Cases With Real Numbers
Individual migrations show just how wide that range can be.
When TransferWise became Wise and moved from transferwise.com to wise.com in February 2021, Robert Brandl’s Ahrefs analysis showed visibility recovering in around three months. Extensive launch coverage also generated links to the new domain, making PR part of the migration instead of something that happens afterwards.
Tooltester’s September 2021 migration followed a similar timeframe but a rougher path. Visibility dropped more than 30%, bottomed out after roughly five to six weeks and exceeded its previous level around three months later. A Google update occurred during the same period, however, making cause and effect difficult to isolate.
LiveChat demonstrates a different issue. The app stayed on the old domain during the move, which allowed that domain to continue ranking. That was a sequencing problem rather than evidence of a normal recovery curve.
And Facebook-to-Meta and Square-to-Block should not be used as comparisons. Neither moved its primary product domain, despite appearing as domain migration examples.
The Mechanics That Are Not Optional
A rebrand might be a business decision, but several technical requirements are non-negotiable once the domain changes. If you get these wrong, search engines will struggle to connect the old brand with the new one.
Redirects and Change of Address
Every old URL needs to have a 301 or 308 redirect that points one-to-one to its equivalent page on the new domain. Google states that permanent redirects don’t cause a loss in PageRank.
What you should not do is redirect large volumes of old URLs to the new homepage. Google might treat irrelevant redirects as soft 404s, while the pages lose the topical relationship that a direct replacement preserves.
Google’s Change of Address tool provides another signal that the move is permanent. It works well alongside redirects rather than replacing them, and doesn’t guarantee preserved rankings or prevent fluctuations.
Google updated its guidance on June 17, 2026 to require Change of Address submissions for all relevant subdomain variants, including www and non-www, with each property verified separately in Search Console.
For the implementation detail, we’ve covered the technical migration risks, site migrations, and enterprise migration separately. The rebrand question is whether those mechanics are ready before the new identity goes live.
The Old Domain and the Things Google Also Knows
Keep the old domain live and redirecting for at least 12 months. Longer is safer. Allowing it to expire risks handing an established domain, and the links still pointing towards it, to somebody else. Then update the signals outside of the redirect map.
Change the company name and domain in your Google Business Profile. Rewrite internal links so pages point directly to the new domain rather than repeatedly passing through redirects. Check for broken links where an old URL has been mapped to a destination that no longer exists.
Individually, these might seem to be small details, but together they help to remove conflicting signals between the old and new identities.
For larger B2B SaaS companies, this is also where experienced enterprise Webflow delivery helps coordinate migration instead of treating redirects, search visibility and the new website as separate launch tasks.
Everything Else That Breaks
Clean domain migrations don’t necessarily signify the end of your rebrand. Your company name and old URLs can exist across multiple systems outside of the website, and many of them don’t have an owner to take charge of updates.
The List Beyond Email
One of the leading guides comes from dchost, which covers email, an area many migration articles overlook.
This guidance addresses sending reputation, SPF, DKIM and DMARC, DNS records, TTL and cutover timing, and keeping the old email domain monitored. Instead of duplicating that work, utilize the guide for email and DNS migrations.
Everything surrounding the website tends to get less coverage. Your old brand can remain attached to review profiles, marketplace listings, social accounts and app stores. Old URLS can be hardcoded into the product, documentation, and campaigns. Some links might exist inside PDFs or partner assets that your team can’t change.
None of these alone will negatively impact your rebrand. Together they will create a messy second week following your launch, when customers may potentially encounter pieces of your old identity.
This happens because the SEO migration typically has a project owner, checklist and launch date. These smaller dependencies often don’t.
SEO work has an owner and deadline. These typically don’t, and this is why customers find them before the team does.
Sequencing and Measurement
Two things have to exist before launch day.
First, you need to finish and test the redirect map before your new structure gets locked in. URL decisions made for branding reasons can wind up making clean one-to-one mapping impossible.
Second, it’s important to establish analytics continuity. Robert Brandl notes that GA4 wasn’t configured before one migration he documented, eliminating a reliable before-and-after comparison. If measurement changes after launch, you can’t determine what the migration has changed with any degree of confidence.
Finally, make sure you assign ownership. Rebranding resets responsibilities across marketing, product, and engineering. Without clear website governance, these decisions become fragmented and the new site begins accumulating the same problems the rebrand was meant to leave behind.
The redirects are the part everyone plans for.
The SEO work on a rebrand has an owner, a checklist and a date. Everything else does not: the review profiles, the marketplace listings, the app store entry, the links buried in a PDF a partner published two years ago. Those get discovered by customers in week two, which is what makes a rebrand feel chaotic even when the migration itself went cleanly. We build B2B SaaS websites, and on a rename the useful part of that work is usually the list of things nobody assigned to anyone.
FAQs
How long does it take to recover traffic after a domain change?
The honest answer is a range. Google says expect a few weeks or more for medium sites. The largest independent study, covering 892 migrations, found an average of 523 days and 17 percent never fully recovering. Wise and Tooltester both recovered in roughly three months.
Will we lose rankings if we change domains?
Expect temporary fluctuation. Google states that 301 and other permanent redirects do not cause a loss in PageRank, so a clean migration is recoverable. What is not recoverable is redirecting many old URLs to the homepage, which Google may treat as soft 404s.
What does the Change of Address tool actually do?
It signals a permanent move and helps Google transfer signals faster alongside your redirects. It does not preserve rankings, does not replace redirects, and does not prevent fluctuation. Since June 2026 Google asks you to submit it for all subdomain variants including www and non-www.
How long should we keep the old domain?
At least twelve months of live redirects, and longer is safer. Letting it expire donates whatever authority it accumulated to whoever registers it next, and there will still be links in PDFs, decks and partner pages that nobody can edit.
Should we redesign the site at the same time?
Google's own guidance is to change one thing at a time. Combining a domain move with a redesign, a CMS change and a new taxonomy means every lost page has several plausible causes and none can be isolated. Move the domain cleanly first.
What breaks besides SEO and email?
G2 and Capterra profiles, marketplace and integration listings, app store entries, social handles, your Google Business Profile, documentation links, hardcoded in-product URLs and every live campaign destination. None of it is on the website, which is why none of it is on the website checklist.
Did Facebook to Meta hurt their SEO?
It was not a domain migration. Facebook.com stayed exactly where it was and meta.com is a separate corporate site. The same is true of Square to Block. Several articles use both as migration case studies, which is why comparisons drawn from them do not hold.
