Post-Acquisition Brand & Domain Migration Without Losing Rankings (2026)

Here's the week-by-week plan we run for post-acquisition rebrands and domain consolidations, with the healthcare-specific traps called out.

First decision: do you even migrate now?

Rebrand pressure after an acquisition is real, but domain equity is an asset on the books like any other. Three legitimate options:

Migrate now — right when the brand change is announced anyway and the target site is healthy.
Migrate later — stabilize first (tracking, forms, booking — see Standardizing HIPAA-Compliant Marketing Across an Acquired Portfolio), migrate in a planned window. Usually correct.
Don't migrate — multi-brand groups keeping local names should keep local domains; local links and citations are ranking assets you can't transfer at par.

Never combine a domain migration with a site redesign or platform change in the same window. If rankings drop, you need to know which change did it. One variable at a time.

Weeks 1–2: Crawl, benchmark, audit

You cannot preserve what you haven't inventoried.

Full crawl of the old site. Every URL, status code, title, and internal link. This crawl is your redirect map's left-hand column.
Traffic and ranking benchmark. Export 12 months of Search Console queries and pages, top landing pages by organic sessions, and current rankings for money terms ("implants + city", "therapist + city", provider names). This is the baseline you'll defend.
Backlink inventory. Which pages hold the links? Those URLs get first-class redirects, no exceptions.
Compliance audit of the legacy stack. Trackers on every page, form destinations, plugins, admin accounts. Fix the URMC-class exposures now — don't 301 patients into a page that still leaks their data. (Self-audit: Does Your Practice Website Leak PHI?.)
Take a verified backup. Full site and database to cloud storage, restore-tested. The rollback plan is not "we'll figure it out."

Healthcare-specific inventory: provider bio pages (often the highest-converting organic pages a practice has), location pages, and patient galleries. Galleries must remain noindexed through and after the move — a migration that accidentally exposes before/after photos to indexing is a privacy incident, not an SEO bug (rules: Before & After Photos and HIPAA).

Weeks 3–4: Map and stage

Build the 301 map — one-to-one, page to page. The rules:

Old URL type	Redirect target	Never
Service page	Equivalent service page on new domain	The homepage
Provider bio	Same provider's new bio	A generic team page (unless the provider left)
Location page	Same location's new page	The locations index
Blog post	Same post at new URL	A category page
Linked-to page (any)	Closest true equivalent	404, ever
Genuinely retired content	Closest topical parent	Homepage blanket redirect

Blanket everything-to-homepage redirects are treated as soft 404s and forfeit the equity you're trying to move. Budget real hours here — the map is 60% of the migration.

Stage the new site — sealed. Staging must be unindexable and access-controlled. Staging sites get indexed constantly (we monitor for exactly this across our fleet), and an indexed staging clone splits your content with itself right before the move. Verify noindex/auth from an external request, not from the admin panel.
Carry over the compliant stack, don't rebuild it ad hoc: server-to-server forms, first-party tracking, hardened WordPress config (fail-closed 2FA, malware scanning, backups — the architecture in How We Build HIPAA-Compliant WordPress Sites). One structural advantage worth noting: because our booking runs iframed off the website and intake never touches the WP database, a domain swap doesn't touch the booking pipeline — patients booked mid-migration land in the EHR like any other day.
Pre-write the update list for everything outside the website: GBP website fields for every location, top citations, payer directories, social profiles, email signatures, ad destination URLs.

See it live on your own practice

EHR-integrated booking, HIPAA-safe tracking, and marketing that reports in kept appointments — in one platform.Book a Demo

Week 5: Cutover

Pick a low-traffic day. Then, in order:

Freeze content changes on both sites.
Deploy the new site to production; verify it renders on both mobile and desktop with a real headless check of live HTML — not a cached admin preview. (House rule: nothing is "live" until both viewports are verified from outside.)
Activate the 301 map. Spot-check the top 100 old URLs immediately: one hop, correct target, 301 not 302.
Search Console: verify the new property, submit the new sitemap, file Change of Address on the old property. Keep the old property — it's your redirect-error monitor for the next year.
Update GBP website links for every location the same day. For multi-location groups, stagger profile edits rather than bulk-editing all listings in one pass — mass same-day edits are a suspension trigger, and a suspended listing hurts more than a slow redirect (ops detail: Google Business Profiles at 20+ Locations).
Update ad final URLs immediately — ads paying to land on a redirect chain waste money and Quality Score.
Keep the old domain registered and serving 301s indefinitely — minimum several years. Dropping it is how a practice's old domain becomes a casino site with your backlinks.

Weeks 6–8 (and out to 12): Watch

Migration success is a monitoring posture, not a launch event:

Daily, weeks 6–7: crawl the old URL inventory for anything returning 404/302/chains; watch Search Console coverage on both properties; watch rankings on the benchmark terms.
Expect a dip. A well-executed healthcare migration typically wobbles for two to six weeks as Google reprocesses. The distinction that matters: a dip with rising new-domain impressions is normal; a dip with old URLs erroring is a broken map — fix the redirects, not the content.
Watch the money pages hardest: provider bios, location pages, top service pages. If one of them hasn't recovered by week 8, inspect it individually (redirect target mismatch, internal links still pointing at old URLs, thin new-page content).
Citations sweep: work the pre-written list until the top citations and payer directories show the new domain.
Keep the compliance scan running on the new domain — redesign-adjacent plugin installs are how a clean site regrows a pixel.

The migration go/no-go checklist

Cut over only when every box is checked: benchmark exported; backup restore-tested; one-to-one 301 map covering 100% of crawled URLs and 100% of backlinked URLs; staging sealed and verified externally; galleries noindexed on the new site; forms and tracking compliant on the new site; GBP/citation update list pre-written; rollback plan written down; a named owner watching Search Console daily for two weeks.

Actually doing the marketing

A migration protects the asset; it doesn't grow it. The post-migration quarter is the right time to press: refresh the top service and location pages while Google is recrawling everything anyway, rebuild internal linking deliberately, and point paid spend at the proven converting pages on the new domain — measured per location, per the enterprise playbook and compliant per the HIPAA-Compliant Marketing guide.

Or hand us the whole thing: PilotPractice runs post-acquisition migrations as a managed sequence — audit, map, hardened rebuild, cutover, and the 12-week watch — on infrastructure where booking, forms, and tracking are HIPAA-compliant by default and backed up before anyone touches DNS. Book a demo and bring the domain you're about to retire; we'll benchmark what's actually at stake.