The five ways redesigns kill traffic
In every post-mortem we've run on a redesign gone wrong, the cause was one of five: URLs changed without redirects, content was 'streamlined' away along with its rankings, metadata was regenerated from templates, internal links thinned out, or the new build was simply slower. None of these are design problems. All of them are process failures — which means all of them are preventable with a checklist and an owner.
The migration discipline
Before anything ships: crawl the old site and inventory every URL with traffic or links; map each to its successor in a redirects file that lives in version control; diff old and new content for parity on pages that rank; and hold the new build to equal-or-better performance budgets. After launch: watch Search Console daily for two weeks, chase every 404, and resist the urge to 'clean up' redirects for at least a year.
Done this way, redesigns usually gain traffic within a quarter — the new site is faster and better structured, and Google notices both. The horror stories come from teams that treated migration as an afterthought on launch week.
Working on something in this space?
We help teams turn articles like this into shipped systems. One business day to an honest answer.
Request a Quote