Insights · Web & UI/UX
Website redesign process:
7 stages from strategy to launch.
A redesign succeeds when it changes how clearly the business communicates and how easily people act—not when it only replaces the visual skin.
The direct answer
What are the stages of a website redesign?
A sound website redesign has seven stages: define business outcomes, audit the current site, research users and content, rebuild the information architecture, create and approve content, design and prototype the experience, then develop, test, launch and measure. Strategy and content should begin before high-fidelity screens.
Why redesigns become difficult
A website sits between brand, sales, service, hiring, technology and internal politics. If those needs are not made explicit, the project becomes a collection of page requests and visual opinions. A staged process gives every decision a reason and prevents expensive discoveries late in development.
1. Define the business outcome
Start with what the site must change: qualified enquiries, product understanding, partner confidence, recruitment, self-service or operational efficiency. Choose a small number of measurable outcomes and identify the audience action connected to each one.
- What business change triggered the redesign?
- Which audiences matter most?
- What should each audience understand or do?
- How will the team recognize improvement after launch?
2. Audit the current website
Inventory pages, traffic, search queries, conversion paths, content owners, integrations and technical risks. Keep what already earns attention or trust. Redirect valuable URLs instead of erasing their history. A redesign should not accidentally remove the pages people and search engines already rely on.
3. Research users, stakeholders and content
Interview customer-facing teams and a focused sample of users. Review sales questions, support requests, search data and competitor patterns. The goal is not to copy convention blindly, but to understand the language, evidence and tasks people need.
4. Rebuild the information architecture
Create a sitemap and navigation based on user intent and business priority. Give every page one primary purpose. Map critical flows—such as understanding a service, evaluating proof and making contact—before designing layouts.
| Question | Useful output |
|---|---|
| What does the audience need? | Intent and task map |
| Where should each topic live? | Sitemap and page ownership |
| How does someone reach a decision? | Priority user flows |
| How will pages connect? | Navigation and internal-link plan |
5. Create the content before polishing screens
Write page briefs, message hierarchy, proof requirements and calls to action. High-fidelity design based on placeholder copy usually creates rework: the real content will not fit the imagined shape, and important evidence arrives too late.
Content does not need to be final before any wireframe exists. Structure and writing can develop together—but both must be treated as product work, not last-minute population.
6. Design and prototype the experience
Begin with low-fidelity layouts for hierarchy and flow, then establish the visual system: typography, spacing, color, image direction, components and interaction states. Test the highest-risk journeys and review mobile behavior early rather than shrinking a desktop composition at the end.
7. Develop, test, launch and measure
Development should include accessibility, responsive behavior, performance, analytics, redirects, metadata and content editing—not only visual reproduction. Before launch, test forms, links, devices, browsers, tracking, indexing controls and error states.
After launch, compare the agreed outcomes. A website is not finished when it goes live; it becomes measurable.
Who should own each decision?
Assign one accountable owner for business goals, content, design approval and technical delivery. Gather stakeholder input at planned points, but avoid asking every person to approve every detail. Clear decision rights protect both schedule and quality.
Common redesign mistakes
- Beginning with visual references before agreeing on goals.
- Copying the old sitemap into a new skin.
- Writing content after layouts are approved.
- Ignoring redirects, search demand and existing high-value pages.
- Leaving mobile, accessibility and performance to final QA.
- Launching without conversion events or a measurement baseline.
Website redesign readiness checklist
You are ready to begin when the business trigger, priority audiences, decision-makers, launch constraints, available evidence, content owners, technical integrations and measurement access are known. Unknowns are acceptable; invisible unknowns are what create risk.