Replatform Without Losing SEO: A Technical Migration Guide

Changing platforms is one of the most nerve-wracking things a store can do, and for good reason. The horror stories are real: a business moves to a shiny new platform, the launch looks great, and then over the following weeks the organic traffic quietly falls off a cliff, taking a chunk of revenue with it. The rankings that took years to earn evaporate, not because the new store is worse, but because the migration broke the trail search engines had been following.

The reassuring part is that this is almost entirely preventable. Lost-traffic replatforms are not bad luck, they are missing redirects and dropped metadata, and both are avoidable with a methodical plan. This guide is that plan: how to move platforms while keeping your search rankings intact. The examples assume a Next.js or Vercel target, and the principles apply to any move.

Search engines rank specific URLs, and they have built up trust in yours over time. A replatform usually changes the URL structure, so unless you tell search engines where each page went, every ranking URL suddenly returns a 404 or lands somewhere unexpected. On top of that, teams often lose the page titles, descriptions, and structured data that helped those pages rank, and sometimes launch a slower site or accidentally leave a "do not index" setting on from staging. Any one of these dents traffic, and together they cause the cliff.

The single most important task is that every old URL keeps working. Where you can keep the same URL, do. Where the URL has to change, send a permanent redirect from the old address to the new equivalent, so both visitors and search engines are passed seamlessly to the right page and the ranking authority transfers with them.

// every old URL maps to its new home with a permanent 301
const redirects: Record<string, string> = {
  "/old-product-slug": "/products/new-slug",
  "/category/widgets": "/collections/widgets",
};

export function middleware(req: Request) {
  const to = redirects[new URL(req.url).pathname];
  if (to) return NextResponse.redirect(new URL(to, req.url), 301);   // 301 = permanent
}

You cannot redirect URLs you do not know about, so inventory them first. Pull your complete list of live URLs from every source you have, the existing sitemap, your analytics, Google Search Console, and a full crawl of the current site, then map each one to its destination on the new platform. The goal is zero orphans: every old URL that has traffic or rankings points somewhere sensible. This map is the backbone of the migration, and it should exist and be reviewed before launch, not scrambled together afterward.

Use permanent (301) redirects, not temporary (302) ones, because only permanent redirects tell search engines to move the ranking to the new URL. Avoid redirect chains, where one URL hops to another and then another, since each hop loses a little and slows the page, so map each old URL directly to its final destination in a single step. And do not redirect everything to the homepage, a lazy catch-all that throws away the specific relevance each page had, send each URL to its true equivalent.

A page is more than its address. Carry over the things that helped it rank: the title, the meta description, the heading structure, the image alt text, and any structured data, and set the canonical URL correctly on the new page. Treat the old metadata as proven and do not casually rewrite it during the move.

// carry the proven title and description to the new page, do not regress them
export const metadata = {
  title: product.seoTitle,
  description: product.seoDescription,
  alternates: { canonical: `https://store.com/products/${product.slug}` },
};

Two self-inflicted wounds are common at launch. First, leaving a staging "noindex" or a robots.txt that blocks crawlers, which makes your whole new store invisible, so check that the production site is actually indexable. Second, launching slower than the old site, which hurts both rankings and conversion, so make sure the new store is fast on day one. Then submit the new sitemap so search engines discover the new structure quickly.

A small temporary dip after a migration is normal as search engines re-crawl and re-evaluate. What matters is catching real problems fast. After launch, watch Search Console for coverage errors and a spike in 404s, confirm your redirects are firing, and keep an eye on rankings for your important pages. Most migration damage that becomes permanent does so because nobody was watching in the first two weeks, so the monitoring is part of the job, not an afterthought.

• Inventory every live URL from the sitemap, analytics, Search Console, and a full crawl.
• Map each old URL to its true new equivalent, with zero orphans.
• Use single-hop 301 redirects, never 302s, chains, or a catch-all to the homepage.
• Preserve titles, descriptions, headings, alt text, structured data, and canonicals.
• Confirm the production site is indexable, no leftover noindex or blocking robots rules.
• Launch at least as fast as the old site, then submit the new sitemap.
• Watch Search Console for 404s, coverage, and rankings, and fix issues fast.

Why do stores lose traffic when they change platforms?

Because the migration breaks the trail search engines follow. Replatforming usually changes URLs, so without redirects the ranked pages return 404s or land in the wrong place, and the authority they built is lost. Teams also commonly drop the titles, descriptions, and structured data that helped pages rank, launch a slower site, or leave a staging noindex on. Each hurts traffic, and together they cause the post-launch cliff, all of it preventable with a plan.

What is the most important step in an SEO-safe migration?

Making sure every old URL keeps working. Preserve URLs where you can, and where they must change, send a permanent 301 redirect from the old address to the exact new equivalent so visitors and search engines are passed through and the ranking transfers. This rests on building a complete map of your existing URLs before launch, from your sitemap, analytics, Search Console, and a crawl, so nothing is left to 404.

What is the difference between a 301 and a 302 redirect, and which should I use?

A 301 is a permanent redirect and a 302 is temporary. For a replatform you want 301s, because only a permanent redirect tells search engines the page has truly moved and instructs them to transfer the ranking to the new URL. A 302 signals the move is temporary, so engines may keep the old URL indexed and not pass authority along. Use 301s, and map each URL directly to its destination to avoid lossy redirect chains.

Will my rankings drop after migrating?

Expect a small, temporary dip as search engines re-crawl and re-evaluate the new site, even when everything is done correctly. With proper redirects, preserved metadata, a fast indexable launch, and a fresh sitemap, rankings typically recover within a few weeks. Lasting drops come from missing redirects, lost on-page SEO, or an accidental noindex, and from nobody monitoring after launch, which is why watching Search Console closely in the first two weeks matters.

Should I just redirect all old pages to the homepage?

No, that is one of the most damaging shortcuts. Redirecting everything to the homepage throws away the specific relevance each page earned, and search engines often treat such redirects as soft 404s, so the rankings vanish anyway. Map each old URL to its true equivalent, a product to the matching product, a category to the matching category, so the authority and relevance carry over to the right place on the new store.

If you are planning a platform move and want to keep the traffic you have worked for, tell me where you are now and where you are headed and I will map out a migration that protects your rankings.