Website redesigns commonly fail for reasons that have nothing to do with visual design: no measurable goals, no redirect map, no performance budget, no rollback plan. Below is a 12-step checklist from https://softwin.io for planning a redesign before design work starts.
As companies grow — more products, more traffic, a larger team — their website often falls behind the business. A redesign gets approved, but many redesign projects skip straight to visual design without first defining goals, auditing the current site, or planning the technical migration. That sequencing gap is where most redesign problems come from: broken redirects, lost search rankings, integrations that silently stop working, launches with no rollback plan.
None of this is inevitable — it's a sequencing problem, and it's fixable by treating strategy and technical planning as the first phase of a redesign, with visual design second. SoftWin uses the checklist below when planning redesign projects, and it's shared here for anyone weighing one.
1. Define success as numbers, not adjectives
"Looks more modern" isn't a spec. Pick 2–3 measurable targets — conversion rate, mobile bounce rate, LCP/INP scores, lead quality — and record the current baseline plus the target. Without this, it's difficult to evaluate afterward whether the redesign achieved anything beyond a new look.
2. Audit before making changes
Pull analytics, Search Console, and current Core Web Vitals data. Identify the pages already driving conversions or organic traffic — these should be treated as a "do not break" list going into the redesign.
3. Run a content inventory
List every URL. Tag each: keep / update / merge / remove / redirect. Unglamorous, but one of the strongest predictors of whether post-launch SEO holds up.
4. Rebuild the IA before wireframes
If the business has grown, the existing navigation structure likely no longer represents it accurately. Map the new sitemap and primary user flows first; wireframes come after IA, not before.
5. Map every 301 redirect
Every changed URL needs an explicit, tested redirect to its new location. Unmapped redirects are a leading cause of companies losing accumulated search equity during a relaunch.
# Example redirect map format (adapt to your infra — nginx, Vercel, Cloudflare rules, etc.)
/old-product-page → /products/new-product-page 301
/blog/old-slug → /resources/new-slug 301
/pricing-old → /pricing 301
6. Set a performance budget, not just a style guide
Agree on LCP, INP, and CLS targets before design starts, and hold design and development decisions to them. A visually rich page that misses its performance targets works against the redesign's own goals.
7. Build accessibility in from the start
Contrast ratios, keyboard navigation, semantic heading order, alt text, and visible focus states are far cheaper to implement from wireframes than to retrofit after launch — and increasingly a compliance requirement rather than a nice-to-have.
8. Pick a CMS/stack for where the company is headed
If a knowledge base, localization, gated content, or a self-serve portal is on the roadmap for the next year, that should inform the platform decision now. Re-platforming shortly after a redesign is an expensive mistake to plan around after the fact.
9. Test integrations early and again before launch
CRM sync, marketing automation, analytics, and chat widgets can fail without an obvious signal. Verifying every form and tracking event before and immediately after launch reduces the risk of undetected breakage.
10. QA across real devices and browsers
Not just one browser on one machine — testing across device types and browsers catches issues that are easy to miss under deadline pressure.
11. Write an actual rollback plan
Define rollback trigger conditions, who owns the decision, and how quickly a revert can happen if something breaks in production.
12. Monitor for weeks, not hours
Track rankings, Core Web Vitals, and conversion rate against the baselines from step 1 for at least a few weeks post-launch, not just launch-day metrics.
Top comments (0)