I THE INDEX CLUBApply
Membership ▾
Expertise ▾
Programmes ▾
Proof ▾
Search Notes

THE INDEX CLUB / SEO MIGRATIONS

SEO migration consultancy for high-consequence site launches.

Protect organic rankings, traffic and revenue through a domain move, redesign, replatform, merger or URL restructure.

A migration does not fail on launch day. It fails earlier, when architecture, templates, content and redirect decisions are made without evidence from the site people already find.

The Index Club gives UK brands a senior SEO migration lead who works directly with leadership, designers and developers from planning through post-launch recovery.

Apply to work togetherRead Migration Risk Guide
Pre-Migration Risk Audit URL & Redirect Mapping Post-Launch Safeguards

On this page

Why It Matters

Migration risk is a leadership problem.

Redirect spreadsheets matter. So do architecture, content consolidation, internal linking, and rendering logic. A migration forces trade-offs across design, engineering, brand, and growth.

Good migration SEO makes those trade-offs visible early before they become costly organic losses. Read our article on Migration Risk Is a Leadership Problem.

The migration brief

What is an SEO migration?

An SEO migration is any substantial website change that makes search engines re-crawl, re-evaluate or re-index URLs, content, templates or internal links. The visible launch may take one day; the search transition happens URL by URL over the weeks that follow.

Domain moves and rebrands

Moving to a new domain, TLD, subdomain or brand means transferring authority and verifying every old and new property, redirect and external signal.

CMS and platform migrations

Replatforming to Shopify, WordPress, Webflow, headless or a custom stack can change URL rules, rendering, pagination, canonicals and structured data.

Redesigns and architecture changes

A new design can remove useful content, weaken internal links or alter templates even when the domain stays the same. It still needs migration governance.

URL and content consolidation

Changing folders, slugs, categories or merging duplicate pages requires intent-led mapping so each old URL reaches a genuinely relevant successor.

International and ecommerce changes

Locale moves, hreflang changes, product and category migrations, faceted navigation and discontinued stock add indexing and commercial risk.

Hosting, protocol and rendering moves

HTTPS, CDN, server, JavaScript or rendering changes can affect crawl capacity, page delivery and what search engines can actually see.

The riskiest projects stack several changes together. A new domain, CMS, design and URL structure in one release is not one migration. It is four overlapping migrations with one launch date. Where possible, we reduce or phase that risk.

Consultancy scope

What SEO migration consultancy includes.

01

Pre-migration risk review

Inventory URLs, templates, rankings, traffic, conversions, backlinks and indexation so the team knows exactly what must survive the move.

02

URL and redirect strategy

Map every valuable old URL to its closest relevant destination, with explicit decisions for consolidation, removal, 301s and genuine 404 or 410 responses.

03

Staging checks

Crawl and compare staging for indexability, canonicals, hreflang, structured data, internal links, rendering, analytics and template parity.

04

Launch monitoring

Run the go-live checklist, validate priority URLs and redirects, submit the right sitemaps, and watch crawl, indexation, traffic and revenue signals.

05

Stakeholder reporting

Turn crawl data and ranking movement into a clear risk register, launch decision and executive view of commercial impact.

06

Recovery support

Diagnose redirect gaps, crawl blocks, canonical conflicts, rendering failures, lost internal links and content regressions, then sequence fixes by revenue risk.

Migration process

How a website migration is sequenced.

Step 01

Pre-Migration Audit & Benchmarking

Combine crawl data, XML sitemaps, Search Console, analytics, backlinks and CMS exports into one URL inventory. Baseline rankings, traffic, conversions and indexed coverage before change begins.

Step 02

Architecture & Redirect Mapping

Review the proposed information architecture and page inventory. Define which URLs stay, merge, move or retire, then specify redirects, canonicals, hreflang and internal-link updates.

Step 03

Staging QA & Testing

Crawl staging against the baseline and acceptance criteria. Test templates, rendering, metadata, schema, robots controls, sitemaps, analytics, consent, forms and Core Web Vitals.

Step 04

Launch Day Command & Monitoring

Own the SEO launch runbook: remove staging blocks, activate and sample redirects, test priority journeys, confirm tracking, submit sitemaps and use Change of Address when a domain changes.

Step 05

Post-Launch Index Recalibration

Monitor old and new URLs as Google recrawls the move. Triage 404s, soft 404s, redirect chains, canonical drift, indexing gaps and losses by page type, query and commercial value.

Failure modes

What actually breaks SEO during a migration?

Traffic loss is rarely caused by the idea of migrating. It comes from specific implementation and decision failures that can be found before launch or diagnosed quickly afterwards.

Valuable old URLs disappear

Pages found in Search Console, analytics, backlinks or logs are missing from the crawl-led inventory, so they launch as 404s or fall into a generic homepage redirect.

Staging controls reach production

A site goes live with noindex directives, blocked resources, the wrong robots.txt, password protection or canonicals still pointing to staging.

The new page is not equivalent

A technically correct 301 cannot compensate for a destination that removed the content, intent, products or information that earned the old page's visibility.

Internal authority vanishes

Navigation, breadcrumbs, related links, pagination or contextual links change, leaving important pages deeper, weaker or effectively orphaned.

Search signals reset or conflict

Canonical tags, hreflang clusters, metadata, structured data, XML sitemaps or status codes disagree about which URLs should be indexed.

Rendering and capacity are overlooked

Key content is missing from rendered HTML, JavaScript fails, performance regresses or the new infrastructure cannot absorb the heavier crawl activity that follows a move.

A launch date is not a reason to launch. Priority redirects, production robots rules, canonical templates, analytics, sitemaps and critical user journeys should have named acceptance checks. If a high-consequence control is red, the team needs an explicit decision to delay, phase or roll back.

Sometimes the right advice is not to migrate yet. If the commercial upside is unclear, the new site is not testable, or several major changes can be separated, reducing the blast radius is often the best SEO decision.

The load-bearing work

URL mapping is a decision system, not a spreadsheet exercise.

The redirect map is where search equity, user intent and the new information architecture meet. Every known old URL needs an evidence-based outcome before launch.

Keep

Retain the URL where it is still the right answer. Preserve useful copy, metadata, headings, structured data and internal links rather than rebuilding a weaker version.

Move

Use a server-side permanent redirect to the closest equivalent new URL. Point directly to the final destination and remove chains, loops and unnecessary hops.

Merge

Consolidate overlapping pages only when the destination satisfies the same intent and contains enough information to replace them. Several relevant pages can legitimately resolve to one stronger page.

Retire

Return a genuine 404 or 410 when content has no useful replacement. Redirecting unrelated pages to the homepage creates poor journeys and can be treated as a soft 404.

Update every signal

Replace old internal links and update canonicals, hreflang, XML sitemaps, structured data, image and PDF references, campaign links and high-value external links.

How the inventory is built: crawl data alone is never enough. We reconcile the crawl with XML sitemaps, Search Console pages, analytics landing pages, backlink destinations, CMS exports, server logs and paid campaign URLs so valuable orphaned pages are not silently lost.

The working checklist

SEO migration checklist: before, during and after launch.

A useful checklist names the evidence, the owner and the acceptance condition. These are the controls we adapt to the scale and risk of the move.

01 / Before launch

Establish what must survive

  • Set migration goals, risk owners, go or no-go criteria and a rollback route.
  • Archive crawls and benchmark traffic, conversions, rankings, backlinks and indexed coverage.
  • Inventory URLs, templates, content, metadata, canonicals, hreflang, schema, media and internal links.
  • Review the proposed architecture before navigation, templates and copy are locked.
  • Complete the old-to-new URL map and have redirect rules ready in the production format.
  • Crawl staging and compare it with the old site by template and priority URL.
  • Verify analytics, consent, forms, Search Console properties, XML sitemaps and production robots rules.
02 / Launch day

Control the cutover

  • Freeze avoidable content and development changes before release.
  • Remove temporary noindex directives and crawl blocks from production.
  • Activate redirects and test priority URLs, templates and user journeys.
  • Confirm new URLs return 200, old URLs return the planned 301, and retired URLs return the intended status.
  • Check canonicals, hreflang, structured data, internal links and rendering on the live site.
  • Validate analytics and conversion events in real time.
  • Submit the new sitemap and use Search Console Change of Address for eligible domain moves.
03 / After launch

Watch the transfer happen

  • Crawl both old and new URL sets and compare outcomes with the approved map.
  • Monitor 404s, soft 404s, redirect chains, indexation, sitemap processing and canonical selection.
  • Track organic sessions, conversions and rankings by page type, query group and device.
  • Use server logs on larger sites to confirm how search crawlers are discovering the move.
  • Update important external links, profiles, paid campaigns and owned references.
  • Keep permanent redirects for at least a year; for users and legacy links, longer is usually better.
  • Document fixes and close the migration only when priority signals have stabilised.
What you receive

The artefacts that keep teams aligned

  • Risk register and migration acceptance criteria.
  • Evidence-backed URL inventory and priority-page set.
  • Redirect map with keep, move, merge and retire decisions.
  • Staging comparison and technical QA report.
  • Named launch runbook, checks and escalation route.
  • Post-launch monitoring view and concise leadership reporting.
  • Prioritised recovery plan when a previous launch has already lost visibility.

Timing: involve SEO before the information architecture and templates are final. Smaller migrations may need a short runway; large ecommerce, international or multi-domain moves need longer. The right start date is set by the number of decisions still open, not a generic week count.

FAQ

SEO migration FAQs.

When should SEO join a site migration?

As early as possible. SEO should be involved during wireframing, architecture planning, and platform evaluation—not a week before launch.

Do redirects solve migration risk?

Redirects are essential, but they are only one part. Changes to page layout, internal linking, site architecture, and rendering also impact rankings.

Can you help after a migration has gone wrong?

Yes. Recovery work starts by isolating whether losses stem from redirect gaps, canonical errors, rendering bugs, or content drops.

Do you work with agencies and developers?

Yes. Migration work often means sitting between internal teams, design agencies, and development partners to align technical priorities.

What is an SEO migration?

It is the process of preserving and transferring organic search signals when a website changes domain, platform, URL structure, design, content architecture, protocol, hosting or rendering setup.

Will rankings drop after a website migration?

Some short-term fluctuation can happen while search engines recrawl and reindex changed URLs. A lasting loss is not an unavoidable migration tax: it usually points to missing redirects, changed content, weaker internal links, crawl blocks or technical defects.

How long does an SEO migration take?

The answer depends on site size, migration type and how many decisions are still open. Planning starts before architecture and templates are fixed; monitoring continues until priority URLs, rankings and conversions have stabilised after launch.

How long should migration redirects stay live?

Google recommends keeping permanent redirects for at least one year so its systems can transfer signals. Keeping useful legacy redirects for longer protects visitors and links that may continue to use old URLs.

Does every old URL need a redirect?

Every known URL needs a decision, but not every URL deserves a redirect. Use a relevant permanent redirect when a true successor exists; return a genuine 404 or 410 when content has been retired without an equivalent.

Should a complex migration be phased?

Sometimes. Separating a domain move, replatform, redesign and content restructure can reduce the number of variables in play. Larger sites may also migrate by section when that improves monitoring and control.

Next Step

Protect your organic revenue before the migration goes live.

The Index Club works with a maximum of 10 active brand memberships at any one time.

Explore related capabilities: Technical SEO | AI Search | SEO Consultancy | Case Studies | Warren Hance.

Apply to work togetherStart with an Index Review

THE INDEX CLUB

Senior search strategy without agency theatre for ambitious UK brands.

warren@theindexclub.co.uk
MembershipSearch MembershipIndex ReviewFounding MembersMembers' BoardApply
ExpertiseSEO ConsultancySEO Freelancer UKTechnical SEOSEO MigrationsAI Search
ProgrammesSEO for CharitiesSEO for Startups
Proof & NotesCase StudiesWarren HanceAboutPrinciplesSearch Notes
© 2026 The Index Club · UK-first search membership