Migrating a website after an acquisition without inheriting toxic SEO

When you acquire a company and fold its site into yours, the real danger is not the content, it is inheriting a toxic backlink profile. Disavow the bad links on the acquired domain first, then map redirects page by page, and only then point anything at your domain. Do it in the wrong order and you pass the toxicity straight into the site you just paid to protect.

That is the whole warning. The rest of this is the playbook, and one deal that shows exactly why the order matters.

Why is inheriting a toxic backlink profile the real risk in an acquisition migration?

Because redirects pass link equity, and link equity is not always good. When you 301 a page from the acquired domain to yours, you are telling Google the new URL is the successor to the old one. Every signal pointing at the old page, including the spammy, paid, and manipulative links, now points at yours by association.

Content you can see. You open the acquired site, read it, and decide what is worth keeping. Backlinks are invisible from the front end. A domain can look clean while carrying years of link-scheme residue underneath, and none of it shows up until you have merged it into your own profile and watched your rankings soften for no reason you can explain.

We worked with a company that acquired a competitor to absorb its traffic and keyword footprint. The acquired site looked fine. Then we pulled its backlink profile and roughly 90% of it was toxic. Link farms, paid networks, the anatomy of someone who bought their way up the rankings years earlier. Redirecting that domain as-is would have poured all of it into a healthy site. We disavowed first, then redirected. That sequence is the point of this article.

What should you audit before merging an acquired site into yours?

Both backlink profiles, before you touch a single redirect. You are not just auditing the thing you bought. You are baselining the site you already own so you can tell later whether the merge helped or hurt.

Pull the referring domains for the acquired site and score them. The tells: link farms, foreign-language sites linking with commercial anchor text, comment-spam networks, private blog networks, paid directory dumps, historical spikes of low-quality links that map to an old link-buying campaign. Any decent backlink tool flags most of this. The judgment call is the gray middle, the links that are low quality but not clearly manipulative.

Then inventory the content. Every URL on the acquired site sorts into one of three buckets, and you decide the bucket before you build a single redirect:

• Keep and migrate. Pages that rank, earn links from legitimate sources, or serve a real purpose your site does not already cover.
• Redirect. Pages with a clear equivalent on your side, or thin pages whose only value is the clean equity pointing at them.
• Kill. Duplicates, outdated pages, thin junk, and anything whose backlink support is the toxic stuff you are about to disavow anyway.

Most acquisition migrations over-migrate. Someone decides every page must be preserved out of caution, and you end up carrying dead weight and duplicate content into a site that was doing fine without it. The point of the audit is to move less, not more.

How do you disavow toxic backlinks before pointing redirects at your domain?

Build the disavow file for the acquired domain and submit it under that domain's own Search Console property, while it still resolves and before you redirect anything. This is the step people skip, and skipping it is what causes the damage.

The mechanics matter here, so be precise:

1. Keep the acquired domain live and verified in Search Console. You need its own property to submit a disavow file against it. If you redirect first and let the property lapse, you lose the clean way to disavow at the source.
2. Compile the toxic referring domains into a disavow file. Disavow at the domain level, not the individual URL, for anything that is clearly a bad neighborhood. One `domain:` entry kills every link from that source.
3. Submit the disavow on the acquired domain and give it time to process. Google needs to recrawl those links and apply the disavow before the signals are neutralized. This is not instant. Rushing it defeats the purpose.
4. Only then build and deploy the 301 map to your domain. By the time equity flows across the redirect, the toxic portion is already discounted, so what reaches your site is the clean remainder.

Order is everything. Disavow on the source, let it settle, then redirect. Redirect first and you have merged the profiles before the cleanup applies, which means you are disavowing links already attached to your own domain, a slower and riskier fix.

A migration is the highest-stakes moment to fix an SEO problem or to create one. We have used the same care on the upside: a merge-two-domains migration that took a site from 600 to 25,000 monthly visits, and a 600-post content migration for dYdX that drove +3,722% organic growth. Same discipline, opposite direction. The migration either compounds your equity or contaminates it, and the difference is prep work nobody sees.

How do you build a 301 redirect map for the pages worth keeping?

Map every keep-and-migrate and redirect URL from the old domain to its exact successor on yours, one to one, with no lazy redirects to the homepage. A page that ranked for a specific query should land on the page that best answers that query, not on your front door.

The rules that keep equity intact:

• One-to-one wherever a match exists. Old product page to new product page, old blog post to the equivalent. Homepage-catch-all redirects tell Google the old page had no real successor, and the equity mostly evaporates.
• Preserve the few pages with genuine authority. If a handful of acquired pages carry legitimate, high-quality links, migrate the page intact so the URL keeps its inbound equity, or redirect it to the single closest match. Never bury it.
• 301, not 302. A 302 does not pass equity reliably and signals the move is not final.
• No redirect chains. Old URL straight to final URL in one hop. Chains leak equity and slow crawlers, and acquisition migrations breed them.
• Redirect, do not 404, anything with inbound links so the equity is captured, not dropped.

We treat the redirect map as the deliverable that makes or breaks the migration. On large moves we build it as a spreadsheet, validate every mapping, and load it programmatically, the same discipline behind pushing 223 schema articles and 110,000 words into Webflow via Python and the API without hand-editing thousands of entries. At acquisition scale, a redirect map you build by hand and eyeball is a map with holes in it.

How do you consolidate the architecture after the merge?

Fold the acquired site's structure into yours so there is one clean information architecture, not two stapled together. The goal is a single site that reads as one coherent thing to users and crawlers, with no orphaned sections, no duplicate topic clusters competing, and no second navigation logic bolted onto the side.

Watch for keyword cannibalization. When two companies in the same space merge, you often end up with two pages targeting the same query, one from each original site. Left alone, they split the signal and both underperform. Consolidate them into one stronger page and redirect the weaker URL into it. This is also the moment to decide whether the acquired brand keeps a presence or gets fully absorbed, because that decision drives which pages survive.

Then wire the internal links. Every migrated page needs to connect into your existing structure, linking up to the relevant service or pillar page and down to supporting content, so the equity you preserved flows through the site instead of pooling on isolated pages. A page nobody links to internally is a page you migrated for nothing.

Platform matters too. Consolidating two content architectures is far easier on a system where structure, redirects, and CMS content are all API-addressable. It is one reason we run this work on Webflow rather than a builder that fights you at scale.

What is the result of doing an acquisition migration in the right order?

You absorb the traffic and keywords you paid for without importing the liability that came attached. The legitimate equity flows into your site, the toxic portion stays disavowed at the source, the architecture reads as one clean site, and your rankings hold or climb instead of quietly sliding for a reason nobody can trace six weeks later.

The company that acquired the 90%-toxic competitor kept the good and left the bad behind, because the disavow ran before the redirects. Do the same audit-disavow-map-consolidate sequence on any acquisition migration and the merge compounds, the way an acquisition is supposed to. Skip the backlink audit and redirect a clean domain into a poisoned one, and your expensive acquisition quietly makes your SEO worse.

If you are folding an acquired company into your site, the backlink audit is the step that decides whether the deal helps or quietly hurts. Pull both profiles, sort the toxic from the legitimate, and get the disavow in before the redirects, not after. If you want a second set of eyes on the profile before you point anything at your domain, that is the kind of migration work we do, and it is a lot cheaper than untangling a bad merge later.

Frequently asked questions

Do I really need to disavow before redirecting, or can I disavow after the merge?

Disavow before. If you redirect first, the toxic links are already associated with your domain, so you are cleaning up your own live profile instead of the acquired one, which is slower and riskier. Submitting the disavow on the acquired domain while it is still live means the toxicity is discounted before any equity crosses the redirect. Order is the whole game.

How do I know if an acquired domain's backlink profile is toxic?

Pull its referring domains with any competent backlink tool and look at the pattern. Toxic profiles show link farms, private blog networks, foreign-language sites with commercial anchor text, comment-spam, paid directories, and unnatural historical spikes that line up with an old link-buying campaign. A high ratio of low-quality referring domains to legitimate ones is the tell.

Should I redirect every page from the acquired site to my domain?

No. Redirect the pages with a genuine successor or clean inbound equity, keep the pages that earn their place, and kill the duplicates, thin pages, and anything whose only backlink support is the toxic links you are disavowing. Over-migrating drags dead weight and duplicate content into a healthy site. The audit exists so you move less, not more.

What happens to my rankings if I skip the backlink audit?

Most likely a slow, unexplained decline. You inherit the acquired domain's spam by association, Google discounts the merged profile, and your rankings soften over the following weeks with no obvious cause because the damage is buried in link data you never looked at. It is the most expensive kind of SEO problem, invisible until it has already cost you.