Technical SEO · October 1, 2026 · 8 min read
Merging Two Sites Into One Without Losing Both
Most site merges bleed traffic because the redirect map gets written before anyone decides which pages deserve to survive — this inventory fixes the order.
By FluxWriter
Merging two sites into one is usually planned as a redirect job and paid for as a traffic loss, because the decision that matters — which pages survive — gets made last. Most owners treat it as a domain change with extra steps, and the extra steps are where your rankings go. This guide covers choosing the survivor, the page inventory to build before anything moves, and the 90-day reports that show whether it worked.
Why Redirecting Everything Actually Loses Both
The default plan is a one-to-one redirect map. Every URL on the retiring site points at its twin on the surviving one, and where no twin exists, the homepage catches it. It feels complete. It is also the plan behind the classic outcome: a merged site earning less than either did alone.
Two things go wrong. The first is that two sites in one niche almost always rank for the same queries, and a merge does not resolve that overlap — it moves it inside one domain, where both pages keep splitting clicks and links. The second is the homepage catch-all. Google treats a flood of redirects to one unrelated page as soft errors rather than moves, and the value those URLs carried is discarded.
A quieter third problem: the retiring site's internal links are part of why its pages ranked, and a redirect preserves none of them. A page with 40 internal links on the old site lands on yours as an orphan.
So the merge is an editorial decision first. Redirects only execute it.
Choosing the Domain That Survives
The surviving domain should be the one with the deeper history, not the better name. Owners regularly pick the newer brand for looks and hand Google a domain with 12 months of trust to absorb one with 8 years of it. That's backwards.
Read the decision from data, not preference:
| Signal | Where to read it | Favours the site with |
|---|---|---|
| Referring domains | Ahrefs or Semrush Backlinks report | 2x or more the count |
| Non-brand organic clicks | Search Console Performance, 16 months | The larger, steadier line |
| Indexed pages | Search Console Page indexing report | More valid pages, fewer excluded |
| Ranking history | Your rank tracker, or Semrush Organic Research | Older top-10 positions |
| Penalty record | Search Console Manual actions | A clean record, always |
The first two rows settle most cases. When they disagree — one site has the links, the other the traffic — the links usually win. A redirected page keeps most of its clicks within weeks. A referring domain lost in the move takes months of outreach to replace.
Brand can override this only when the numbers are close. Within 20–30% of each other on links and clicks, keep the name you want to be known by. At a 3x gap, the name loses.
Check the penalty row before you commit. A site with an unresolved manual action cannot be the survivor at any traffic level — every redirect would attach to the penalty.
The Page Inventory That Decides Everything
Before you write a single redirect, every URL on the retiring site needs a verdict. Export the full crawl from Screaming Frog or Sitebulb, join it to 12 months of Search Console clicks and your Backlinks report, and sort into four buckets.
Keep. The page has no equivalent on the surviving site and earns clicks or links. Move it across intact at a URL that fits your new structure, and redirect the old one to it.
Merge. The surviving site already has a page on the same intent. One of the two lives, and the loser redirects to it — never to a category or the homepage.
Redirect only. The page is thin or outdated but has links pointing at it. Send it to the closest relevant surviving page. Relevance is the test: a 2019 pricing page redirected to your current pricing page passes value. Sent to the blog index, it passes little.
Drop. No clicks in 12 months and no referring domains. Nothing on it the surviving site lacks. Let it go. On older sites this bucket often runs to 30–50% of URLs, and carrying it across turns a merge into index bloat.
Write the verdict into the spreadsheet as a column. The redirect map comes out of that column — starting from the redirects and back-filling verdicts is how the homepage catch-all creeps in.
Merging Overlapping Pages Without Losing the Better One
The merge bucket is where your traffic is won or lost. Two pages on the same topic across two sites are not duplicates — they are two answers to one query, each with its own links, and Google has been choosing between them.
Pick the survivor the same way you picked the domain: clicks first, referring domains second. Compare the content next. The loser usually has 2–3 sections or a table the winner lacks — carry that across before you redirect.
One cost is specific to a two-domain merge. Across two sites both pages can sit on page one at once, so you held two results and now hold one. The combined page has to land above the better of the two to break even, and it usually does only when the content genuinely absorbs both.
Watch the canonical. If the surviving page still declares one pointing at the retiring domain — common when both sites shared a template — redirect and canonical contradict each other, and the page can drop out.
Fix internal links on the surviving site too, so none point at the retiring domain or a redirected URL. Screaming Frog's Response Codes tab, filtered to internal redirects, lists each one with its linking pages. That count should be zero before you launch.
Sequencing the Cutover
Timing decides how much of the dip you absorb. Do not merge inside 8 weeks of your peak season, or in the same month as a redesign or a CMS change. One variable at a time.
Stage it if the retiring site has more than 300 pages. Move one section — a category, or the blog — wait 3–4 weeks, read the reports, then move the next. Staging adds 2–4 months and turns a catastrophic mistake into a contained one.
On launch day the checklist is short: redirects spot-checked on 50 URLs, the Change of Address tool submitted from the old Search Console property, and a temporary sitemap of the old URLs so the redirects get crawled, removed after 4–6 weeks.
Expect a dip. A clean merge typically loses 10–20% of combined organic clicks for 4–12 weeks, then recovers and, in the better cases, passes the old total by month 4–6. A loss above 30% that has not started to recover by week 6 is a defect, not a settling period.
The Reports That Tell You Whether It Worked
Your verdict in the first 90 days comes from four reports. A rank tracker alone will mislead you.
Open the Performance report on the new property and compare the 28 days after launch against the 28 days before, both old properties combined. Track clicks and impressions together. Impressions recovering while clicks lag usually means your titles or snippets changed in the move.
On the old property, the Page indexing report should show the "Page with redirect" count climbing weekly while valid pages fall toward zero. If valid pages have not started dropping by week 4, spot-check the redirects yourself — the report lags what Google has actually recrawled, so a flat line is a prompt to check rather than proof the redirects are being missed.
The Links report on the old property is your equity ledger. Note the top 20 linked pages before launch. Each should land on a live, relevant page, and any that resolves to something unrelated to its anchor text is a leak to fix that week.
Track your top 50 non-brand queries in a rank tracker, tagged by which site held them. Queries the retiring site owned slip first. A drop of 5 or more positions on one of them usually points at a merge-bucket page, and at content you left behind on the loser.
FAQ
Can I keep both sites running and just link them together?
You can, and it is the slowest way to lose. Two sites in the same niche split every link and click between them, and the overlap grows as both keep publishing. A merge concentrates it. Run the inventory first — if fewer than 20% of your pages overlap, the case weakens.
Do I lose the old domain's authority when I merge?
Some, and how much depends on the redirect map. Page-to-page redirects to relevant targets pass most of the value. Homepage catch-alls pass almost none. A careful map typically lands within 10–20% of the combined baseline by month 3. A catch-all can lose a third or more, and that loss tends to stick.
How long should the old domain stay redirected?
Indefinitely, or for as long as you can keep the registration. Referring domains do not update their links when you move, and the redirects are the only thing carrying that value across. A renewal costs $10–20 a year. Letting it lapse costs every link that still points at it.
The Practical Takeaway
Decide the survivor from links and clicks before touching a redirect, and let the numbers overrule the brand unless the two sites sit within 30% of each other. Export every URL on the retiring site, join it to 12 months of clicks and referring domains, and sort into keep, merge, redirect-only and drop. Build the redirect map from that column, page to page, nothing to the homepage. Stage the move in sections 3–4 weeks apart, submit the Change of Address, and if you are still down 30% at week 6, go hunting for the broken redirect. Start with the 20 pages that hold the retiring site's referring domains.
If you are rebuilding content on the merged site at scale, tools like FluxWriter can help produce the gap-filling pages the inventory exposed — but which page survives, and where every old URL lands, is your call to make first.