Website consolidation after an acquisition is the process of merging two or more company websites into a single web presence, usually following a merger, an add-on acquisition, or a roll-up. Done well, it preserves the search rankings, referral paths, and customer habits the acquired sites spent years building, and concentrates that value on one domain. Done as an afterthought, it quietly deletes a revenue channel the deal model assumed would continue. This guide covers how PE-backed and founder-owned companies should run a website merge: what to decide before touching a domain, how to build the redirect map, and how to measure the cutover so leaks show up in days instead of quarters.
It is written for sponsors and portfolio executives planning post-close integration, and for platform teams partway through a roll-up with a growing stack of legacy websites that nobody clearly owns.
An acquired company's website is usually handed to IT or to a branding agency, because it looks like infrastructure or like design. It is neither. It is a revenue asset with years of accumulated behavior attached to it: search rankings earned by pages nobody remembers writing, local listings pointing at specific service pages, repeat customers who bookmarked a quote form, referral partners linking to a bio page, and phone calls generated by pages the analytics account has never properly tracked.
When a merge is run as a design project, that behavior has nowhere to land. Pages disappear, URLs change without forwarding, and the phone number on the old contact page goes stale. None of it announces itself. Organic search traffic does not drop the day the old site goes dark; it erodes over weeks as search engines recrawl and conclude the content is gone. By the time the decline is visible in a monthly report, the rankings that produced the revenue have been handed to competitors, and rebuilding them costs far more than preserving them would have.
The first consolidation question is not technical. Whether the acquired site should fold into the platform's domain, remain a standalone brand, or live somewhere in between is a brand architecture decision, and it should be made deliberately rather than inherited from whoever set up the hosting. A branded house concentrates equity and simplifies the web estate; a house of brands preserves local goodwill at the cost of running parallel sites. The tradeoffs, and the cost of deciding late, are covered in the brand architecture guide.
The web decision then follows the brand decision. If the acquired brand is being retired, the site merges fully and the old domain forwards permanently. If the brand is being kept, the site stays, but it should be instrumented and aligned with the platform rather than left to drift. The expensive failure mode is the unmade decision: an acquired site left running on autopilot, unmaintained and unmeasured, slowly losing the rankings the deal paid for.
A redirect map is the document that pairs every URL on the retiring site with its closest equivalent on the surviving site, so that a permanent redirect can pass each page's accumulated authority to its true successor. Building it properly means inventorying every page that earns traffic, ranks for anything, or has links pointing at it, using analytics, Search Console, and a backlink index, then mapping each one to the page that serves the same intent. Pages with no traffic, no rankings, and no links can be retired without ceremony.
What the map must never do is dump retired pages onto the homepage or a generic hub page in bulk. Search engines treat that pattern as a soft deletion: the specific page that ranked for a specific problem now answers nothing, so the ranking decays. We have watched a consolidation cut a site's search impressions roughly in half because a handful of retired pages were pointed at a single hub page instead of their actual successors, and most of the loss traced to just two URLs. One-to-one redirects are tedious. They are also the entire game.
The order of operations matters more than the tooling. Before anything is migrated, establish where the acquired company's revenue actually comes from, because the pages worth preserving are defined by revenue, not by pageviews. A commercial audit, about eight weeks, maps revenue to channels and exposes what the analytics account has been missing. The findings change merge plans. In one PE-backed services company we audited, 38 percent of revenue arrived through word of mouth no system tracked; the website equivalent is the unglamorous page that quietly feeds phone calls, which a pageview-ranked content inventory would have retired. That diagnostic sequence is how we begin every engagement.
With the revenue map in hand, the merge itself runs in stages: content inventory and keep-merge-retire decisions, redirect map build and review, staging migration with the redirects tested, cutover, then a monitored stabilization window. Compressing these stages to hit an internal rebrand deadline is the most common way the revenue protections get skipped.
Every page on the retiring site gets one of three verdicts. Keep the pages that earn: anything ranking for commercial terms, anything with meaningful inbound links, location and service pages that feed calls, and content that converts. These migrate with their substance intact, not rewritten into brand voice at the cost of the terms they rank for. Merge the duplicates: when both companies have a page for the same service, consolidate onto the stronger URL and redirect the weaker into it. Retire the rest, but with redirects for anything that ever earned a link.
Multi-location platforms deserve special care. Location pages carry local rankings and citation consistency, and a consolidation that collapses them into a single locations index surrenders local search positions in every market at once. For a roll-up whose growth case depends on owned customer acquisition, the local page inventory is often the single most valuable thing being migrated. How owned acquisition compounds for multi-site platforms is covered in the CAC reduction guide.
A merge needs a baseline and a watch. Before cutover, record organic sessions by landing page, rankings on the terms that drive revenue, calls and form fills by source, and the backlink profile of both sites. After cutover, watch weekly: crawl errors and 404s, index coverage of the new URLs, rankings on the money terms, and lead volume by source. A redirect map error found in week one costs almost nothing; the same error found in month three has already compounded.
The board version of this is simple: the website merge should appear in the integration plan with a revenue-protection line, an owner, and a weekly metric during the stabilization window, exactly like any other commercial workstream. The alternative, discovering in a quarterly review that organic lead flow fell by a third after the rebrand, converts a preventable process failure into a permanent impairment of an asset the fund paid for.
If every page that earns traffic or links is redirected one-to-one to its closest equivalent on the surviving site, most companies retain the large majority of their search performance, and many improve over time as authority consolidates onto a single domain. If pages are deleted or redirected in bulk to a homepage or hub page, search engines treat those pages as removed, and rankings for their topics decay within weeks. The outcome is determined almost entirely by the quality of the redirect map.
Often yes, for a transition period. The answer follows the brand architecture decision. If the acquired brand is being retired, its site should merge into the platform site with full one-to-one redirects. If the brand is being kept for its local or market equity, its site stays live but gets instrumented, maintained, and aligned with the platform. The damaging option is the default one: leaving the acquired site running unowned and unmeasured while its rankings and content decay.
With a complete one-to-one redirect map, search engines typically reprocess the moved pages over several weeks, and most sites stabilize near their prior performance within two to three months. Without a proper map, there is no recovery window to speak of, because the rankings were not moved but abandoned, and winning them back means competing for them from scratch.
Bulk-redirecting retired pages to the homepage or a generic hub page. It feels tidy and ships fast, but it severs the connection between a specific customer problem and the specific page that ranked for it. Search engines read the pattern as content removal and reassign the rankings to competitors. The second biggest mistake is sequencing: rebranding the site before anyone has established which pages actually produce revenue.
Have a revenue problem the board is asking about? Start a conversation.