site consolidation seo
Two sites become one. The technical work is ordinary; the hard part is deciding, page by page, which version wins each topic — and accepting that some rankings are lost by design.
Primary riskTwo sets of pages ranking for overlapping topics must become one, and every merge decision permanently discards something.
Most migration types are technical problems with some content decisions attached. Site consolidation inverts that. The redirect work is ordinary. The difficulty is editorial and commercial: two organizations have two sets of pages ranking for overlapping topics, and the merged site can only have one of each.
That means every overlapping topic requires a decision that permanently discards something. Not a technical trade-off — an actual loss, accepted deliberately, because the alternative is two pages on one site competing with each other.
The comparison table on this page lists the signals worth weighing. Three things about applying them in practice.
Links and traffic disagree more often than not. The page with the most organic clicks and the page with the most referring domains are frequently different pages. An old article that earned coverage years ago may have almost no traffic and considerable equity. Check both lists separately.
Brand fit will sometimes override the data, and that can be correct. If the acquired company’s page performs better but the surviving brand’s voice, compliance position or product naming has to win, that is a legitimate business decision. Make it explicitly rather than letting it happen in the background.
Record the reasoning. Six months later, someone will ask why a particular page was retired, and the traffic data from the time of the decision will no longer be available in the same form. A one-line note per decision saves that conversation.
The instinct when combining two pages is to append one to the other. It produces a long, repetitive document that reads exactly like what it is, and it typically ranks worse than either original.
Merge by editing. Read both, identify what the losing page says that the winner does not, and integrate that material where it belongs in the structure. Often that is two paragraphs and a table, not the whole page. Then redirect.
Consolidations sit at the long end of every recovery window on this site, and it is worth understanding why so the timeline is not misread as failure.
Google has to reprocess two sites’ worth of signals, resolve which URLs now serve queries that previously had two answers, and re-evaluate a merged site with a substantially changed page inventory. That takes longer than forwarding one site to another.
Some ranking loss is also structural rather than a fault. If your two sites previously occupied positions three and seven for a query, the merged page occupies one position. Combined impressions for that query go down. That is the consolidation working as intended, and it should be in the forecast before launch rather than explained afterwards.
If the merge also involves moving to a new domain, domain name change covers the additional steps. For merging a subdomain rather than a separate site, subdomain to subfolder is the closer fit. The full engagement covers running a consolidation end to end.
What you see The surviving site has two pages targeting the same query. Neither ranks as well as the original did alone.
What fixes it Pick a winner, redirect the loser, and merge anything genuinely unique from the losing page into the survivor first.
What you see Every URL on the acquired domain 404s or fails to resolve. All of its accumulated equity is discarded at once.
What fixes it Keep the acquired domain registered and its redirects live for at least a year. The registration cost is trivial against what it preserves.
What you see The surviving page becomes a long, repetitive document that reads as two articles stapled together and ranks worse than either did.
What fixes it Merge by editing, not by appending. Take the genuinely unique material from the losing page and integrate it properly.
What you see Deep pages from the acquired site all land on a category page. Their rankings vanish rather than transferring.
What fixes it Map to the specific surviving equivalent. Category-level redirects are for pages with no equivalent, and they should be a decision.
| Signal | What it tells you | Weight | Trap |
|---|---|---|---|
| Organic clicks | Which page currently earns traffic | High | Recent seasonal spikes distort this — use twelve months |
| Referring domains | Which page carries external equity | High | The winner on links is often the loser on traffic |
| Conversion rate | Which page serves the business better | High | Sample size; a page with nine conversions proves nothing |
| Content depth | Which page will hold up long term | Medium | Longer is not automatically better |
| Brand alignment | Which fits the surviving brand | Medium | Frequently overrides the data, and sometimes it should |
| Publication date | Which is more current | Low | Rarely decisive on its own |
Content decisions come before technical work here, which is the reverse of most migration types.
Every ranking page from both sites, with the queries it ranks for. The overlap between the two lists is the actual scope of the project.
Output Combined inventory with overlap marked
Using traffic, links, conversion and brand fit together. Record the reasoning — this decision gets questioned six months later, and memory will not hold.
Output Winner selection with rationale
Before redirecting, move anything genuinely valuable from the losing page into the winner. Edit it in properly rather than appending it.
Output Updated surviving pages
To its specific surviving equivalent. Category-level fallback only for pages with no equivalent, and only as a recorded decision.
Output Consolidation redirect map
Where possible, migrate one section at a time rather than everything at once. Sequencing makes problems attributable and rollback survivable.
Output Phased cutover plan
Track queries where the surviving site now returns two URLs. Merges create internal competition that only becomes visible weeks later.
Output Cannibalization monitoring
Eight to sixteen weeks is typical, longer than most migration types. Google has to reprocess two sites' worth of signals and resolve which URLs now serve which queries. Consolidations also lose some rankings permanently by design, since two competing pages become one.
Yes, registered and redirecting, for at least a year and ideally indefinitely. External links to the acquired site keep sending traffic and signals for far longer than expected. The registration cost is trivial compared with what letting it lapse discards.
Where the architecture allows it, yes, and it is usually the better approach. Phased cutover makes any traffic movement attributable to a specific section and keeps rollback realistic. The trade-off is a longer period of running two sites.
One has to win. Merge the unique value from the losing page into the winner, then redirect. Keeping both is the worst outcome: they compete with each other on the same site, and the combined result is usually below what either achieved alone.
Send the launch date and what is changing. We will tell you which parts of this page apply to your situation and which do not.