A company merger redirect is the technical and strategic process of consolidating the web presences of two or more companies, following a business merger, acquisition, or consolidation, onto a single authoritative domain, using permanent redirects to transfer traffic, link equity, and SEO equity from the retiring domains to the surviving domain. When Company A acquires Company B, or two equals merge into Company C, the digital properties of each legacy entity must be unified under the combined brand’s single web presence.

Company mergers create complex redirect management scenarios because each legacy company typically has its own established domain with its own backlink profile, its own indexed pages, its own loyal users, and its own brand recognition. A simple technical redirect handles the URL routing, but the strategic decisions surrounding a merger redirect are far more complex. Which domain becomes the canonical primary? How is the content from each legacy site consolidated? How are customers of each legacy company communicated to about the change? How long should each legacy domain continue to redirect? These questions require coordinated decisions across technical SEO, brand strategy, customer experience, and business strategy.

For redirect management merger redirects represent some of the most consequential configurations in a domain portfolio, each legacy domain may have accumulated years of backlink equity and brand recognition that should be carefully preserved through the transition rather than abandoned. Correctly executed merger redirects consolidate the combined equity of all merging entities onto the surviving domain, emerging from the merger with a stronger combined digital foundation than any individual entity had alone.

Types of company mergers and their redirect implications

Different merger structures create different redirect requirements, the appropriate approach depends on the relationship between the merging entities and their digital properties.

Acquisition, acquirer absorbs acquired: Company A acquires Company B. Company A’s brand and domain survive. Company B’s brand and domain are retired. All of Company B’s web presence redirects to Company A’s domain. The redirect strategy is relatively straightforward, map Company B’s URLs to the most relevant equivalents on Company A’s site and deploy permanent redirects.

The complexity arises from content consolidation, Company B may have product pages, blog posts, documentation, and service pages that duplicate, complement, or contradict content on Company A’s site. Before configuring redirects each page on Company B’s domain must be evaluated, does it have a direct equivalent on Company A’s domain? Should it be merged with existing Company A content? Is it unique content that should be added to Company A’s site? The redirect destination for each Company B URL depends on these content decisions.

Merger of equals, new combined brand: Company A and Company B merge to create Company C. Both legacy domains retire and redirect to a new domain. Both legacy domains contribute their accumulated equity to the new combined domain. This scenario is the most complex, neither existing domain is the primary, a new domain is being built from scratch and must receive equity from both sources simultaneously.

The new domain starts with zero direct authority, the authority flows from both legacy domains through their redirect configurations. The combined backlink profiles of Company A and Company B provide the new domain with a strong starting authority base, but only as their equity is transferred through correctly configured 301 redirects as Googlebot processes the signals.

Parent absorbs subsidiary: a parent company acquires and integrates a subsidiary, retiring the subsidiary’s independent domain and integrating its content into the parent’s domain structure. Similar to an acquisition but typically involves more content integration, the subsidiary’s content becomes a section or category within the parent’s site rather than simply being redirected to relevant pages.

Brand portfolio consolidation: a company operating multiple brands under separate domains consolidates some or all onto a primary domain, perhaps maintaining separate domains for distinct brand identities while consolidating overlapping properties. Redirect strategy depends on which properties are being consolidated and which are being maintained independently.

Strategic decisions before configuring redirects

Several strategic decisions must be made before any redirect rules are deployed, the redirect configuration follows from these decisions rather than preceding them.

Choosing the primary domain: when one entity is clearly dominant, an acquirer absorbing a small acquisition, the acquirer’s domain is typically the natural primary. When entities are more equal the decision involves comparing relative domain authority, backlink profiles, brand recognition, organic traffic, and strategic fit. The domain with stronger SEO metrics, measured by Domain Rating, Domain Authority, total referring domains, provides a stronger foundation for the combined entity.

However SEO metrics alone should not determine the primary domain, brand considerations, customer relationships, and strategic positioning matter equally. A domain with slightly lower SEO metrics but stronger brand recognition among the target customer base may be the better primary even if the competing domain has higher raw authority scores.

Content consolidation mapping: before building the redirect map audit both legacy sites’ content and determine the final content architecture:

Pages that directly overlap, duplicate or near-duplicate content covering the same topics, require consolidation decisions. Keep the best version, merge the content into one comprehensive page, or create a new page combining the best from both. The redirect for the retired page points to the surviving consolidated page.

Pages that complement, covering different aspects of related topics, may both be kept, potentially restructured and cross-linked. The redirect from any URL that changes points to the new URL.

Pages unique to one entity, covering topics not addressed on the other entity’s site, should typically be migrated to the primary domain. The redirect from the old domain URL points to the equivalent new URL on the primary domain.

Pages with high backlink equity, regardless of content quality, warrant careful redirect treatment. A page with many high-quality backlinks should redirect to the most topically relevant page on the primary domain, maximising equity transfer.

Brand communication planning: merger redirects are not just technical operations, they affect customers who know the old domains. Customer communication should precede or accompany the redirect deployment, explaining the merger, introducing the new combined brand, and directing customers to the new domain. Customers who encounter a redirect without communication context may be confused or concerned, clear proactive communication transforms the redirect from a confusing experience to a positive brand introduction.

Building the merger redirect map

The redirect map, the comprehensive document mapping every legacy URL to its primary domain destination, is the operational foundation of a merger redirect.

Crawling both legacy domains: complete crawls of all legacy domains before configuring any redirects. Crawl tools, Screaming Frog, Sitebulb, export complete URL inventories including response codes, title tags, meta descriptions, and internal link structures. The crawl data provides the complete list of URLs that need redirect treatment.

Backlink audit of all legacy domains: export the complete backlink profiles of all legacy domains through Ahrefs, Moz, and Semrush, using multiple tools for completeness. The backlink audit identifies which legacy URLs have the most valuable backlinks, these are the highest-priority redirect sources. A legacy URL with many high-authority backlinks is wasting significant equity without a correctly configured redirect.

Mapping to primary domain destinations: for each legacy URL determine the most appropriate primary domain destination:

Exact content match, the primary domain has a page covering the identical topic. Redirect directly to that page.

Category match, no exact page match exists but the primary domain has a relevant category or section. Redirect to the most specific relevant section.

Homepage fallback, no relevant section exists. Redirect to the primary domain homepage as a last resort, though this is the least precise option and provides the weakest equity transfer.

New page to be created, a legacy URL has significant backlink equity and no good match exists on the primary domain. Create a new page on the primary domain covering the topic and redirect to it, maximising equity transfer to a topically relevant destination.

Wildcard rules for URL patterns: when legacy URLs follow consistent patterns, /blog/YYYY/MM/slug, /products/category/item, /services/service-name: wildcard redirect rules handle entire URL patterns rather than individual mappings. A pattern-based rule for the entire blog section, /blog/* → primary-domain.com/blog/*: handles thousands of blog post URLs with one rule rather than individual mappings for each post.

Deploying merger redirects

With the redirect map complete the deployment follows the same principles as any large-scale redirect migration, with the additional complexity of coordinating multiple legacy domains simultaneously.

Staged deployment by domain: for mergers involving multiple legacy domains consider staged deployment, deploying redirects for one legacy domain at a time rather than all simultaneously. Staged deployment limits the blast radius of any configuration errors, problems with one domain’s redirects do not affect others. Each stage can be monitored and verified before the next stage deploys.

Verifying redirect destinations: before deploying redirects verify that every redirect destination on the primary domain returns a 200 OK response. Redirect destinations that return 404 errors waste the equity from the source’s backlinks, and deliver a poor user experience to visitors following the redirected URL. Complete destination verification before redirect deployment catches missing pages before they become broken redirect chains.

Bulk redirect import: mergers involving hundreds or thousands of legacy URLs benefit from bulk redirect import, deploying the complete redirect map from a CSV file rather than manually creating individual rules. Redirect management platforms and web servers support bulk import, the redirect map spreadsheet becomes the configuration deployment document.

SSL certificates for all legacy domains: HTTPS visitors to legacy domains must complete a TLS handshake before receiving the redirect response. Valid SSL certificates must be active on all legacy domains for HTTPS redirect serving to work. Certificate provisioning for legacy domains should be completed before redirect deployment, or the redirect platform’s automated certificate management should handle this as part of onboarding legacy domains.

Managing multiple legacy domains post-merger

After a merger redirect is deployed managing the portfolio of legacy domains requires ongoing attention.

Monitoring redirect performance across all domains: each legacy domain requires ongoing monitoring, verifying that redirect rules are correctly serving responses, that SSL certificates remain valid, and that domain registrations do not lapse. Monitoring dashboards should provide visibility across all legacy domains rather than requiring individual domain checks.

Outreach to high-value backlink sources: the highest-value backlinks pointing to legacy domain URLs are worth direct outreach, contacting the linking sites and requesting they update their links to the new primary domain URLs. Direct links to the primary domain pass equity without redirect hop loss. Outreach should target the most authoritative linking domains, smaller sites are not worth the outreach investment.

Maintaining legacy domain registrations: all legacy domains from the merger must be maintained indefinitely, or at minimum for 2-3 years. Allowing a legacy domain to expire breaks all its redirects, permanently losing the equity from every backlink pointing to that domain. Domain expiry is the most damaging post-merger maintenance failure. Automated domain renewal and portfolio monitoring prevent accidental expiry.

Secondary brand protection registrations: beyond the primary legacy domains register alternative TLDs and common misspellings of both legacy brand names, preventing competitors or squatters from acquiring these domains after the merger. Legacy brand protection domains redirect to the primary domain alongside the primary legacy domains.

Common merger redirect mistakes

Not auditing backlink profiles before redirect mapping: building the redirect map without backlink data means high-value legacy pages may redirect to poorly matched destinations rather than topically relevant primary domain pages. Backlink audit data should drive redirect destination prioritisation, the highest-equity legacy pages deserve the most careful redirect destination selection.

Deploying redirects before content is ready: redirecting legacy URLs to primary domain destinations that do not yet exist, returning 404 errors. Redirect destinations must exist and return 200 OK before redirects are deployed. Content migration should precede or accompany redirect deployment, not follow it.

Using temporary redirects: implementing 302 temporary redirects rather than 301 permanent redirects for merger consolidation. Temporary redirects do not transfer equity and do not trigger Google’s index updates. All merger consolidation redirects must be 301 permanent redirects.

Inconsistent redirect destination selection: different team members selecting redirect destinations without a consistent methodology, some redirecting to the homepage, others to category pages, others to specific product pages. Consistent methodology, most topically relevant destination, category if no exact match, homepage only as last resort, produces better equity transfer outcomes than ad hoc decisions.

Premature legacy domain retirement: decommissioning legacy domains before the merger’s redirects have been fully processed by search engines and before backlinks have been updated. The standard minimum is 2-3 years, legacy domains with strong backlink profiles should be maintained indefinitely.