A website redesign is rarely just a design decision. It is usually triggered by a bigger business problem: your brand has moved on, the site no longer reflects the quality of your work, enquiries are weak, or the user journey has become difficult to manage. Knowing how to plan a website redesign properly turns that frustration into a focused commercial project rather than an expensive visual refresh.
The strongest redesigns do not begin with colours, layouts or a list of competitor sites. They begin with clarity. What needs to change, what must be protected, and what should the new website help the business achieve?
Start with the business case, not the homepage
Before anyone opens a design file, define why the existing site is being replaced or reworked. “It looks dated” can be part of the answer, but it should not be the whole brief. A modern-looking site that keeps the same confusing structure, weak messaging and poor conversion paths will still underperform.
Set a clear primary objective. For a service business, that may be generating better-quality enquiries. For a growing brand, it could be establishing credibility in a more competitive market. For an ecommerce business, the focus may be improving product discovery and reducing checkout friction. A site can support several outcomes, but one priority should lead the project when trade-offs arise.
Turn that objective into measurable signals. These might include more consultation requests, stronger organic traffic to key services, a lower bounce rate on campaign landing pages, increased time spent reviewing case studies, or fewer support queries caused by unclear information. Baseline the numbers before the project starts. Without a starting point, it is difficult to prove whether the redesign has worked.
It also helps to identify what is not working in plain language. Perhaps visitors cannot quickly understand your offer. Perhaps your team struggles to update content. Perhaps the mobile experience feels like an afterthought. These are practical problems that strategy, content, UX and development can solve together.
How to plan a website redesign around real users
A website should make sense to the people you want to work with, not only to the people inside your business. Your internal team knows your services, terminology and process already. A prospective customer does not.
Start by looking at the audiences that matter most. A founder buying a specialist service has different questions from a returning customer or a recruitment candidate. Consider what each group needs to know before taking the next step, what may create doubt, and what action represents progress.
This does not always require a lengthy research programme. Review enquiry notes, sales calls, customer feedback, search terms and website analytics. Speak with the people who deal directly with customers. Their perspective often reveals the questions the site needs to answer more clearly.
Then map the key journeys. A visitor arriving from Google may land directly on a service page, not your homepage. A prospect referred by a colleague may go straight to your portfolio or about page to assess credibility. Each route should lead naturally towards the next useful action, whether that is booking a call, requesting a quote, viewing relevant work or making a purchase.
Good UX is not about adding more steps or visual effects. It is about removing unnecessary effort. Clear navigation, decisive page hierarchy, useful calls to action and content that answers the right questions create momentum.
Audit what exists before deciding what goes
Treat the current site as evidence. Some pages may be obsolete, but others may bring valuable traffic, rank well in search, attract links or convert consistently. Removing them without a plan can damage visibility overnight.
A practical audit should cover at least these areas:
- Site performance, mobile usability and technical issues that affect experience or search visibility.
- Page-level traffic, rankings, backlinks and conversions.
- Content quality, accuracy, duplication and gaps in the customer journey.
- Brand consistency, including messaging, imagery, typography and tone of voice.
- Content management needs, such as who updates the site and how often.
Use the audit to make informed decisions: keep, improve, consolidate, redirect or retire. This is particularly important for established businesses with years of blog posts, service pages or campaign content. A smaller site with a clearer structure can be more effective than a large one, but simplification should be deliberate.
Define the new structure and content early
A sitemap is not a technical afterthought. It is the framework for how customers understand your business. It should reflect your priorities, services and the way people search for information.
Avoid organising the site purely around internal departments or jargon. Use language your audience recognises. If your services overlap, decide whether they need separate pages for search intent and clarity, or whether one stronger page will do a better job. It depends on the depth of the offer and the questions buyers need answered.
Once the structure is agreed, create a content plan before design is finalised. This prevents a common problem: a polished layout is approved, then content is forced into it later. Copy should shape the hierarchy, not simply fill empty space.
For every key page, establish its role, intended audience, primary message, supporting proof and next action. A strong service page may need to explain the problem it solves, the process, the scope, relevant outcomes and why your approach is distinct. Case studies should show more than attractive finished work. They should demonstrate thinking, execution and results where available.
Photography, illustration, video and motion also need planning. Bespoke visual assets can materially improve brand perception, but they require time, budget and direction. Stock imagery may be appropriate for some contexts, yet it can quickly make a premium business feel interchangeable. Decide where original creative work will have the greatest impact.
Build SEO and technical requirements into the brief
Search visibility should be protected from the start, not patched in at launch. If URLs change, create a redirect plan that maps every important old page to its most relevant new destination. Do not redirect everything to the homepage. That creates a poor experience and can waste existing authority.
Retain valuable page themes where they still serve the business. Update titles, headings, internal links and copy to match the new positioning, but do not discard useful search equity because a page feels visually outdated. New content opportunities should be based on genuine customer demand, not a list of generic keywords.
The technical brief should also cover performance, accessibility, security, analytics, cookie consent, form handling and integrations. If the site needs to connect to a CRM, booking system, email platform, payment provider or member area, establish the requirements before development begins. Late integration decisions are a reliable way to create delays and compromises.
Accessibility deserves the same consideration as aesthetics. Legible type, sufficient contrast, logical heading structure, keyboard-friendly interactions and meaningful image descriptions make the site easier to use for more people. They also tend to improve overall clarity.
Set a realistic scope, budget and decision process
A redesign moves faster when the right people are involved at the right moments. Assign one project lead on the client side who can gather feedback, make decisions and keep stakeholders aligned. Too many unstructured opinions can dilute a clear direction.
Agree what the project includes before work begins: strategy, copywriting, photography, brand refinement, design, development, SEO migration, testing and post-launch support. A low initial cost can become expensive if essential elements are treated as extras later. Equally, not every business needs a full rebrand or a complex custom platform. The right scope depends on the gap between where the business is now and where it needs to be.
Build time into the schedule for content approvals, legal checks, stakeholder feedback and testing. The design stage is only one part of the project. Rushed launches often happen because content and technical decisions were left too late.
Test before launch, then keep improving
Before publishing, test the site across current browsers, screen sizes and real user paths. Submit every form. Check confirmation messages, email notifications, tracking, navigation, search functions and redirects. Review pages on a phone, not just a desktop monitor.
Launch is the beginning of the next phase, not the finish line. Watch search performance, user behaviour and enquiry quality closely in the first weeks. Small improvements to calls to action, page copy or form fields can have a meaningful effect once real visitors begin using the site.
A well-planned redesign gives your business more than a better-looking website. It creates a sharper digital foundation for how customers find you, judge you and choose to get in touch. Give the planning the same attention as the design, and the finished site will have something more valuable than polish: a clear reason to perform.
