The most common outcome of a redesign is a better-looking site that performs worse. Not because the design was wrong, but because nobody mapped the old URLs, recorded a baseline, or checked the content survived.
Everyone enjoys the design phase. The reason redesigns go wrong is almost always in the work either side of it — what existed before, and what got measured after.
Which pages earn the traffic, which earn the revenue, and which nobody has visited in a year. You cannot protect what you never measured.
Every existing page catalogued and given a decision — keep, merge, rewrite, or drop — deliberately rather than by whoever forgets to migrate it.
Every indexed URL mapped to its replacement before cutover, which is the single step that most often gets skipped and most often causes the drop.
The part you were expecting, done against the structure the audit and inventory established rather than against a blank page.
Speed treated as a requirement with a number attached, so the new site doesn't launch heavier than the one it replaced.
Rankings, errors, and conversion tracked daily against the recorded baseline for the weeks when problems actually surface.
These are the four failures we get called in to repair, usually about six weeks after a launch that everyone was pleased with at the time.
A redesign is also the right moment to fix how the site behaves on phones — see responsive web design. Keeping it healthy afterwards is website maintenance.
Tell us what's driving the redesign and what the current site earns. We'll come back with a plan that protects the second thing while delivering the first.