Website Migration: Safely Consolidate Two Domains Without Losing SEO
A practical website migration guide for consolidating a legacy and newer site, selecting surviving pages, mapping redirects, and verifying technical, user-facing, and AI-visibility outcomes after launch.
· 14 min read
A real estate company with a 20-year legacy domain and a newer, faster site can lose valuable URLs, backlinks, and search visibility if it simply points both homepages at one another. A disciplined website migration preserves the strongest content, maps every meaningful old URL, and gives the team concrete evidence that SEO, performance, accessibility, links, and AI-answer visibility survived the move.
“Changing a website” may mean editing a WordPress page, previewing a new Elementor layout, moving from WordPress to Showit, changing a website domain, or consolidating two overlapping sites. Those are different jobs. This guide prioritizes the highest-risk scenario: choosing one public domain and merging a newer site with a legacy site without turning years of useful content into broken links or irrelevant redirects.
Google’s site-move guidance recommends preparing the new site, creating a URL map, implementing permanent redirects, updating references, and monitoring the move. The work should begin with a content and URL decision—not a homepage redesign. (Google Search Central)
Start with the two-domain consolidation decision
When two domains represent the same business, the long-term target should usually be one canonical public site. Keeping both domains fully live with substantially duplicate pages creates a confusing experience for visitors and makes it harder to maintain consistent content, tracking, canonical URLs, and internal links.
For example, a real estate firm may have legacyrealty.com, which has 20 years of branded links and indexed neighborhood pages, and newrealty.com, which has better templates and a more usable CMS. It may make sense to place the newer platform on legacyrealty.com if that remains the durable company name and recognized public address. The alternative can also be correct if the newer brand is permanent, but the decision needs documented business ownership rather than an assumption that the older domain always wins.
The selected primary domain should meet these tests:
- It matches the business’s intended long-term name and offline marketing.
- It can support the preferred platform, security configuration, analytics, and editorial workflow.
- It has a clear plan for retaining valuable legacy URLs and content.
- The other domain can remain registered and serve tested redirects for the foreseeable future.
- Stakeholders agree which email, social profiles, Google Business Profile links, printed materials, and citations need updating.
A domain consolidation is not a reason to merge every page blindly. The aim is one useful destination for each meaningful searcher intent, not one enormous site full of duplicated city pages, old promotions, and competing service descriptions.
Build an inventory before design or DNS work
The migration inventory should combine both sites before anyone changes DNS records, templates, or navigation. Start with crawls of the legacy and newer domains, then add XML sitemaps, Google Search Console exports, analytics landing pages, paid-campaign URLs, server logs where available, backlink reports, and manually maintained lists of key pages.
This produces a fuller picture than a CMS export alone. A WordPress dashboard may list published posts, for example, but it may not reveal a valuable old .php URL that still receives backlinks or an unlinked PDF that appears in search results.
Use one row per old URL
A practical spreadsheet needs more than an old URL and a redirect destination. Include the page’s purpose and evidence of value so reviewers can make defensible decisions.
| Legacy URL | Newer-site URL | Search intent | Evidence | Decision | Final destination |
|---|---|---|---|---|---|
/neighborhoods.php | /areas/ | Browse local areas | Indexed and linked internally | Merge | /neighborhoods/ |
/first-time-buyers/ | /buying/ | Buyer guidance | Organic landing page | Keep and improve | /buyers/first-time-buyers/ |
/promo-2021/ | — | Expired offer | No current equivalent | Retire | 410 response |
/lakeview-condos/ | /condos/lakeview/ | Specific property search | Backlinks and traffic | Redirect | /condos/lakeview/ |
For large sites, this work benefits from repeatable crawling rather than sampling a few top pages. Audra’s guide to crawling large websites explains the operational difference between inspecting a small URL list and comparing a substantial inventory before and after a move.
Decide which overlapping pages keep, merge, or retire
Two-site consolidation becomes difficult when both domains have pages about the same service, location, or topic. The team should not keep both merely because both exist, and it should not pick the newer page solely because its design looks better.
For each overlapping pair, compare five factors: search intent, organic landing-page history, backlinks and referring pages, factual completeness, and conversion usefulness. A legacy page may be visually dated but contain unique local history, author expertise, FAQs, or links that the newer version lacks. Conversely, a newer page may better answer the same query with clearer structure, current contact details, and stronger mobile usability.
Apply four page-level outcomes
Every duplicate or near-duplicate page should receive one of four explicit outcomes:
- Keep: Retain the better page at its preferred URL when it already satisfies the intent and contains complete, current information.
- Merge: Combine unique evidence from both pages into one stronger destination, then permanently redirect the discontinued URL to that consolidated page.
- Replace: Build a new page when neither existing version fully serves the intent. This is common when two thin location pages should become one detailed area guide.
- Retire: Return a 404 or 410 only when the content is permanently unavailable and no relevant replacement exists. A retired 2021 promotion is a stronger candidate than a still-relevant buyer guide.
Consider two pages: /austin-relocation/ on the legacy site and /moving-to-austin/ on the newer one. If both target relocation advice, the team can preserve the legacy page’s local statistics, agent credentials, and inbound-link value while using the newer page’s clearer structure. Publish one complete relocation guide, choose its final URL, redirect the other page with a 301 or 308, and update internal links to the chosen address.
Avoid redirecting discontinued pages to the homepage by default. It gives users an unrelated destination and hides the underlying content decision. Google identifies permanent server-side redirects as a strong signal for permanent URL moves, but the redirect still needs to lead to a relevant destination. (Google Search Central)
Separate previews and routine edits from a real migration
A temporary browser edit is useful for discussing a proposed change, but it is not a website migration test. In Google Chrome DevTools, a reviewer can inspect an element and edit the displayed HTML or CSS in the Elements panel. Those browser-side edits normally disappear after reload and do not update the server, CMS, search index, or another visitor’s screen. (Chrome for Developers)
Chrome DevTools is appropriate for showing a stakeholder a revised headline, testing whether a button label wraps on mobile, or capturing a quick visual mock-up. It cannot validate a production canonical tag, HTTP status code, redirect, structured data output, or server-rendered content.
For genuine temporary testing, use a protected staging environment, preview URL, or branch deployment. WordPress, Elementor, and Showit each have different publishing workflows, so the critical check is not the product name: the preview should accurately reproduce templates, scripts, forms, caching, redirects, and mobile behavior.
A WordPress theme preview or a tool such as Theme Switcha may help a team assess an alternate appearance, but the team should verify the rendered result independently. A theme or builder change can affect headings, navigation, image handling, schema output, and JavaScript weight even when page content remains in the CMS.
Before production launch, ensure staging controls do not carry over. Google specifically identifies unintended noindex directives and robots.txt blocks as migration risks. (Google Search Central)
Implement redirects and domain signals correctly
A permanent domain move needs a tested, page-level redirect map. The old URL should return a server-side 301 or 308 and lead directly to the final equivalent URL, which should return a 200 response and declare itself canonical. Avoid chains such as legacy URL → temporary domain → final domain.
The launch plan should include these technical actions:
- Configure 301 or 308 redirects from every mapped legacy URL to its final destination.
- Update canonical elements, internal links, navigation links, XML sitemaps,
hreflangannotations where used, and structured-data URLs. - Verify the preferred HTTPS hostname and ensure non-preferred
wwwor non-wwwvariants resolve consistently. - Update analytics, consent tools, conversion events, email templates, paid campaigns, social profiles, and business directory links.
- Keep the retiring domain registered and redirecting; letting it expire shortly after launch creates an avoidable risk.
- Verify both old and new properties in Google Search Console.
For a whole-domain or subdomain move, use Google Search Console’s Change of Address tool after redirects and verification are in place. Google’s dedicated documentation states that the tool tells Google about a move and helps migrate Search results from the old site to the new one. (Google Search Console Help: Change of Address)
Canonical tags do not replace redirects. A canonical indicates a preferred version among duplicate or very similar URLs; a permanent redirect sends users and crawlers from a retired address to its new location. Both can be correct on the final site, but they solve different problems.
Capture a pre-launch audit baseline
The most useful pre-launch audit records facts that can be compared later. Save crawl exports rather than relying on a single overall health score, because a post-launch issue needs a specific URL, template, or redirect to investigate.
At minimum, capture these six areas across representative templates such as the homepage, service page, location page, article, listing/detail page, and contact page:
- Technical SEO: indexability, status codes, titles, meta descriptions, H1s, canonicals, robots directives, sitemaps, and structured data.
- Links: internal link counts, broken links, redirect chains, orphan pages, and important external destinations. The best broken link checkers compares tools for this part of the inventory.
- Search performance: organic landing pages, clicks, impressions, queries, conversions, and branded versus non-branded traffic.
- Performance: field and lab observations for loading, interaction, and layout stability.
- Accessibility: heading order, form labels, alternative text, contrast, keyboard navigation, focus states, and error messages.
- AI-answer evidence: a fixed set of prompts, engine, date, cited URLs, brand mentions, and answer accuracy.
Core Web Vitals describe real-user loading, interaction responsiveness, and visual stability. Lab tests diagnose a particular run under selected conditions; field data reflects actual user sessions when sufficient data exists. Both are useful, but neither should be substituted for the other. (web.dev)
Use launch-day and post-launch thresholds
A schedule of 24 hours, one week, and later is useful only when each review has pass/fail thresholds and a named escalation action. The thresholds below are operational guardrails, not Google guarantees; acceptable variation depends on seasonality, site size, tracking configuration, and historical performance.
First 24 hours: fix implementation failures
At 24 hours, test 100% of mapped legacy URLs where practical, or a documented representative sample plus every high-value landing page when the map is very large. Escalate immediately if any priority URL returns a 4xx or 5xx response, redirects to an irrelevant page, has a chain longer than one redirect hop, or lands on a page with a staging canonical or noindex directive.
Treat a failure rate above 1% in tested redirects as a launch blocker until investigated. Also escalate if analytics or conversion events record zero data when they normally record activity, if key forms fail, or if a major template produces critical keyboard traps or inaccessible navigation.
One week: identify systematic regressions
At one week, compare crawls and Search Console data. Investigate if more than 2% of previously indexable priority URLs now become non-indexable without an intentional retirement decision, if duplicate title tags affect more than 5% of crawled indexable pages, or if internal links to priority pages decline by 20% or more because a navigation or template element disappeared.
For performance, compare equivalent templates under the same test setup. A regression of 20% or more in a key lab metric, or a new Core Web Vitals problem affecting a major template, warrants engineering review before further redesign work. For accessibility, any new critical issue involving forms, menus, keyboard operation, or focus visibility should be fixed before declaring the migration complete.
Four weeks and beyond: validate outcomes
At four weeks, compare organic landing-page clicks and impressions against the pre-launch baseline using matched dates where possible. Escalate a sustained 20% decline on priority non-branded landing pages when demand, tracking, and seasonality do not explain it. First check redirects, indexing, canonicalization, robots directives, internal links, and content removal before rewriting pages or assuming an algorithmic cause.
This verification-first approach is especially useful when diagnosing a traffic change after launch. Traffic drop diagnosis outlines why teams should separate implementation, measurement, indexing, and demand problems before making reactive SEO changes.
Test AI-answer visibility with a documented example
No site move can guarantee citations or mentions in AI answer engines. Systems may vary their retrieval methods, sources, prompts, and response formats. A migration can, however, preserve the source material that makes a business easy to understand: specific service pages, clear headings, factual local information, current contact details, author or company evidence, and accessible linked resources.
Use the same prompt set before and after launch, record the engine and test date, and save the cited URLs rather than only noting whether the brand name appeared. A small documented example makes the check actionable:
- Pre-launch prompt: “Which real estate agencies help first-time buyers in Austin, Texas?”
- Observed citation: The answer cites
legacyrealty.com/first-time-buyers/and accurately mentions buyer consultations. - Post-launch result: The answer no longer cites the business after that page was redirected to a generic
/buyers/hub. - Corrective action: Create or strengthen
/buyers/first-time-buyers/with the consultation process, local service area, named business details, and relevant internal links; redirect the old URL directly to that page rather than the broad hub.
This does not prove causation or create a fixed AI ranking metric. It gives the team a reproducible record of an observable regression and a page-level remediation path. For client work, AEO audit software for client websites explains the distinction between auditing source pages and monitoring brand mentions over time.
Monitor the new site without relying on one tool
Visual monitoring is helpful for a limited list of important pages after launch. Visualping presents website-change monitoring and alert options, while ChangeTower positions its service around monitoring web-page changes. Their exact plan features, alert destinations, and retention terms can change, so teams should confirm current product documentation before selecting either vendor. (Visualping, ChangeTower)
A visual alert can reveal an altered headline, removed legal notice, or unexpected template change. It may not identify a 302 redirect, a staging canonical, an internal-link collapse, or a blocked resource. Combine monitoring methods:
- Use visual or text monitoring for the homepage, contact page, top landing pages, and critical legal pages.
- Use recurring crawls for status codes, redirects, metadata, canonicals, links, and indexability.
- Use Search Console and analytics for search and conversion outcomes.
- Recheck performance and accessibility after plugin, theme, builder, or navigation changes.
W3C describes accessibility evaluation as an activity that can happen before a redesign, during development, and through periodic monitoring after release. (W3C WAI)
FAQ
How do I change an existing website?
First classify the request: routine content edit, design change, domain move, platform migration, or two-site consolidation. For an ordinary page edit, use a preview or staging workflow and verify the live URL after publishing. For a migration, inventory old URLs, decide which pages survive or merge, implement relevant redirects, and compare technical and user-facing results after launch.
How do I change things on my website without taking it offline?
Prepare the work in a CMS draft, staging environment, preview URL, or branch deployment, then publish during a monitored window with a rollback plan. Chrome DevTools can demonstrate a temporary visual change, but it does not modify the live server. After release, test the real production URL, forms, analytics events, mobile layout, canonical, and page status.
How can I change a website temporarily for testing or previewing?
For a private visual mock-up, use Google Chrome DevTools to edit displayed HTML or CSS; the edits normally disappear on reload. For a review that needs realistic templates, scripts, forms, and rendering, use a protected staging site or preview deployment. Keep unfinished environments out of search results with appropriate access controls and verify no production restrictions persist at launch.
How do I change my website’s domain without breaking links or SEO?
Choose one long-term primary domain, map each meaningful old URL to its closest relevant destination, and use server-side 301 or 308 redirects. Update canonicals, internal links, sitemaps, structured data, analytics, and public business references. Verify both properties in Search Console, use the Change of Address tool for an entire domain move, and investigate redirect or indexing failures immediately.
How do I compare a website before and after major changes?
Create a baseline crawl before launch and record status codes, indexability, titles, canonicals, links, performance, accessibility, landing-page traffic, and a stable set of AI-answer prompts. Re-crawl at 24 hours, one week, and four weeks. Compare specific regressions, such as a 1% redirect failure rate, missing priority URLs, a 20% internal-link decline, or a new inaccessible form, rather than relying only on an aggregate score.
Sources
- https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes
- https://developers.google.com/search/docs/crawling-indexing/301-redirects
- https://support.google.com/webmasters/answer/9370220
- https://developer.chrome.com/docs/devtools/dom/
- https://web.dev/articles/vitals-tools
- https://visualping.io/
- https://changetower.com/
- https://www.w3.org/WAI/test-evaluate/