How to Merge Two Websites Without Losing Rankings

Merge two sites by mapping every URL on the retiring site to its closest equivalent on the surviving site, then 301 redirecting each one individually. Page-level redirects carry the ranking signals across; bulk-redirecting everything to the homepage throws them away. Expect a dip of four to twelve weeks before the combined site settles higher than either did alone.

A merge is a migration with an extra decision at the front: which site survives. Get that decision and the URL map right and the rest is mechanical.

Decide which domain survives

Not always the bigger one, but usually. Weigh these in order:

Backlink profile. Count referring domains, not raw backlinks, and look at quality rather than volume. This is the signal that's hardest to rebuild, so it should dominate the decision.

Organic traffic and ranking keywords. Which site earns more, and for terms closer to what the business actually sells?

Brand. If one name is the one customers say out loud, that's a real cost to retire even when its SEO is weaker.

Domain history. If either domain carries an old manual action or a sketchy link profile from a previous owner, retire it regardless of its metrics. You'd be inheriting the problem.

If it's genuinely close, keep the site with the stronger backlink profile and move the better brand name onto it as a redirected domain. You can change the name people see; you can't conjure ten years of links.

Map the URLs before you touch anything

This is the whole job. Everything else is execution.

1. Export every URL on the retiring site. Crawl it (Screaming Frog, Sitebulb, or any crawler), then supplement with the XML sitemap, a Search Console export of every URL that got an impression in the last 12 months, and your analytics landing-page report. Crawls miss orphaned pages that still rank; Search Console catches them.

2. Pull the backlinks by destination URL. Use whatever backlink tool you have and export links grouped by target URL. Any page on the retiring site with external links pointing at it is non-negotiable — it needs a redirect to a genuinely relevant destination, not an approximation. How to audit your backlink profile covers pulling that list cleanly.

3. Build the map in a spreadsheet. Four columns: old URL, new URL, why, and a status flag. Every row needs a decision:

Situation on the retiring site	Destination on the surviving site
An equivalent page already exists	301 to that page
No equivalent, but the content is worth keeping	Move the content across first, then 301 to it
Content overlaps an existing page	Merge the best of both into the survivor, then 301
Thin or obsolete page, no backlinks, no traffic	Let it 404 or 410 deliberately
Thin page with backlinks	301 to the closest relevant category or guide
Homepage	301 to the surviving homepage

4. Check the map for laziness. Sort by destination. If a large number of rows point at the homepage or one category page, you have a problem — Google treats an irrelevant redirect as a soft 404 and passes nothing. A redirect only carries value when the destination genuinely answers what the old page answered.

Watch for cannibalization in the merged site

The mistake nobody plans for. Both sites probably had a page on the same topic, and if you move both across you now have two pages competing for one query on one domain — keyword cannibalization, self-inflicted.

Before the move, list the primary keyword for every page coming across and compare it against the surviving site's existing pages. Where two pages target the same query, merge them into one better page and redirect the loser. Doing this during the merge is far cheaper than untangling it six months later.

The order of operations

Freeze publishing on the retiring site so the map can't go stale underneath you.
Move the content that's staying. Get the new pages live, indexed and internally linked before any redirect fires. Redirecting to a URL that doesn't exist yet is the single most common way merges go wrong.
Update internal links on the surviving site to point at the new destinations directly, not through the redirect.
Implement the redirects as 301s, not 302s — a 302 signals a temporary move and delays consolidation. Prefer server-level rules over a plugin for speed at scale.
Test every single one. Crawl the old URL list and confirm each returns a single 301 landing on a 200. Fix any redirect chains so each hop goes straight to the final destination.
Keep the retiring domain registered and the redirects live. Indefinitely if you can — at minimum several years. Letting the domain lapse kills every link pointing at it.
File a Change of Address in Search Console if you're retiring an entire domain and the content maps one-to-one. It doesn't apply to a partial merge into an existing site, and it isn't a substitute for the redirects.
Submit an updated sitemap on the surviving site, and temporarily keep the old site's sitemap live so Google recrawls those URLs and discovers the redirects faster.
Update your highest-value backlinks at the source. For the twenty or thirty best links, email and ask for the URL to be updated. A direct link is always worth more than a redirected one, and it insures you against the redirects ever breaking.

What actually transfers, and what doesn't

A 301 passes essentially all ranking signal — Google confirmed years ago that PageRank is no longer reduced through 301s. Backlink equity, topical relevance and ranking history all move across when the destination is genuinely equivalent.

What doesn't come with you: your Search Console data history (the new property starts fresh), social share counts on the old URLs, and any signal from a redirect Google judges irrelevant enough to treat as a soft 404. What happens to backlinks when you migrate a site goes deeper on the mechanics.

The dip, and when to worry

A visible dip is normal. Google has to recrawl the old URLs, discover the redirects, and reassess the merged site's structure, and that takes weeks rather than days.

Typical shape: a drop in the first two to three weeks, recovery beginning around week four to six, and stability by week eight to twelve. Larger sites take longer because crawling takes longer.

Worry when you see a drop still deepening after six weeks, redirects returning 404s or chains in a crawl, "Page with redirect" appearing against URLs you expected to be indexed, or traffic recovering for most sections while one section stays flat — usually a sign that part of the map pointed somewhere irrelevant.

Monitor weekly: Search Console coverage on both properties, rankings for your top 20 terms, and a monthly recrawl of the old URL list.

Frequently asked questions

How long does it take to recover rankings after merging two websites? Four to twelve weeks for most sites. Google needs to recrawl every redirected URL and reassess the merged site. Small sites with clean one-to-one redirect maps often recover in under a month; large sites with thousands of URLs can take a full quarter.

Should I redirect the old site's pages to the new homepage? No. Redirecting many pages to one homepage is treated as a soft 404, and the ranking signals are discarded. Each URL needs a destination that genuinely covers the same subject. Where no equivalent exists and the page has no links or traffic, a clean 404 is better than an irrelevant redirect.

Do I lose backlinks when I merge two websites? Not if the redirects are right. Links keep pointing at the old URLs, and a 301 passes their value to the new destination. You lose that value only if the redirect is missing, points somewhere irrelevant, or the old domain expires — which is why keeping the retired domain registered matters.

How long should I keep the redirects running? Permanently if the domain is cheap to hold. Google eventually treats a long-standing 301 as a permanent move and transfers indexing to the destination, but third-party sites keep sending visitors through those old links for years. Three years is a practical minimum.

Do I need to file a Change of Address in Search Console? Only when you're moving an entire site to a new domain with a one-to-one URL mapping. For a partial merge into an existing site, the tool doesn't apply — the redirects do the work on their own.

What should I do with the old site's content that has no equivalent? Decide page by page. Content with traffic or backlinks moves across and gets a redirect. Obsolete content with neither should 404 or 410 rather than being redirected somewhere vaguely related — deliberately removing dead weight is part of what makes the merged site stronger.

The bottom line

A merge is won or lost in the spreadsheet. Pick the survivor on backlink strength, map every retiring URL to a genuinely equivalent destination, move the content before the redirects fire, resolve cannibalization while you're already in there, then test every redirect and hold the old domain for years. Do that and the combined site ends up stronger than either half — one domain accumulating every link instead of two splitting them.

Once the merge settles, the fastest way to compound that consolidated authority is steady, relevant link building into the surviving domain. Backlinkster handles that side: one-for-one in-content swaps with owners of related sites, each verified live by code. See the plans.