Blog / Technical SEO /

Merging two websites into one without losing traffic

“We’ll move everything and lose no traffic.” I’d be wary of anyone who says that.

When two businesses merge, or an owner decides two sites should become one, careful planning can cut avoidable losses. But search visibility may change, and no checklist guarantees that every ranking or visit transfers.

Decide what belongs on the destination

Start with why you’re merging. Do the sites serve the same audience and offer? Is one outdated, or do both have pages worth keeping? Map the content before touching DNS. For every old URL, decide whether there’s a close equivalent, whether several pages should become one, or whether the content should be retired.

Don’t redirect every old page to the new homepage. A redirect should take visitors and crawlers to the most relevant destination. Send an old service article to a broad homepage and the user loses the context they clicked for. Where no equivalent exists, I’d rather return a clear not-found than an irrelevant redirect.

Build a complete URL map

Export known URLs from both sites using sitemaps, analytics, Search Console, a crawl and any page inventory. No source is complete alone. Include valuable pages with little recent traffic, and URLs with backlinks or enquiries. Record old URL, new URL, planned action and reason.

For each retained page, set a direct permanent redirect from the old URL to its best equivalent, with no chains or loops. Update internal links, canonicals, XML sitemaps and any structured data that references the old host. Check trailing slashes, case, query parameters and protocol differences. Keep redirects for a long time, because users and other sites keep using old links.

Prepare the destination first

Before launch, make sure the destination site is crawlable and ready. Confirm that pages return the expected status codes, important content is present, robots rules do not block the site, and canonical tags point to the intended URLs. Test forms, checkout, navigation and mobile layouts. If the destination is still under construction, do not send the old site’s audience into unfinished pages.

Plan domain and DNS changes with whoever manages them. DNS and SSL are a regular part of my work, and I check the certificate on the new host and that HTTP and HTTPS both resolve as intended. DNS takes time to propagate. Keep access to the old hosting and domain settings until the migration is verified.

Launch in a controlled way

Choose a launch window when the people responsible are available to monitor the site. Capture a baseline of important URLs, traffic and technical state. Apply redirects and update the destination sitemap. Verify a sample of old URLs manually and crawl the new site for broken links, redirect chains, accidental noindex directives and missing canonicals.

Submit the destination sitemap in Search Console and monitor indexing and crawl activity for both properties. Google’s Change of Address tool may apply to a move between domains when its requirements are met; it does not replace redirects or careful monitoring. Keep both properties verified and retain the old domain so Google and visitors can follow the redirects.

Watch for issues and avoid panic fixes

After launch, check server errors, 404s, redirect behaviour, Search Console indexing and relevant analytics. Compare landing pages and queries over a reasonable period, accounting for seasonality and campaigns. A short-term fluctuation does not prove the migration failed, but broken redirects, missing pages or a blocked destination deserve prompt attention.

Don’t make sweeping content changes at the same time unless they’re in the reviewed plan. If rankings drop, use the URL map to trace affected pages and check redirects and content. Fix concrete problems rather than rewriting everything because of one graph.

Keep the migration accountable

Assign an owner to each step: mapping, redirect implementation, DNS, analytics, content review and post-launch checks. Record what changed and when. Make sure the business knows which domain to use in email, advertising, social profiles and printed materials. External links and citations may take time to update, so contact important partners where appropriate.

The best migration is one where users can still find what they came for and the team can explain the decisions. Zero traffic change is not on offer.

Preserve what people already rely on

Before launch, look beyond rankings. Old URLs may appear in invoices, bookmarks, email campaigns, partner websites and printed materials. Redirects help, but a customer may also need updated links and contact information. Check branded search results and public profiles after the merge, then update the places the business controls. If email addresses share the domain, coordinate mail records with the DNS change so a website migration does not interrupt messages. Keep a copy of the old site or a documented backup until the new version is verified. A migration is easier to recover from when the team knows what the previous state was and who can restore it. These operational checks protect continuity even when search engines are still processing the move.

Before you merge, can you trace every valuable old URL to a relevant destination?