Crisis SEO Case study

A sitewide redirect chain caused an almost 80% organic traffic loss

A developer partner had released a new design and structure on the same Magento CMS. When traffic collapsed, the team considered returning to the old website. We found one repeated redirect pattern behind the loss and repaired it without discarding the redesign.

≈ 0 %

Organic traffic lost after migration

Critical migration mistake

STARTING POINT

The Situation

The CMS had not changed, but the design and structure had. Soon after release, organic traffic fell by almost 80%, placing the entire redesign under suspicion.

Problem

Traffic collapsed

The website lost almost four-fifths of its organic traffic after release.

Problem

The site looked functional

Normal browser use did not reveal an obvious failure matching the scale of the decline.

Problem

A rollback was being considered

The team was close to abandoning the new design and returning to the previous structure.

Problem

The failure affected the whole site

The cause was repeated across many migrated URLs rather than limited to one page.

WHAT MADE IT COMPLEX

The Challenge

Redirects had been created from old URLs to intended destinations. During development, some of those destination URLs changed again, and the website automatically redirected them to the current pages.

That created an additional hop across the website. Each individual chain could appear minor, but the repeated pattern formed a sitewide migration failure. The task was to prove that this specific implementation issue, not the redesign as a whole, was the cause.

Redirect destinations changed during development

Automatic redirects hid the outdated mappings

The same chain pattern existed across the website

The client was considering a costly full rollback

Our Approach

We reconstructed the URL path before deciding whether the new website itself had failed.

Step

Compare the migration paths

We followed old URLs through every redirect until they reached the current pages.

Step

Identify the repeated extra hop

We confirmed that outdated target URLs were redirecting again automatically.

Step

Separate the cause from the redesign

The evidence showed that the design did not need to be abandoned to recover performance.

Step

Correct the redirect setup

Affected old URLs were pointed directly to their current intended destinations.

Step

Verify traffic recovery

We monitored the website after the correction while the new design and structure remained live.

“

After the traffic loss, we were seriously considering returning to the old Magento design and structure. Back2Rank did not assume the redesign itself was the problem. They investigated the migration, found the sitewide redirect chains, and explained the cause in a way our development team could act on immediately. Traffic recovered without a rollback, which protected both the client's organic performance and all the work invested in the new website.

Hein de Kroes, Lead Software Developer of the project

The Results

Organic traffic returned without reverting the new website

Correcting the sitewide redirect chains restored the lost performance. The client preserved the full Magento redesign and avoided a disruptive rollback.

The case changed the decision from “old website or new website” to the more accurate question: “Which part of the migration is broken?” One repeated technical pattern, not the whole project, was responsible.

≈ 0 %

Organic traffic lost after migration

Critical migration mistake

Lost traffic after a migration or redesign?

Before you roll the whole website back, we can identify which change actually caused the loss and build the shortest defensible path to recovery.