A website redesign process runs in six phases: strategy, audit, structure and content, design, build, and measurement after launch. Most of the effort lands before anyone opens a design file, and that is the part teams underestimate.
Skip the early phases and you get a familiar result. The new site looks current, the navigation is cleaner, and the donation rate has not moved. Eighteen months later the same complaints come back, because nobody ever decided what the site was for.
This guide walks through each phase, what it produces, how long it takes, and where redesigns lose the plot. By the end you should be able to scope your own project honestly, and spot the cases where a redesign is the wrong tool entirely.
Key Takeaways
- A website redesign process has six phases: strategy, audit, structure and content, design, build, and post-launch measurement.
- Expect the first three phases to take a large share of the calendar while producing no screens anyone can look at.
- Plan 12 to 24 weeks for a marketing-site redesign, and expect content to be what makes it run long, not design.
- Launch is the midpoint of the process. Without a measurement phase, you cannot tell whether the redesign worked.
- If your problem is one leaking page or an unmaintainable platform, you need CRO or a re-platform, not a redesign.
Why a website redesign process starts before the design
A redesign request almost always arrives as a look problem. The site feels dated, a board member complained, a peer organization launched something sharper. Those signals are real, but they describe a symptom. The question underneath is what the site needs to do this year, and for whom.
Answering that question has a cost. It takes weeks of honest argument about audiences and priorities, and it produces nothing you can show anyone. Skipping it feels efficient. It is also the most reliable way to spend six months and land somewhere beige.
So before moodboards, before scope, name the job: one primary audience, one primary action for that audience, and one metric you would defend in a board meeting. Everything downstream, including human-centered product design, gets easier once that exists, because you finally have something to say no with.
The six phases of a website redesign process
The sequence below is the one we use on client work. The phases overlap in practice, but the order matters: each one produces the input the next one needs.
1. Strategy: decide what the site is for
This phase produces a short document, not a deck. It names the primary audiences, the action you want from each, the metric that defines success, and the constraints you are working inside: budget, team capacity, the platform you can realistically maintain.
It should also record what you are deliberately not doing. A redesign with no stated exclusions expands until the budget runs out.
2. Audit: learn what already works
Before you throw anything out, find out what is earning its place. Pull analytics for the last 12 months and sort pages by traffic and by conversion. Pull Search Console queries to see what people already come to you for. Inventory every page and tag it: keep, merge, cut, rewrite.
Then watch a few people use the current site. Research from Nielsen Norman Group found that testing with about five users surfaces the majority of usability problems, which puts a real usability read within reach of a small team.
The audit protects you as much as it informs you. Teams rebuild high-performing pages surprisingly often, purely because those pages looked old.
3. Structure and content: fix the shape, then write
Information architecture comes next: the sitemap, the navigation, and a page-by-page plan for what survives. Most cluttered sites are not badly designed. They are well-designed sites carrying five years of well-meaning additions.
Then the content, which is where most redesign timelines break. Copy is usually owned by people who have other full-time jobs, and it cannot be finished in the last two weeks. Assign an owner and a due date to every page in the plan, and start the writing while design is still in progress.
4. Design: build a system, not a set of pages
Good redesigns produce a system: a type scale, a color palette with contrast you have tested, a component library, and the rules for how they combine. Pages then assemble from parts your team can reuse without a designer in the room.
Treat accessibility as a design constraint here, not a QA pass at the end. Contrast, focus states, and heading structure are cheap to get right in the system and expensive to retrofit across 80 pages.
5. Build: move the site without losing the traffic
Engineering is where the plan meets reality: the CMS, the integrations with your CRM or donation platform, and the redirect map. If URLs are changing, follow Google’s guidance on site moves with URL changes and map every old URL to its closest new equivalent before launch day, not after.
Set a performance budget at the same time. A redesign that ships beautiful pages with poor Core Web Vitals has traded measurable reach for visual polish. This is the phase where re-platforming and design have to be one conversation rather than a handoff between two vendors.
6. Launch and measure: the midpoint, not the finish line
Record your baseline numbers before launch: conversion rate on the pages that matter, organic traffic, and the funnel steps where people currently drop out. Without that snapshot, you have no way to know what the redesign did.
Then keep working. The first month after launch is the cheapest time to fix real problems, because you finally have behavior instead of opinions. This is where conversion rate optimization earns its keep, and it is the discipline behind our product-led growth work with Kiva: find the leak, test the fix, prove it moved.
How long a website redesign takes
Plan 12 to 24 weeks for a marketing-site redesign with a small in-house team, and longer if you are also rebuilding a brand or migrating hundreds of pages of program content.
Four things drive the number:
- Page count and content depth. A 30-page site and an 800-page content library are different projects.
- Who writes the copy. In-house writing is cheaper and slower; nothing stretches a timeline further.
- Integrations. CRM, donation, and event tooling add discovery and testing time.
- Decision structure. Every additional approval layer adds calendar, not quality.
The last one is worth naming plainly. If the first time a senior stakeholder sees the work is the moment they have to approve it, you have already lost weeks. Bring them into the strategy phase, when changing direction is free.
Where redesign projects go wrong
Most redesigns do not fail loudly. They drift. The five most common drifts:
- The goal was never written down, so every opinion carried equal weight and the loudest one won.
- Design started before structure, and beautiful pages on a confused sitemap stay confusing.
- Content was left until the end, so the site launched with placeholder copy nobody went back to.
- Sign-off became the objective, and work aimed at internal comfort lost the edge that made it effective.
- Nobody measured anything, so a year later the only evidence is that it looks better.
Every one of those is a process problem rather than a taste problem. That is good news, because process problems are fixable in advance.
When you don’t need a website redesign
A full redesign is the most expensive answer to several cheaper questions. Before you scope one, check whether you have a different problem:
- One page underperforms. If your donation form or signup flow is where people leave, run experiments on that flow. A redesign is a slow, costly way to fix a single page.
- The platform is the problem. If the structure and content still work but the site is slow or unmaintainable, you want a re-platform, not a new design.
- Nobody agrees what you do. If your team cannot state the value proposition in one sentence, a redesign will render that confusion in a nicer typeface. Start with brand strategy.
- The site is two years old and working. Age is not a reason. Falling short of a goal is.
Saying this costs us work sometimes, and it is still the right advice. The redesigns that pay for themselves are the ones scoped against a real problem.
Frequently asked questions about redesigning a website
How much does a website redesign cost?
Cost tracks scope more than anything else: page count, how much content needs writing, the number of integrations, and whether brand work is included. Rather than asking for one number, ask any partner to price two or three scope tiers and explain what drops out of each. That conversation tells you more about how they think than a single quote does.
Should we redesign or re-platform?
Re-platform when the structure and content still serve you but the technology does not. Redesign when the site no longer communicates the right thing to the right people. Plenty of projects need both, which is an argument for keeping design and engineering on one team.
Will a website redesign hurt our SEO?
It can, and the damage is almost always avoidable. Rankings drop when URLs change without redirects, page content thins out, or metadata is lost in migration. Build the redirect map before launch, keep the content that earns traffic, and watch Search Console closely for the first month.
Do we need to rewrite all our content?
Usually some, rarely all. The audit tells you which pages earn traffic and which have never been read. Rewrite the pages that matter, cut the ones nobody visits, and stop treating a content refresh as a separate project you will get to later.
How do we know if the redesign worked?
Compare the metric you named in the strategy phase against the baseline you recorded before launch. If you did not name a metric or record a baseline, you cannot answer this question, which is the main reason both steps belong in the process.
Starting a redesign you won’t regret
A website redesign process is mostly decisions. Name what the site is for, learn what already works, fix the structure, build a system rather than a pile of pages, protect your traffic through the migration, and keep measuring once it is live. Projects that go sideways have usually skipped one of those steps, and the cause is almost never a shortage of taste. It is a sequence nobody agreed on.
The two habits worth carrying into your own project: do the unglamorous work before anyone opens a design file, and treat launch day as the middle of the job.
If you are weighing a redesign and want a candid read on scope, start a conversation with Niftic. We will tell you what we would cut, and we will tell you if a redesign is not what you need.