Merging Two Websites Without Losing Rankings

Merging two websites is an SEO problem first and a branding problem second. Search engines do not see a merger; they see one set of URLs disappearing, another set absorbing them, and two bodies of content that may now compete for the same queries. The rankings you keep depend on three decisions: which page survives when both sites cover the same topic, how every retired URL is redirected, and how you handle the overlap so the combined site does not undercut itself.

This guide is about consolidation specifically, meaning two live domains becoming one. A single-site move to a new domain or platform has its own checklist, and the mechanics overlap, but the hard part here is different: you are choosing winners among pages that both have history, links and traffic. Loss in a merger rarely comes from the redirect technology. It comes from discarding the wrong page, redirecting to something irrelevant, or leaving two versions of the same answer in the index.

Decide the Structure Before You Touch a URL

The first decision is architectural: does one domain absorb the other, or do both fold into a new third domain? Absorbing into the stronger existing domain is almost always safer. A brand-new domain carries no history, so you would be asking search engines to transfer signals from two sources into a place with nothing behind it, and every transfer is lossy to some degree. A third domain is justified when the merged company has a genuinely new name and neither old brand can carry it, and in that case you should plan for a longer recovery.

Define which site is the acquirer and which is the retiring side, even if the business calls it a merger of equals. Two domains merging into one of them is a clear direction. Two sites that keep half their sections each is a patchwork, and patchworks produce redirect chains and orphaned pages. If legal or branding insists on both names surviving as separate properties, you are not merging, and the question becomes cross-linking and cannibalization management rather than consolidation.

Also decide the URL structure of the destination before mapping anything. The retiring site's content has to land somewhere sensible. Options include a subdirectory that preserves its identity (for example a division folder), merging into existing sections of the main site, or a mixture. Subdirectories keep topical clusters intact and make redirect rules easy to write as patterns. Subdomains are treated as separate from the main site in many practical respects, so folding a blog or product line into a subdomain gives you less consolidation than a folder does.

Inventory Both Sites and Score Every Page

You cannot decide which URLs survive without data on both sides. Export every indexable URL from each site through a crawl, then join it with four sources: organic clicks and impressions from Search Console for the last twelve months or more, referring domains from a backlink tool, conversions or assisted conversions from analytics, and the current indexed status. Seasonal businesses need a full year so a quiet quarter does not make a valuable page look dead.

The aim is a single spreadsheet with one row per URL and enough columns to sort it into four buckets. Pages with meaningful traffic or links are assets. Pages with neither but with a real business purpose, such as a legal page or a support article, are required. Pages with neither traffic, links nor purpose are candidates for deletion. And pages that duplicate a topic on the other site are the overlap set, which is where the real decisions live.

Keep the inventory honest about external links. A page that earns no traffic can still hold a link from a site that matters, and redirecting it correctly preserves that link's value. Deleting such a page with a 404 throws the link away. Sort by referring domains before you decide anything is disposable.

Choosing Which URL Survives When Content Overlaps

Overlap is the defining feature of a merger. If both companies sold accounting software, both probably have a page on invoicing, a page on pricing and a blog post about year-end reporting. You cannot keep both, and you cannot redirect them blindly in one direction. Compare each pair on the evidence rather than on which brand is senior.

A workable order of criteria is below. Apply them in sequence and stop when one decides the case.

• Organic performance. The page that currently earns more clicks and ranks higher for the shared query is usually the survivor, because it has already proven it satisfies the intent.
• Backlink profile. If the weaker performer has far more referring domains, consider keeping its URL or at least merging its best content into the survivor before redirecting.
• Content quality and completeness. The survivor should be the more thorough page. If the loser has sections, examples or data the winner lacks, fold them in first so the retired page leaves something behind.
• Intent fit. A category page and a blog post can target the same words but serve different intents. Do not merge a transactional page into an informational one because their keywords match.
• URL quality and age. Prefer a clean, stable URL that has been live longer, all else equal, since you avoid introducing an unnecessary new address.

Merge Content, Then Redirect

When two pages are close in strength, the best outcome is often a combined page that is better than either original. Take the surviving URL, add the useful material from the retiring one, update facts to reflect the merged company, and only then point the old address at it. A redirect tells search engines that the old page has moved to a substitute. If the substitute contains the substance of the original, the signals follow more reliably. If the destination is thinner or about something else, search engines may treat the redirect as a soft 404 and drop the old page's value.

Not every retiring page has a counterpart. Some content simply has no home on the acquiring site: a product that was discontinued, a region the combined company no longer serves. You have three honest options. Redirect to the closest relevant category or hub if one exists, keep the page live on the acquirer's domain if it still has value, or return a 410 or 404 if nothing relevant remains. Sending those URLs to the homepage is the tempting shortcut and usually the worst, because a homepage is rarely a relevant replacement and large volumes of mismatched redirects are treated much like 404s.

Be disciplined about thin leftovers. A merger tends to leave dozens of near-empty pages: team bios for people who left, event pages from past years, location pages for closed offices. Decide page by page rather than carrying them across out of caution, because a bloated combined site dilutes the authority of the pages that matter.

Building the Redirect Map

The redirect map is the core deliverable. It is a two-column file listing every retiring URL and the one destination it should reach, built from your inventory decisions. Use permanent 301 redirects, which tell search engines the move is lasting and that signals should transfer. Each old URL should go to its final destination in a single hop. Chains, where A redirects to B and B to C, waste crawl effort and add points of failure, and they tend to appear when the acquirer has already been through an earlier rebrand. Flatten them before launch by checking whether any destination is itself a redirect.

Write rules as patterns where the structure allows it. If the whole retiring blog moves to a folder on the main site with slugs unchanged, one rule handles thousands of URLs. Where slugs differ, you need explicit one-to-one entries. Preserve the path and handle query strings deliberately, because tracking parameters on inbound links should not break a match. Test a large sample, plus every page that has backlinks or meaningful traffic, before anything goes live.

Remember what redirects do not cover. Images, PDFs and other files hosted on the retiring domain have their own URLs and their own links, so include them. Internal links inside the moved content should be updated to point straight at the new addresses rather than relying on redirects to catch them, and so should canonical tags, hreflang annotations and sitemap entries. A canonical tag pointing at a redirected URL sends search engines conflicting instructions.

Handling Cannibalization During and After the Merge

Cannibalization is what happens when two pages on the same site compete for one query and search engines alternate between them or rank neither well. A merger creates it at scale and overnight, because pages that were rivals on separate domains are now siblings. Some of it is resolved by your redirect decisions, but it can also appear in a quieter form: you keep both pages because they seemed different, and they turn out not to be.

Look for the pattern in Search Console. Filter by a shared query and check whether multiple URLs from the combined site receive impressions for it, and whether the URL showing changes from day to day. Positions that bounce between two URLs are a typical sign. The fixes follow the same logic as the survivor decision: merge and redirect if the pages answer the same question, differentiate them clearly if the intents differ, or use a canonical tag if you genuinely need both accessible but only one indexed.

Watch your internal linking too. After a merge, navigation and related-link modules from both sites often point at both versions of a topic. Consolidate anchor text so each target query has one obvious page that most internal links reach. Links are one of the clearest signals of which page you consider primary.

Launch, Signal the Change and Monitor

Launch the redirects across the whole retiring domain at once rather than trickling them out, and keep the old domain registered and pointing correctly for as long as you can afford, since old links and bookmarks keep arriving for years. If the retiring site is verified in Search Console, use the Change of Address tool where it applies (it handles domain-level moves and does not apply to a move from a domain into a subfolder of another). Keep both properties verified so you can monitor them.

Submit an updated sitemap for the surviving site that lists the new URLs. You can also keep a sitemap of the old URLs temporarily so crawlers find and process the redirects faster. Update external profiles you control, such as social accounts, directories and partner pages, and contact the owners of your most valuable inbound links to ask for a direct update. A direct link is slightly better than one passing through a redirect, and it protects you if the redirects are ever removed.

Expect turbulence. Rankings commonly dip and move for a period after a consolidation while pages are recrawled and reprocessed. The length depends on the size of the sites and how often they are crawled, so set expectations with stakeholders in advance rather than reacting to the first week. Monitor the retiring domain's 404 and soft 404 reports, the coverage of the new URLs, and clicks for the top queries from both sites combined. A sustained drop on a specific group of pages usually points at a redirect mapped to the wrong destination or a section dropped in the content merge, and those are fixable once you can see them.