The website redesign process: a step-by-step guide
A redesign goes wrong when it starts with visuals instead of a plan. Done right, it's a sequence: define the problem first, audit what you have, plan structure and content before design, and protect your SEO with a redirect plan so you don't lose years of rankings. Then design, build, and test with real content, and treat launch as a starting point, not a finish line. It's a structured project, not a fresh coat of paint.
A redesign is a project, not a paint job
Most website redesigns start in the wrong place: with how the site looks. Someone decides the current site feels dated, a designer is briefed, and the project becomes about visuals. Months later there’s a prettier site that often performs no better, and sometimes worse, because the redesign never addressed why the old site wasn’t working.
A redesign done well is a structured process with a clear order, where each step builds on the last. Looks are part of it, but near the end, not the beginning.
The seven steps
A redesign that protects what works and fixes what doesn’t, in order. Here’s the sequence that actually works.
Step 1: Define why you’re redesigning
Before anything else, get specific about the problem you’re solving. “It feels old” isn’t a reason. “Our bounce rate is high, the site doesn’t generate leads, and we can’t update it without a developer” is.
Write down the actual goals: more qualified leads, better mobile experience, easier content management, faster load times, a clearer message. These goals drive every later decision, and without them you have no way to judge whether the redesign succeeded. Define what success looks like in measurable terms now, so you can prove it later.
Step 2: Audit what you already have
You can’t improve a site you don’t understand. Before redesigning, take stock of the current one.
Look at the data: which pages get traffic, which convert, which rank in search, and which are dead weight. Your best-performing pages are assets to protect, not things to casually throw away. A redesign that accidentally removes or breaks a page that brought in steady leads is a step backward, however good it looks. This audit tells you what to keep, what to fix, and what to cut.
Step 3: Plan structure and content before design
This is the step most teams skip, and it’s the one that matters most. Structure comes before visuals.
Map the sitemap first: what pages exist, how they’re organized, how someone navigates from landing to conversion. Then sort out content, because design should present content, not the other way around. Designing beautiful pages and then trying to pour words in later is backwards, and it shows. Get your messaging and key content settled, at least in draft, before serious design begins.
Step 4: Protect your SEO (the step people forget)
This is where redesigns quietly destroy value. Search authority is earned slowly and lost fast, and a careless redesign can erase years of rankings overnight.
The essentials: map every old URL to its new equivalent and set up proper redirects so nothing breaks and no equity is lost. Keep the content and pages that rank well, preserve their structure where you can, and plan the migration so search engines follow you cleanly to the new site. If you take one thing from this guide, make it this. A redesign that loses your SEO is a failure no matter how good it looks. (For more on the technical side, our Webflow CMS and SEO coverage goes deeper.)
Step 5: Design, then build, with real content
Now, and only now, does design happen, and it happens with real content in hand, not lorem ipsum.
Design the key templates and pages around the structure and content you’ve already settled. Designing with real headlines, real copy, and real images produces a site that works in reality, not just in a mockup. Then build it properly: clean, fast, responsive, and easy for your team to manage afterward. A site that looks good but is slow or impossible to update has just recreated the original problem in a new skin.
Step 6: Test before you launch
Before going live, test everything. This is dull and it is also where launch disasters are prevented.
Check that pages work across browsers and devices, forms submit and reach where they should, links work, the site is fast, and every redirect resolves correctly. A staging environment lets you catch problems before users do. Walk the whole site as a visitor would, on a phone as well as a desktop, and fix what breaks before launch, not after.
Step 7: Launch carefully, then keep improving
Launch is a careful, monitored step, not a button you press and walk away from.
Go live with a plan: confirm redirects are working, check analytics is tracking, watch search performance in the days after, and be ready to fix anything that slipped through. Then remember the real point: a redesign is a starting line, not a finish line. The first version live is the beginning of improving based on real data, not the end of the project. The best sites are refined continuously, not redesigned in a panic every few years.

The short version
A good redesign follows an order: define why, audit what you have, plan structure and content, protect your SEO, then design, build, and test, and launch carefully. Skip the early steps and you get a prettier site that performs worse. Follow them and you get a site that actually fixes what the old one got wrong. The visual refresh is the easy part and the last part. The thinking that comes before it is what makes the difference.


