Upgrade to Pro — share decks privately, control downloads, hide ads and more …

SEO for M&A Migrations: Moving Large Sites at S...

SEO for M&A Migrations: Moving Large Sites at Scale “Without” Losing Visibility

Lightning talk at Google Search Central Live Deep Dive Europe 2026, Barcelona (1 October 2026).

When one company buys another, the acquired website has to fit into the buyer's site. The redirects are the easy part. This talk is about the part that decides whether the migration works: the map, the list of every old URL and where it goes on launch day, and the decisions behind each row.

Three parts: what to settle before you map a single redirect (negotiate, clean house, rank by business, warm the destination, set expectations); how to turn every row of the map into a decision with a name on it, and how to do that at scale with a similarity score that proposes but doesn't decide; and the three checks after launch that a 200 OK can't tell you: route, answer, enquiry.

Data point: median recovery after a domain migration is 304 days (SALT.agency, 1,052 migrations, June 2026). The illustrative row shown on stage is an example; the context and decisions come from a real acquisition project.

The full M&A migration guide, with the process checklist, the mapping template and the scripts, is at https://drive.google.com/drive/folders/1bqmdZF2BzKsPbal1MmkD6e41V0JHt8pT?usp=drive_link.

David Carrasco Pamies, SEO consultant and founder of Magnify, Barcelona. magnify.ing · linkedin.com/in/david-carrasco-pamies

Avatar for David Carrasco

David Carrasco

October 05, 2026

More Decks by David Carrasco

Other Decks in Marketing & SEO

Transcript

  1. Search Central Live Deep Dive 2026 Lightning Talk SEO for

    M&A Migrations: Moving Large Sites at Scale “Without” Losing Visibility David Carrasco Pamies SEO Consultant | Founder @ Magnify
  2. Before you map a single redirect 01 Negotiate 02 03

    04 Clean house Rank by business Warm the destination
  3. Can I work offline? Old URL /offline-crm/ Approved destination /sales/offline/

    Must survive Offline answer + demo request Approval Product lead Acceptance Answer present + lead received