Site Split and Carve-Out SEO Migration

TL;DR — A site split separates one company’s website into two. The hard part is not writing redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't.. It is deciding who owns every page, domain, account, image, download, link, and piece of historical data. Keep good URLs unchanged where you can. When a page really moves, redirect its old URL to the equivalent new page. If there is no replacement, return a real 404 or 410. Test both new estates because a carve-out can break the seller’s site as easily as the buyer’s.

What a site split or carve-out is

A site split is a migration where part of one website becomes a separate digital estate. It commonly follows a divestiture, spin-off, product sale, regional separation, or joint-venture unwind.

A normal domain migration is mostly one-to-one: the old site moves to the new site. A carve-out is one-to-many. Some pages stay with the seller, some move to the buyer, some are copied temporarily under a license, some are retired, and shared systems have to keep working while ownership changes.

That creates three jobs:

1. Decide ownership. Who controls each domain, URL, content asset, account, and service after the transaction?
2. Preserve meaning. Does the buyer’s new page genuinely replace the seller’s old page for the user?
3. Prove independence. Can each side crawl, publish, measure, secure, and operate its estate after the transition services end?

The redirect rule

Redirect a moved URL only when the destination is its real replacement. A product page sold with the business can usually redirect to the same product on the buyer’s site. A corporate careers page retained by the seller should not redirect to the buyer’s home page just because it has links.

Google advises against sending many old URLs to one irrelevant destination because that may be treated as a soft 404A soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing.. It recommends server-side permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. such as 301 and 308 for permanent moves. See Google’s site-move guidance.

Start before the separation date

Inventory the digital estate while the people, systems, and permissions still exist. At minimum, capture:

• domains, subdomains, old domains, DNS, certificates, hosting, and CDN rules;
• every indexable URL plus images, videos, PDFs, scripts, and feeds;
• Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., analytics, tag management, ad, consent, and business profiles;
• content owners, licenses, authors, trademarks, product data, and source files;
• redirects, canonicals, hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and robots rules;
• vendors, APIs, authentication, search, forms, and shared repositories.

The contract and counsel determine legal ownership. The SEO team’s job is to expose where a proposed separation depends on an asset or right that has not been assigned.

What success looks like

After launch, the buyer’s moved pages should be crawlable, indexable, internally linked, measurable, and mapped from their old URLs. The seller’s retained pages should still work. Historical data and access should be preserved appropriately, while former parties lose operational access on the agreed schedule.

That is a successful carve-out. Two sites going live is only the visible part.

TL;DR — Treat a carve-out as an asset-separation program with an SEO migrationA site migration is any significant change to a website's URL structure, domain, platform, protocol, or hosting that can affect how search engines crawl, index, and rank it. The risk scales with how much you change at once. inside it. Build an entitlement matrix across URLs, content, domains, data, links, accounts, infrastructure, and people. Give every legacy URL an explicit disposition: retain, move, consolidate, duplicate temporarily under documented rights, or retire. Map only equivalent moves, preserve shared assets or replace their references, separate measurement without discarding history, and sequence cutovers around DNS, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., authentication, consent, and transition-service dependencies. Monitor both estates by URL cohort. A buyer-side gain does not excuse seller-side damage.

Define the separation perimeter

Begin with the transaction perimeter, then translate it into a digital perimeter. The legal entity, product line, brand, geography, and customer contract may each draw the boundary differently. Do not assume a URL folder is the definitive answer.

Create an entitlement matrix with one row per asset and these fields:

Transition service agreement (TSA) is the deal term worth learning. It defines services one party continues providing temporarily after close. For SEO, a TSA may cover redirect hosting, DNS, a CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms., an image CDN, analytics exports, consent tooling, or staff who know how the publishing system works. Give each dependency an owner, service level, end date, exit test, and fallback.

Build an evidence-complete URL inventory

Combine sources rather than trusting the sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.:

• production crawls and CMS/database exports;
• XML sitemapsAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags., server/CDN logs, analytics landing pages, and Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. pages;
• externally linked URLs, paid landing pages, feeds, and business profiles;
• images, videos, PDFs, downloadable files, JavaScript, CSS, API endpoints, and old redirects.

Google explicitly tells site owners to include embedded assets in a move and to use sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., logs, analytics, CMS data, and link reports to identify important URLs. The current documentation lists those sources.

Assign every URL one disposition:

• Retain: remains at the seller and keeps its URL.
• Move: transfers to an equivalent buyer page.
• Consolidate: several pages genuinely become one comprehensive replacement.
• Temporary dual use: appears on both estates under documented rights, with an owner and expiry.
• Retire: has no useful replacement and returns 404/410.
• Hold: cannot launch until ownership, rights, or destination is resolved.

No blank cells. “We’ll decide after launch” is a decision to accept an unmanaged failure.

Design mappings around user equivalence

The buyer is acquiring a business, not automatically every search signal attached to the seller. A redirect is justified when the destination satisfies substantially the same user intent and continues the same subject, product, or service.

Review mappings with content, product, legal, and brand owners. Score each row:

• exact successor;
• consolidated but equivalent;
• uncertain and requires manual review;
• no equivalent, return 404/410;
• prohibited because the asset or claim does not transfer.

Avoid chains by resolving old rules directly to the final destination. Google says it can follow long chains but recommends direct redirects and keeping unavoidable chains low, ideally no more than three and fewer than five. Keep permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. for at least a year and longer when practical. Google documents both points.

Untangle shared assets and services

Shared dependencies are where carve-outs get weird.

Asset hosts

A moved page may still load images from the seller’s CDN, fonts from a corporate domain, PDFs from a shared DAM, or JavaScript from a parent-company host. Inventory requests from rendered crawls and browser/network logs. For every dependency, choose transfer, copy, stable licensed hosting, or replacement. Update references and test cache, CORS, robots rules, signatures, hotlink restrictions, and expiry.

Content and product data

Separate source content from rendered pages. Product descriptions, specifications, reviews, author biographies, localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. memory, and structured-data fields may come from systems outside the CMS. Legal and data specialists determine whether each can transfer. Do not solve unclear rights by copying everything.

Identity and transactions

Forms, login, account recovery, checkout, subscriptions, and support portals can cross the separation boundary. Test user journeys and the indexable states around them. Search visibility is not a win if the page sends a customer into an account flow the new company cannot operate.

Separate Search Console and measurement safely

Preserve history before changing access. Export baseline data by URL cohort, query, country, device, and search appearance. Record property scope and timezone. Keep a read-only archive in accordance with the transaction’s data rules.

For Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.:

1. Inventory Domain and URL-prefix properties, users, owners, and verification methods.
2. Verify the buyer’s destination properties before launch.
3. Preserve seller verification needed to monitor old URLs and redirects.
4. Transfer or establish buyer ownership through approved controls.
5. Revoke former access only after the agreed monitoring and handoff tests pass.

Google distinguishes owners, full users, and restricted users. Verification tokensA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. can confer control, so access design belongs with security rather than in a shared SEO spreadsheet. Google documents Search Console permissions.

For analytics and tagging, define which party may retain historical user-level or commercial data. Often the safest SEO baseline is an approved aggregate export plus new destination properties, not copying an entire account. Rebuild events, consent, cross-domain configuration, referrals, channel rules, and business-outcome joins; then verify them with test transactions.

Sequence the cutover

Use waves based on dependencies, not arbitrary URL counts:

1. Control plane: domain registration, DNS, certificates, CDN, hosting, secrets, account ownership, and monitoring.
2. Destination readiness: templates, content, assets, accessibilityWeb accessibility means designing sites so people with disabilities can use them, per the W3C's WCAG guidelines. It overlaps with SEO in specific, checkable ways — alt text, heading structure, descriptive link text, captions, and page speed all serve both audiences — but Google has said accessibility itself is not a ranking factor, and most WCAG success criteria (keyboard focus order, ARIA live regions, form labels) have no SEO effect at all., analytics, consent, robots, canonicals, hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., schema, and sitemaps.
3. Pilot cohort: a coherent, lower-volatility section whose performance can be measured independently.
4. Primary content: high-value product, category, support, and editorial cohorts.
5. Long tail and legacy: orphaned pages, files, old redirects, profiles, and integrations.
6. TSA exit: replace or terminate every shared dependency and revoke access.

Google recommends splitting large moves when useful, while warning that a pilot may not represent a whole-site move. It also recommends changing one major variable at a time and launching during lower traffic where possible. Those expectations are in its site-move guidance.

Launch gates

Do not launch a cohort until:

• ownership and rights have a documented state;
• destination pages return the intended status and render their main content;
• production robots and meta directives allow intended crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. and indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.;
• canonicals, hreflang, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., and sitemaps use final URLs;
• redirect rules pass exact, representative, and adversarial tests;
• analytics, consent, conversion, and log collection pass test journeys;
• capacity, monitoring, incident ownership, rollback, and communications are ready;
• the seller’s retained estate passes its own regression suite.

Monitor cohorts, not blended totals

Create fixed cohorts before launch: retained seller URLs, moved buyer URLs, retired URLs, shared-transition URLs, and control URLs that should not change. Compare at 7, 14, 30, and 90 days while accounting for seasonality and unrelated releases.

Track:

• old URL requests and redirect outcomes;
• new URL crawl, index, impressions, clicks, rankings, and conversions;
• seller retained-page regressions;
• server errors, latency, crawl volume, and cache behavior;
• canonical selection, hreflang reciprocity, rich-result eligibility, and internal links;
• TSA dependencies, expiring credentials, certificate renewal, and unresolved assets.

Do not promise a fixed recovery date. Google says significant moves can fluctuate while URLs are recrawled and reindexed, and that completion happens per URL. Large sites can take longer. Use the expected transition pattern as context, not as an excuse for broken implementation.

Final thoughts

The redirect file is not the carve-out plan. The plan is a provable answer to who owns each asset, what the user should reach, how each company operates independently, and when every temporary dependency ends.

AI summary

• Treat the carve-out as one estate becoming two, not as a normal domain swap.
• Inventory URLs, rights, domains, accounts, data, infrastructure, links, and people.
• Assign retain, move, consolidate, temporary dual use, retire, or hold to every URL.
• RedirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. only to a genuine successor; use 404/410 when none exists.
• Test assets and services outside the CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms., especially CDNs, DAMs, forms, identity, product data, consent, and analytics.
• Preserve appropriately scoped history, establish new ownership, and revoke old access on an agreed schedule.
• Launch by dependency cohort and regression-test the seller’s retained estate.
• Monitor buyer, seller, retired, transition, and unchanged control cohorts separately.

What the official guidance establishes

• Google: site moves with URL changes: mapping, permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank., assets, staging, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., monitoring, and troubleshooting.
• Google: redirects and Search: supported redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. methods and signal interpretation.
• Google: canonicalization: canonical signals and why redirects are stronger than annotations alone.
• Google: localized versions: reciprocal hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. and cross-domain implementations.
• Google: Search Console users and permissions: ownership, user levels, and verification controls.

These sources explain search-system behavior. They do not decide ownership, license, privacy, employment, tax, or transaction terms. Route those decisions to specialists.

Quotes from the source

• “Split your move into smaller steps, if that makes sense for your site.” Google Search Central. Jump to quote

Carve-out checklist

Before design

• Freeze the transaction perimeter and name unresolved assets.
• Inventory domains, URLs, files, rights, accounts, systems, vendors, and people.
• Export crawls, mappings, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., analytics, logs, links, and rankings.
• Identify every shared dependency and proposed TSA.
• Create seller, buyer, retired, transition, and control URL cohorts.

Before launch

• Assign a disposition and evidence owner to every URL.
• Approve each redirect for user equivalence and rights.
• Validate assets, forms, authentication, consent, analytics, and conversions.
• Verify production crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., canonicals, hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., schema, internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., and sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing..
• Test rollback and seller-side regressions.
• Staff monitoring and incident response.

After launch

• Crawl every old URL and verify the final destination.
• Inspect important URLs in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. and compare indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. cohorts.
• Monitor logs, errors, latency, traffic, rankings, and outcomes on both estates.
• Resolve TSA dependencies before their exit dates.
• Revoke access and rotate secrets after handoff gates pass.

ROME: rights, ownership, meaning, execution

Use four gates for every asset:

1. Rights: May the destination company use, modify, host, and redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. it?
2. Ownership: Who controls the domain, account, code, content, and renewal?
3. Meaning: Is the proposed destination genuinely equivalent for the user?
4. Execution: Can the destination render, measure, secure, and maintain it independently?

A row that fails any gate is not ready to migrate.

Decide what happens to a legacy URL

Launch-day SOP

1. Confirm the signed URL-map version and owners in the change record.
2. Snapshot DNS, CDN, redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., robots, sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., analytics, and certificate state.
3. Release the destination cohort and run smoke tests before enabling redirects.
4. Enable direct redirects; crawl exact, sampled, unmatched, parameterized, and asset URLs.
5. Validate key user journeys and real-time measurement on buyer and seller estates.
6. Submit new sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. and inspect representative high-value URLs.
7. Publish the status update with incidents, owners, next checkpoint, and rollback state.
8. Keep the team available until the observation window and business tests pass.

Common ways carve-outs fail

• Folder equals ownership: the legal and operating boundary rarely matches one neat directory.
• Traffic-rights logic: valuable traffic does not prove the buyer owns the page or may receive its redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't..
• Everything to the new homepage: irrelevant redirects confuse users and can be treated as soft 404sA soft 404 is a URL that returns a success status code (usually 200 OK) even though the page is empty, missing, or shows a 'not found' message. It isn't a status code a server sends — it's a label search engines apply after comparing the response code against the rendered content, and they treat the page like a 404 for indexing..
• Copy now, decide later: temporary duplication becomes permanent, ungoverned content.
• Buyer-only QA: shared-code and redirect changes quietly break the seller.
• TSA as architecture: temporary services expire. Every dependency needs an exit.
• Delete old access immediately: monitoring and history disappear before handoff.
• Never revoke old access: former parties retain control after the approved window.

Tools for the work

• SEO Migration Planner & Validator: review maps, deployed redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., old-URL outcomes, sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. differences, and archived history.
• Redirect Map Builder: suggest and manually review URL mappings, preserve unmatched rows, flatten chains, and export rules.
• CrawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. plus rendered-browser crawl: inventory URLs and shared asset requests.
• Server/CDN logs: prove bot requests, status codes, redirects, and retained traffic.
• Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and analytics exports: establish pre-close cohorts and monitor transfer.
• DNS, certificate, dependency, and secret inventories: prove operational separation.

Tests that must pass

Resources

Patrick’s verified work

• The Role of SEO in Mergers and Acquisitions: due diligence, the merge decision, staged integration, old-brand demand, and post-acquisition monitoring.
• A Website Migration Takes More Than a Checklist: Patrick’s planning, baseline, URL-change, testing, and monitoring process, including site splits.

Official documentation

• Google’s site-move documentation: URL inventory, mapping, permanent redirectsA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank., phased moves, monitoring, and troubleshooting.
• Google’s Search Console permission model: owners, users, verification methods, and tokenA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. removal.
• Bing Webmaster Guidelines: current redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., crawl/render, and removal guidance.

From around the industry

• KPMG’s Digital Separation Blueprint: operating-model and transitional-service context for a carve-out; not SEO or legal policy.
• 9thCO’s M&A website migration case study: a vendor-reported multi-domain consolidation example.
• Search Engine Land’s site migration guide: planning, consolidation, launch, and post-launch coverage.
• Screaming Frog’s redirect-audit tutorial: a recoverable workflow for testing the old-URL set at scale.

Related on this site: Site MigrationsA site migration is any significant change to a website's URL structure, domain, platform, protocol, or hosting that can affect how search engines crawl, index, and rank it. The risk scales with how much you change at once., Website Migration Checklist, and SEO Due Diligence for M&A.

Test yourself