Insights lesenGespräch

Relaunch

New doesn't mean better.

Ecommerce Website Relaunch Without Losing Traffic or Sales

A new store is supposed to improve everything. Without careful planning, it often loses in the first few weeks exactly what the old one did well.

4 min read

Key takeaways

  • A relaunch is one of the riskiest ecommerce projects, with search visibility, conversion and stability all at stake.
  • What works in the old store has to be measured before the rebuild and deliberately carried over.
  • Buffers, testing and a clean redirect strategy decide how the first weeks go.
Contents

A relaunch raises big expectations: new design, better technology, faster processes. On launch day, everyone is delighted. A few weeks later the questions start: Why is organic traffic dropping? Why are fewer visitors buying? Why does the checkout crash from time to time?

A relaunch is one of the riskiest projects in ecommerce. Many stores lose Google visibility, conversion rate and stability afterward. This is rarely caused by the new technology. It comes down to planning, priorities and handover.

45 %average budget overrun on large IT projectsMcKinsey & University of Oxford, 2012
56 %less value than planned delivered by large IT projects on averageMcKinsey & University of Oxford, 2012

These figures come from a 2012 study by McKinsey and the University of Oxford covering more than 5,400 large IT projects. An ecommerce website relaunch at a mid-sized company is usually smaller. The patterns are the same, though: too much scope, too little buffer, and benefits measured too late.

The three major risks

1. Google visibility

New URLs, changed content, missing redirects: search engines have to understand the store all over again. If redirects are missing for pages that rank well, those rankings are lost. This often hits exactly the category pages and guide content that have brought in organic traffic for years. That is why site migration SEO belongs at the center of any relaunch plan.

2. Conversion

New navigation, new filters, new checkout: returning customers suddenly can’t find their way around. Elements that worked well fall victim to the new design, often because nobody measured what was working in the old store.

3. Stability

Interfaces to ERP, payment providers and shipping carriers behave differently under load than in testing. Errors in order transfer often go unnoticed until orders start piling up.

The best relaunch starts with the question of what the old store does well.

A relaunch in five phases

Five phases for a safe relaunch

AuditMeasure what works today
Goals & scopePriorities, must-haves and nice-to-haves
ImplementationIn stages, with testing
CutoverRedirects, data reconciliation, trial run
AftercareMonitor closely and fix what needs fixing

Phase 1: Audit of the current store

Before anything new is built, you need a clear picture of what exists:

  • Which pages bring in organic traffic and revenue?
  • Which features do customers use most, such as search, filters, wish lists or quick order?
  • What are the current conversion rate, average order value and load times, broken down by device?
  • Which interfaces and special processes exist?

These figures later become the yardstick for success.

Phase 2: Goals and scope

Set measurable goals and draw a clear line between “must be there at launch” and “can come later.” The smaller the first step, the lower the risk. Many features can be added calmly after launch.

Phase 3: Implementation in stages

Test early and regularly, not just at the end. Involve the business teams: customer service, warehouse and accounting know the special cases that nobody thinks of in project concepts.

Phase 4: The cutover

The most critical moment is the switch itself. This is where a go-live checklist earns its keep:

  • Redirects: Every important old URL points to the matching new page, not blanket to the homepage.
  • Data reconciliation: Products, prices, stock levels and customer accounts are fully checked before launch.
  • Trial run: Real orders go through the whole process once, from checkout to the invoice in the ERP.
  • Timing: Don’t launch ahead of public holidays, major promotions or during peak season.

Build in generous buffers. Don’t announce a fixed launch date externally until testing is complete.

Phase 5: Aftercare

The first weeks after launch are decisive. Monitor visibility, error pages, conversion and order transfer every day. Keep development capacity free for quick fixes. A relaunch is only finished when the key metrics are back to at least the old level.

The most common mistakes

  • Too much at once: A new platform, new design, new product range and new processes all at the same time.
  • Forgetting what already works: Popular features of the old store are missing because nobody wrote them down.
  • Redirects as an afterthought: They are created shortly before launch and never checked.
  • No measurement afterward: Whether the relaunch reached its goal is never properly evaluated.

Sometimes the best relaunch is none

Not every problem calls for a new store. Targeted improvements to the existing system often deliver more: a reworked checkout, better product data, faster load times. Take an honest look at whether a step-by-step rebuild would be cheaper and safer.

Conclusion

A relaunch succeeds when it is run as a business project, not a design project. Measure beforehand what works. Limit the scope. Plan the cutover carefully and watch the first weeks closely. That is how a new store becomes a better store, and how you manage a relaunch without losing traffic.

Frequently asked questions

How do I prevent ranking losses after a relaunch?

With a complete list of all important URLs, clean 301 redirects to pages with matching content, carried-over content and metadata, and close monitoring in Google Search Console after launch.

How much buffer should I plan for?

Enough that you don’t have to launch under deadline pressure. What matters is to set the launch date only once testing has been completed successfully.

What needs to be tested before launch?

The complete order process with all payment methods, the handover to ERP and shipping, customer accounts, search and filters, and the redirects for the most important old URLs.

Sources

Inhalt

    InsightsIns Gespräch kommen