SEO

Online store migration without losing traffic: an SEO checklist.

How to move an online store to a new platform, domain or URL structure without losing Google traffic. An SEO checklist for before, during and after launch.

Changing your store platform, domain or URL structure is the moment when it is easiest to lose Google traffic built up over years. I have worked on projects like this in large e-commerce, and each time I saw the same thing: preparation decides the outcome, not launch day itself. Here is a checklist you can work through point by point.

Why stores lose traffic after a migration

Google knows your store under specific URLs. When they change, it has to find the new pages, understand that they replace the old ones and transfer the signals they earned. Traffic usually drops when:

  • old URLs return a 404 instead of a redirect,
  • redirects point to the homepage or unrelated categories,
  • new templates lose content, headings, structured data or internal links,
  • the staging version gets indexed, or production launches with indexing blocked,
  • nobody monitors Search Console during the first weeks.

Before the migration: URL map and staging

1List of old URLsSitemaps, server logs, analytics, Search Console and a platform exportFoundation
2Redirect mapEvery important old URL assigned to its most similar new oneCritical
3Staging reviewContent, templates, structured data, links, speedControl
4BaselineRecord of traffic, rankings and indexed pages before launchMeasurement
Four things worth having ready before the launch date is set.
  1. Collect all old URLs. Not just those in the sitemap. Google recommends also using server logs, analytics and your store system. In stores it often turns out that traffic comes from URLs nobody remembered.
  2. Prepare the redirect map. Category to category, product to product. Removed products to a successor or the closest category. Avoid redirect chains: each old URL should lead straight to its final destination.
  3. Review staging. Do key categories keep the same content and headings, does product structured data work, do internal links point to new URLs, do filters avoid generating thousands of new duplicates? Staging must not be accessible to Google.
  4. Record a baseline. Organic traffic, rankings for key queries and the number of indexed pages before the migration. Without it, it is hard to judge what changed after launch.

Launch day: redirects and sitemaps

MistakeEverything to the homepageBulk-redirecting old URLs to the homepage loses signals and frustrates customers arriving from links and bookmarks.
RightURL to its equivalentPermanent server-side 301 or 308 redirects from every important URL to its closest equivalent.
Google explicitly recommends permanent server-side redirects and advises against pointing many pages to one unrelated page.
  • Switch on 301 or 308 redirects according to the map and check a sample of key URLs right after launch.
  • Remove staging blocks: noindex, password protection, robots.txt disallow. A common and very costly mistake.
  • Update URLs in canonicals, hreflang and internal links so they do not point to redirects.
  • Submit the new sitemap in Search Console. Keep the old one during the move so you can track how Google switches to the new URLs.
  • If you change domain, use the Change of Address tool in Search Console for the old domain.

After the migration: what to monitor in the first weeks

Google warns that rankings may fluctuate temporarily during a move, and that larger sites take longer to switch over. So in the first weeks, check regularly:

  • indexing reports in Search Console: are new URLs getting indexed, and is the number of 404 errors stable,
  • server logs: is Googlebot crawling new URLs without hitting errors,
  • traffic and conversions in GA4 for key categories and products, compared with your baseline,
  • rankings for the most important queries, keeping in mind that short-term fluctuations are normal.

Keep redirects for as long as possible. Google recommends at least a year, and ideally they stay permanently.

The most common store migration mistakes

  • No redirects for products and categories with external links.
  • Changing URLs, content and templates all at once, with no way to tell the impact of each change.
  • Launching at the peak of the sales season.
  • Filters on the new platform generating new duplicates. More on that in faceted navigation and SEO.
  • Nobody responsible for monitoring after launch.

If you are planning a platform change, start with an SEO audit before design decisions are made. To see how I work with stores, visit e-commerce SEO.

Sources

  1. How to move a site (site moves with URL changes) - Google Search Central
  2. Redirects and Google Search - Google Search Central

Was this article helpful?

About the author. Maciek - SEO & GEO consultant with 10+ years of experience, formerly Head of SEO at companies including Gemini Polska and Staples Solutions. More about me

Store migration questions.

How much traffic does a store usually lose in a migration?

There is no single number. A well-prepared migration can go through with small, short-lived fluctuations, while a poorly run one can cost a large share of traffic for months. Google itself warns that rankings may fluctuate temporarily during a move.

How long should redirects stay in place after a migration?

As long as possible. Google recommends at least a year, and for users it is best to keep them indefinitely, because links, bookmarks and search results still point to old URLs.

Can I redirect all old URLs to the homepage?

No. Redirecting many URLs to the homepage or another unrelated page is treated as if there were no equivalent. Each important old URL should lead to the most similar new page, and removed products to a successor or category.

When should an SEO specialist get involved in a migration?

At the planning stage, before decisions on URL structure and templates are made. That is when it is cheapest to avoid mistakes that require costly fixes after launch.