Redesign without losing what ranks: compare every page before launch

Redesigns and platform migrations are where sites quietly lose years of work. Addresses change, headings disappear, internal links break, pages get slower, and nobody notices until the traffic report a month later. By then it is hard to tell which change did the damage.

On a recent rebuild we treated the launch like a release that had to prove it changed nothing for the worse.

Build on a full copy, not a sample

We tested on a complete copy of the live site, with real data and every page, not a handful of templates on a staging server. Problems in a redesign hide in the long tail: the old article with an odd layout, the category with 400 items, the page nobody has opened in two years.

Compare old against new, page by page

Before launch, 3,050 pages were compared between the old site and the new one. None got worse.

Make it faster while you are in there

Load times were measured on the full copy before launch, on the five page types that matter most. Field data from real visitors comes after launch, and we report it separately.

Release it like any other change

• Changes grouped into one release, with a written way to undo it.
• Live checks run straight after launch: 20 of 20 passed.
• Old addresses forwarded deliberately, not in bulk: 27,734 rules became 220.

A checklist before your own redesign

1. Export every address that gets search impressions today. That is the list you cannot lose.
2. Decide where each one goes after launch, before writing a line of code.
3. Test on a full copy of the site, not on a few templates.
4. Compare old and new automatically, page by page, and read the differences.
5. Measure speed on phones, on the pages that earn.
6. Keep a written way to undo the launch, and check it works.