Guide Site Split and Carve-Out SEO Migration

TL;DR — A site split separates un company’s website into two. The hard partie n’est pas writing redirections. It is deciding who owns every page, domain, account, image, download, lien, and piece of historical données. Garder bon URLs unchanged où vous pouvez. Quand une page really moves, redirection its old URL to the equivalent nouveau page. Si là is aucun replacement, retourner a réel 404 or 410. Tester les deux nouveau estates parce que a carve-out peut break the seller’s site as easily as the buyer’s.

Ce que a site split or carve-out is

A site split is a migration où partie of un 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 nouveau site. A carve-out is one-to-many. Some pages stay with the seller, some déplacer to the buyer, some are copied temporarily sous a license, some are retired, and shared systems have to garder working pendant que ownership changements.

Que creates three jobs:

1. Decide ownership. Who contrôle chaque domain, URL, content asset, account, and service après the transaction?
2. Preserve meaning. Fait the buyer’s nouveau page genuinely replace the seller’s old page pour the utilisateur?
3. Prove independence. Peut chaque side explorer, publish, mesurer, secure, and operate its estate après the transition services fin?

The redirection rule

Redirection a déplacé URL seulement quand the destination is its réel replacement. A product page sold with the business peut usually redirection to the même product on the buyer’s site. A corporate careers page retained by the seller ne doit pas redirection to the buyer’s home page simplement parce que it has liens.

Google advises contre sending nombreux old URLs to un irrelevant destination parce que que may be treated as a soft 404. It recommends server-side redirection permanentes tel as 301 and 308 pour permanent moves. Voir Google’s site-move guidance.

Commencer avant the separation date

Inventory the digital estate pendant que the personnes, systems, and permissions encore 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 Console, analytics, tag management, ad, consent, and business profiles;
• content owners, licenses, authors, trademarks, product données, and source fichiers;
• redirections, canonicals, hreflang, données structurées, sitemaps, and robots rules;
• vendors, APIs, authentication, search, formulaires, and shared repositories.

The contract and counsel determine legal ownership. The SEO team’s job is to expose où a proposed separation dépend on an asset or correct que has pas been assigned.

Ce que success semble comme

Après launch, the buyer’s déplacé pages devrait be crawlable, indexable, internally lié, measurable, and mapped from leur old URLs. The seller’s retained pages devrait encore fonctionner. Historical données and accès devrait be preserved appropriately, pendant que former parties lose operational accès on the agreed schedule.

Que is a successful carve-out. Two sites going live is seulement the visible partie.

TL;DR — Treat a carve-out as an asset-separation program with an SEO migration à l’intérieur it. Construire an entitlement matrix à travers URLs, content, domains, données, liens, accounts, infrastructure, and personnes. Give every legacy URL an explicit disposition: retain, déplacer, consolidate, duplicate temporarily sous documented rights, or retire. Map seulement equivalent moves, preserve shared assets or replace leur références, separate measurement sans discarding history, and sequence cutovers autour DNS, redirections, authentication, consent, and transition-service dependencies. Monitor les deux estates by URL cohort. A buyer-side gain ne fait pas excuse seller-side damage.

Define the separation perimeter

Begin with the transaction perimeter, alors translate it into a digital perimeter. The legal entity, product line, brand, geography, and customer contract may chaque draw the boundary differently. Ne faites pas assume une URL folder is the definitive réponse.

Créer an entitlement matrix with un row per asset and ces fields:

Transition service agreement (TSA) is the deal term worth learning. It defines services un party continues providing temporarily après fermer. Pour le SEO, a TSA may cover redirection hosting, DNS, a CMS, an image CDN, analytics exports, consent tooling, or staff who know how the publishing system fonctionne. Give chaque dependency an owner, service level, fin date, exit tester, and fallback.

Construire an evidence-complete URL inventory

Combine sources plutôt que trusting le sitemap:

• production crawls and CMS/database exports;
• XML sitemaps, server/CDN logs, analytics landing pages, and Search Console pages;
• externally lié URLs, paid landing pages, feeds, and business profiles;
• images, videos, PDFs, downloadable fichiers, JavaScript, CSS, API endpoints, and old redirections.

Google explicitly indique site owners to inclure embedded assets in a déplacer and to utiliser sitemaps, logs, analytics, CMS données, and lien reports to identifier important URLs. The current documentation listes ceux sources.

Assign every URL un disposition:

• Retain: remains at the seller and garde its URL.
• Déplacer: transfers to an equivalent buyer page.
• Consolidate: several pages genuinely become un comprehensive replacement.
• Temporary dual utiliser: apparaît on les deux estates sous documented rights, with an owner and expiry.
• Retire: has aucun utile replacement and renvoie 404/410.
• Hold: ne peut pas launch jusqu’à ownership, rights, or destination is resolved.

Aucun blank cells. “We’ll decide after launch” is a decision to accept an unmanaged échec.

Design mappings autour utilisateur equivalence

The buyer is acquiring a business, pas automatically every search signal attached to the seller. A redirection is justified quand the destination satisfies substantially the même utilisateur intent and continues the même subject, product, or service.

Examiner mappings with content, product, legal, and brand owners. Score chaque row:

• exact successor;
• consolidated but equivalent;
• uncertain and exige manual examiner;
• aucun equivalent, retourner 404/410;
• prohibited parce que the asset or claim ne fait pas transfer.

Éviter chains by resolving old rules directement to the final destination. Google dit it peut follow long chains but recommends direct redirections and keeping unavoidable chains low, ideally aucun plus que three and fewer que five. Garder redirection permanentes pour at least a année and plus long quand practical. Google documents les deux points.

Untangle shared assets and services

Shared dependencies are où carve-outs obtenir weird.

Asset hosts

A déplacé page may encore charger images from the seller’s CDN, fonts from a corporate domain, PDFs from a shared DAM, or JavaScript from a parent-company host. Inventory requêtes from rendered crawls and navigateur/network logs. Pour every dependency, choisir transfer, copy, stable licensed hosting, or replacement. Mettre à jour références and tester cache, CORS, robots rules, signatures, hotlink restrictions, and expiry.

Content and product données

Separate source content from rendered pages. Product descriptions, specifications, reviews, author biographies, localization memory, and structured-data fields may come from systems outside the CMS. Legal and données specialists determine si chaque peut transfer. Ne faites pas solve unclear rights by copying everything.

Identity and transactions

Formulaires, login, account recovery, checkout, subscriptions, and prise en charge portals peut cross the separation boundary. Tester utilisateur journeys and the indexable states autour les. Search visibility n’est pas a win si lune page sends a customer into an account flow the nouveau company ne peut pas operate.

Separate Search Console and measurement safely

Preserve history avant modification accès. Export baseline données by URL cohort, requête, country, device, and search appearance. Record property scope and timezone. Garder a read-only archive in accordance with the transaction’s données rules.

Pour Search Console:

1. Inventory Domain and URL-prefix properties, utilisateurs, owners, and verification méthodes.
2. Vérifier the buyer’s destination properties avant launch.
3. Preserve seller verification nécessaire to monitor old URLs and redirections.
4. Transfer or establish buyer ownership via approved contrôle.
5. Revoke former accès seulement après the agreed monitoring and handoff tests réussir.

Google distinguishes owners, complet utilisateurs, and restricted utilisateurs. Verification tokens peut confer contrôler, so accès design belongs with security plutôt que in a shared SEO spreadsheet. Google documents Search Console permissions.

Pour analytics and tagging, define qui party may retain historical user-level or commercial données. Souvent the safest SEO baseline is an approved aggregate export plus nouveau destination properties, pas copying an entier account. Rebuild events, consent, cross-domain configuration, referrals, channel rules, and business-outcome joins; alors vérifier les with tester transactions.

Sequence the cutover

Utiliser waves fondé on dependencies, pas arbitrary URL counts:

1. Contrôler plane: domain registration, DNS, certificates, CDN, hosting, secrets, account ownership, and monitoring.
2. Destination readiness: templates, content, assets, accessibility, analytics, consent, robots, canonicals, hreflang, schema, and sitemaps.
3. Pilot cohort: a coherent, lower-volatility section whose performances peut be mesuré independently.
4. Principal content: high-value product, category, prise en charge, and editorial cohorts.
5. Long tail and legacy: orphaned pages, fichiers, old redirections, profiles, and integrations.
6. TSA exit: replace or terminate every shared dependency and revoke accès.

Google recommends splitting grand moves quand utile, pendant que warning que a pilot may pas represent a whole-site déplacer. It aussi recommends modification un major variable at a temps and launching during lower trafic où possible. Ceux expectations are in its site-move guidance.

Launch gates

Ne faites pas launch a cohort jusqu’à:

• ownership and rights have a documented state;
• destination pages retourner the intended status and render leur principal content;
• production robots and meta directives autoriser intended exploration and indexation;
• canonicals, hreflang, données structurées, lien internes, and sitemaps utiliser final URLs;
• redirection rules réussir exact, representative, and adversarial tests;
• analytics, consent, conversion, and log collection réussir tester journeys;
• capacity, monitoring, incident ownership, rollback, and communications are ready;
• the seller’s retained estate passes its propre regression suite.

Monitor cohorts, pas blended totals

Créer fixed cohorts avant launch: retained seller URLs, déplacé buyer URLs, retired URLs, shared-transition URLs, and contrôler URLs que ne doit pas modifier. Comparer at 7, 14, 30, and 90 days pendant que accounting pour seasonality and unrelated releases.

Track:

• old URL requêtes and redirection outcomes;
• nouveau URL explorer, index, impressions, clicks, rankings, and conversions;
• seller retained-page regressions;
• server errors, latency, explorer volume, and cache behavior;
• canonical selection, hreflang reciprocity, rich-result eligibility, and lien internes;
• TSA dependencies, expiring credentials, certificate renewal, and unresolved assets.

Ne faites pas promise a fixed recovery date. Google dit significant moves peut fluctuate pendant que URLs are recrawled and reindexed, and que completion se produit per URL. Grand sites peut prendre plus long. Utiliser the attendu transition pattern as context, pas as an excuse pour broken implementation.

Final thoughts

The redirection fichier n’est pas the carve-out plan. The plan is a provable réponse to who owns chaque asset, ce que the utilisateur devrait reach, how chaque company operates independently, and quand every temporary dependency ends.

AI summary

• Treat the carve-out as un estate becoming two, pas as a normal domain swap.
• Inventory URLs, rights, domains, accounts, données, infrastructure, liens, and personnes.
• Assign retain, déplacer, consolidate, temporary dual utiliser, retire, or hold to every URL.
• Redirection seulement to a genuine successor; utiliser 404/410 quand none exists.
• Tester assets and services outside the CMS, surtout CDNs, DAMs, formulaires, identity, product données, consent, and analytics.
• Preserve appropriately scoped history, establish nouveau ownership, and revoke old accès on an agreed schedule.
• Launch by dependency cohort and regression-test the seller’s retained estate.
• Monitor buyer, seller, retired, transition, and unchanged contrôler cohorts separately.

Ce que the official guidance establishes

• Google: site moves with URL changements: mapping, redirection permanentes, assets, staging, sitemaps, monitoring, and troubleshooting.
• Google: redirections and Search: pris en charge redirection méthodes and signal interpretation.
• Google: canonicalization: canonical signals and pourquoi redirections are stronger que annotations alone.
• Google: localized versions: reciprocal hreflang and cross-domain implementations.
• Google: Search Console utilisateurs and permissions: ownership, utilisateur levels, and verification contrôle.

Ces sources expliquer search-system behavior. Ils ne faites pas decide ownership, license, privacy, employment, tax, or transaction terms. Route ceux decisions to specialists.

Quotes from the source

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

Carve-out checklist

Avant design

• Freeze the transaction perimeter and nom unresolved assets.
• Inventory domains, URLs, fichiers, rights, accounts, systems, vendors, and personnes.
• Export crawls, mappings, redirections, GSC, analytics, logs, liens, and rankings.
• Identifier every shared dependency and proposed TSA.
• Créer seller, buyer, retired, transition, and contrôler URL cohorts.

Avant launch

• Assign a disposition and evidence owner to every URL.
• Approve chaque redirection pour utilisateur equivalence and rights.
• Validate assets, formulaires, authentication, consent, analytics, and conversions.
• Vérifier production exploration, canonicals, hreflang, schema, lien internes, and sitemaps.
• Tester rollback and seller-side regressions.
• Staff monitoring and incident réponse.

Après launch

• Explorer every old URL and vérifier the final destination.
• Inspect important URLs in Search Console and comparer index cohorts.
• Monitor logs, errors, latency, trafic, rankings, and outcomes on les deux estates.
• Resolve TSA dependencies avant leur exit dates.
• Revoke accès and rotate secrets après handoff gates réussir.

ROME: rights, ownership, meaning, execution

Utiliser four gates pour every asset:

1. Rights: May the destination company utiliser, modify, host, and redirection it?
2. Ownership: Who contrôle the domain, account, code, content, and renewal?
3. Meaning: Is the proposed destination genuinely equivalent pour the utilisateur?
4. Execution: Peut the destination render, mesurer, secure, and maintain it independently?

A row que fails quelconque gate n’est pas ready to migrate.

Decide ce que se produit to a legacy URL

Launch-day SOP

1. Confirmer the signed URL-map version and owners in the modifier record.
2. Snapshot DNS, CDN, redirection, robots, sitemap, analytics, and certificate state.
3. Release the destination cohort and run smoke tests avant enabling redirections.
4. Enable direct redirections; explorer exact, sampled, unmatched, parameterized, and asset URLs.
5. Validate clé utilisateur journeys and real-time measurement on buyer and seller estates.
6. Submit nouveau sitemaps and inspect representative high-value URLs.
7. Publish the status mettre à jour with incidents, owners, suivant checkpoint, and rollback state.
8. Garder the team disponible jusqu’à the observation window and business tests réussir.

Courant façons carve-outs échouer

• Folder equals ownership: the legal and operating boundary rarely matches un neat directory.
• Traffic-rights logic: valuable trafic ne fait pas prove the buyer owns lune page or may recevoir its redirection.
• Everything to the nouveau homepage: irrelevant redirections confuse utilisateurs and peut be treated as soft 404s.
• Copy now, decide plus tard: temporary duplication becomes permanent, ungoverned content.
• Buyer-only QA: shared-code and redirection changements quietly break the seller.
• TSA as architecture: temporary services expire. Every dependency nécessite an exit.
• Delete old accès immédiatement: monitoring and history disappear avant handoff.
• Jamais revoke old accès: former parties retain contrôler après the approved window.

Outils pour the fonctionner

• SEO Migration Planner & Validator: examiner maps, deployed redirections, old-URL outcomes, sitemap differences, and archived history.
• Redirection Map Builder: suggest and manually examiner URL mappings, preserve unmatched rows, flatten chains, and export rules.
• Robot d’exploration plus rendered-browser explorer: inventory URLs and shared asset requêtes.
• Server/CDN logs: prove bot requêtes, code d’états, redirections, and retained trafic.
• Search Console and analytics exports: establish pre-close cohorts and monitor transfer.
• DNS, certificate, dependency, and secret inventories: prove operational separation.

Tests que doit réussir

Resources

Patrick’s verified fonctionner

• The Role of SEO in Mergers and Acquisitions: due diligence, the merge decision, staged integration, old-brand demand, and post-acquisition monitoring.
• A Webmigration de site Takes Plus Que a Checklist: Patrick’s planning, baseline, URL-change, testing, and monitoring traiter, notamment site splits.

Documentation officielle

• Google’s site-move documentation: URL inventory, mapping, redirection permanentes, phased moves, monitoring, and troubleshooting.
• Google’s Search Console permission model: owners, utilisateurs, verification méthodes, and token removal.
• Bing Webmaster Guidelines: current redirection, explorer/render, and removal guidance.

From autour the industry

• KPMG’s Digital Separation Blueprint: operating-model and transitional-service context pour a carve-out; pas SEO or legal policy.
• 9thCO’s M&A webmigration de site cas study: a vendor-reported multi-domain consolidation exemple.
• Moteur de recherche Land’s migration de site guide: planning, consolidation, launch, and post-launch coverage.
• Screaming Frog’s redirect-audit tutorial: a recoverable workflow pour testing the old-URL définir at scale.

Connexe on ce site: Migration de sites, Website Migration Checklist, and SEO Due Diligence pour M&A.

Testez vos connaissances