How to plan a website redesign properly

A website redesign usually starts with a visible problem. Conversion rates have stalled. The brand feels dated. Content teams are fighting the CMS. Pages are slow, rankings are slipping, and simple updates take too long. That is exactly why knowing how to plan a website redesign matters. If the planning is weak, the project becomes a cosmetic exercise. If the planning is sound, a redesign can improve performance, reduce operational friction and create a stronger platform for growth.

The mistake many organisations make is treating redesign as a design problem first. In practice, it is a business problem with design, content and technology implications. A better-looking interface may help, but only if it supports the right user journeys, works with your internal processes and gives your team a platform they can manage properly.

How to plan a website redesign with the right brief

A strong redesign brief is less about listing features and more about defining what success looks like. Before anyone discusses layouts, animations or templates, get clear on why the project exists.

That usually means answering a few uncomfortable questions. What is not working today? Which journeys are underperforming? Where are users dropping off? What can your team not do efficiently with the current setup? If senior stakeholders cannot agree on the problem, the redesign is likely to drift.

The most useful briefs connect digital decisions to commercial outcomes. For one business, that might mean increasing qualified enquiries. For another, it could be improving ticket sales, reducing reliance on manual processes or making a high-traffic publishing platform more resilient. A redesign should have measurable intent, not just a refreshed look and feel.

At this stage, scope discipline matters. Not every long-standing issue belongs in the first phase. Sometimes the right call is to redesign the public website now and address wider platform integration later. Sometimes it is the opposite. Good planning is partly about ambition, but just as much about sequencing.

Start with evidence, not opinion

Redesign discussions often attract strong personal views. Senior leaders may have preferences about style. Internal teams may want to preserve sections they built years ago. None of that is unusual, but it becomes risky when opinion outruns evidence.

Start by auditing the current website properly. Review analytics, search performance, user behaviour, content quality, technical health and conversion journeys. Look at where users enter, what they engage with and where they abandon. If the site supports operational tasks, examine how it performs for staff as well as customers.

Qualitative insight matters too. Speak to the people who use the site and the people who manage it. Marketing teams will often surface pain points around campaign landing pages, content publishing and reporting. Operations teams may raise issues around bookings, integrations or admin workflows. Customer-facing teams can often explain exactly where users get confused.

This is where trade-offs start to emerge. You may find pages with strong traffic but weak conversion, or content that performs well in search but undermines brand perception. You may discover that a technically outdated platform still supports editorial teams well, while a newer toolset would create unnecessary complexity. Planning means making informed choices, not assuming newer always means better.

Define audiences and the journeys that matter most

One of the clearest ways to derail a redesign is trying to serve every audience equally. Most organisations have several user groups, but not all journeys carry the same commercial or operational weight.

Map your priority audiences and identify what they need to do. A hospitality brand may need to balance inspiration with booking efficiency. A theatre may need to support discovery, event selection and ticket purchase under sharp peaks in traffic. A B2B company may need to guide users from service understanding to credible enquiry. A publisher may be balancing subscription growth, editorial experience and ad performance.

Those priorities should shape information architecture, content hierarchy and feature requirements. This sounds obvious, yet many redesigns still begin with home page concepts before anyone has agreed the primary journeys.

User needs also need to be balanced with business needs. For example, reducing the number of choices on a page can improve clarity, but it may also affect cross-sell opportunities. Introducing richer media may strengthen brand storytelling, but it can harm performance if not handled carefully. The right answer depends on what the site is there to achieve.

Content and SEO should be part of the plan from day one

A redesign can quietly damage performance when content and SEO are left until late in the process. Search visibility is often built over years, and careless restructuring can undo valuable authority surprisingly quickly.

Planning should include a content audit, migration approach and clear ownership. Decide what will be kept, rewritten, merged or removed. If your current site contains hundreds or thousands of pages, this is not admin. It is a strategic task that affects user experience, search performance and internal workload.

The same applies to SEO. Protect high-value pages, understand keyword intent, map redirects carefully and consider how the new structure will support organic growth. If a redesign changes URL patterns, navigation or page templates, those decisions should be reviewed through a search lens, not just a design one.

It is also worth being realistic about content production. New templates often assume stronger copy, better imagery and more structured content than teams can realistically produce at launch. A content model that looks elegant in workshops can become difficult to sustain in practice. Planning well means building for the team you have, not the ideal team you wish you had.

Choose technology around fit, not fashion

When considering how to plan a website redesign, platform choice is usually one of the most consequential decisions. It affects editorial flexibility, integration options, performance, security, scalability and long-term cost.

The right platform depends on the complexity of the site and the wider business context. A marketing-led website with straightforward publishing needs will require something different from a site tied into bookings, customer data, reporting or bespoke operational processes. This is where businesses often benefit from a partner that can assess both creative requirements and technical realities.

Avoid choosing technology because it is currently fashionable or because one stakeholder used it before. Instead, assess what the site needs to do now, what it may need to do in two to three years, and what level of in-house capability you have to maintain it. A flexible setup with sensible governance is usually more valuable than a highly customised platform that becomes expensive to evolve.

Integrations deserve particular attention. CRM, ticketing, payment systems, ERP tools, marketing automation and third-party services all shape the real complexity of a redesign. A polished front end can hide brittle back-end processes if those dependencies are not scoped properly.

Governance keeps the project moving

Even well-funded redesigns can lose momentum if decision-making is vague. Planning should establish who owns the vision, who approves what, and how changes are controlled.

That does not mean creating unnecessary bureaucracy. It means giving the project enough structure to avoid endless revision cycles and conflicting stakeholder feedback. Clear governance is especially important when a redesign touches multiple departments or when the website supports both brand and operational functions.

It also helps to define what is in scope for launch, what sits in a later phase and what is explicitly out of scope. Without that, redesign projects absorb every dormant idea in the business. The result is usually delay, compromise and budget pressure.

A good agency partner will challenge assumptions here, not simply take requests at face value. At 16i, that kind of challenge is often where better outcomes start, because digital projects rarely improve through unchecked accumulation.

Plan the launch before the build is finished

Launch is not the final item on a timeline. It should be part of the planning from the beginning. That includes migration, redirects, testing, analytics setup, performance benchmarking, accessibility checks and rollback contingencies if something goes wrong.

It also includes internal readiness. Has the team been trained on the CMS? Are workflows in place for publishing and approvals? Do you know how success will be measured in the first 30, 60 and 90 days? A redesign does not create value simply because it goes live. Value appears when the platform is adopted, refined and used properly.

This is one reason post-launch optimisation matters. User behaviour on a live site often reveals things that workshops and wireframes cannot. The aim is not to launch a perfect website. It is to launch a well-considered one with the right foundations for improvement.

The organisations that get the most from redesign tend to treat it as a business change project, not a one-off creative exercise. That mindset leads to better decisions, fewer surprises and stronger long-term returns. If you are planning a redesign, give the strategy as much attention as the visuals. The site your business needs next is rarely solved by surface-level change.