A redesign should not begin with choosing colours or reviewing competitor homepages. It should begin with a commercial question: what must the new website improve for the business? This website redesign project planning guide helps decision-makers turn an ageing, underperforming site into a defined project with clear priorities, accountable people and measurable outcomes.
For most businesses, the trigger is obvious. The site looks dated, performs poorly on mobile, ranks inconsistently, is difficult to update, or fails to turn visits into enquiries. The risk is treating those symptoms as a design problem alone. A successful redesign brings strategy, content, technology, search visibility and conversion together before development begins.
Start with the business case, not the homepage
A website redesign needs a written business case that everyone can refer back to when decisions become difficult. It does not need to be a long document, but it must state why the project matters now and what success looks like after launch.
Set goals that can be observed and measured. For a professional services firm, that may mean increasing qualified consultation requests. For an e-commerce business, it could mean lifting mobile conversion rates and reducing cart abandonment. For a growing organisation, the priority may be presenting a more credible brand while making it easier for staff to publish content and manage leads.
Avoid broad goals such as “make the site modern”. Modern design may be an outcome, but it is not a business result. Instead, define targets such as improving Core Web Vitals, growing organic traffic to service pages, reducing form drop-off, increasing calls from mobile visitors, or cutting the time required to update a campaign page.
There are trade-offs. A highly customised platform can support complex processes and distinctive experiences, but it can add build time and ongoing maintenance. A templated approach may launch sooner and cost less, but can place limits on functionality and flexibility. The right choice depends on the organisation’s growth plans, internal capability and the importance of the website to revenue.
Build the right redesign team and decision process
Redesign projects lose momentum when feedback comes from too many directions or final approval is unclear. Establish a project owner with authority to make decisions, then nominate stakeholders from marketing, sales, operations and IT where relevant. Each person should have a clear role.
Marketing can own messaging, campaign priorities and brand consistency. Sales teams can identify the questions prospects ask before they enquire. Operations can explain workflows the website must support, while technical stakeholders can address security, integrations, hosting and platform requirements.
Agree on how approvals will work before design starts. Define who provides feedback, who consolidates it and who has final sign-off. A structured review process prevents rounds of conflicting comments that delay production and dilute the strategy.
Audit what exists before deciding what to replace
The current website contains valuable evidence, even if its design no longer represents the business. Review analytics, search performance, enquiry data, customer feedback and technical issues before creating a new sitemap.
Look for pages that attract meaningful organic traffic, generate enquiries or earn quality backlinks. These pages need a migration plan. Removing or changing URLs without redirects can cost rankings that have taken years to build. Equally, low-value pages that are outdated, duplicated or never visited should not automatically be carried into the new site.
A practical audit should examine four areas:
- Performance and usability: page speed, mobile experience, navigation, accessibility and form completion.
- SEO and content: rankings, indexed pages, metadata, backlinks, keyword opportunities and content gaps.
- Technology: CMS limitations, plugin health, security risks, hosting performance, integrations and data capture.
- Conversion: enquiry paths, calls to action, trust signals, sales content and friction points.
This work reveals whether the problem is the platform, the content, the user journey or a combination of all three. It also protects the parts of the existing website that already contribute to business performance.
Define scope around user journeys
A sitemap is useful, but it is not enough. The redesign scope should be built around the actions real users need to take. A prospective client may need to understand a service, see proof of capability, compare options and submit an enquiry. An existing customer may need to access support information, book a service or make a payment.
Map the highest-value journeys from entry point to conversion. Consider where people arrive from Google, social campaigns, referral traffic and direct visits. Then identify the content, functions and reassurance they need at each stage.
For example, a service page may need more than a short description and a contact button. It may require clear outcomes, process information, case studies, technical details, frequently asked questions and a form designed around the information the sales team genuinely needs. The answer depends on the buying cycle. High-value B2B services usually require more trust-building content than a straightforward local booking.
Document requirements precisely. “Add a calculator” is not a sufficient brief. Specify what it calculates, who manages the inputs, what happens with the result, whether it connects to a CRM, and how it works on mobile. Clear requirements reduce costly changes during development.
Plan content early, because it controls the timeline
Content is often the biggest hidden delay in a redesign. New page layouts cannot perform properly if the copy, photography, case studies, product data or brand assets arrive late. Treat content as a parallel workstream, not a task to complete after the site is built.
Create a page-by-page content plan that states whether each page will be retained, rewritten, consolidated, created or removed. Assign an owner and deadline to every item. If specialist photography, video or product information is required, schedule it early enough to support design and development.
Strong website copy should make the business proposition clear within seconds. It should explain who the business helps, what it delivers, why it is credible and what visitors should do next. Clear language outperforms vague claims, particularly for businesses selling complex services.
Choose technology that supports the next three years
Platform selection should be based on operational needs, not popularity alone. WordPress may suit a content-led business that needs flexible publishing and marketing integrations. Shopify or WooCommerce may be appropriate for e-commerce, depending on catalogue complexity, integrations and fulfilment requirements. A CMS migration or custom build may be necessary where the current system is insecure, difficult to maintain or unable to support essential workflows.
Ask practical questions. Who will update the website after launch? What third-party tools must connect to it? Is there a requirement for member access, bookings, subscriptions, multiple locations or complex product rules? What level of security, hosting and support is required?
Speed, mobile responsiveness and security should be requirements from the outset, not last-minute enhancements. The same applies to accessibility. A website that excludes users or creates avoidable friction is not serving the business well.
Protect SEO during the redesign
A redesign can improve search performance, but only if SEO is planned before URLs and page templates are finalised. Search engines need clear signals about what each page covers and how the new site relates to the old one.
Maintain a URL migration register for every important existing page. Where a page moves, implement a permanent redirect to the closest relevant replacement. Do not redirect large groups of removed pages to the homepage simply because it is convenient. Review page titles, headings, internal linking, image alt text and structured data as part of the build.
Technical SEO also needs quality assurance before launch. Check that staging sites are not indexed, then confirm that the live website is crawlable, secure and free from broken links. Analytics, conversion tracking and search console configuration must be tested, not assumed.
Build a launch plan that includes testing and ownership
Launching a website is a controlled handover, not the finish line. Before go-live, test the site across current browsers and real mobile devices. Check forms, email notifications, payment processes, search functions, CRM integrations, redirects, cookie controls and key calls to action.
Set a launch window with the right people available to resolve issues quickly. Avoid launching immediately before a major campaign, peak sales period or public holiday unless there is a genuine business reason. Once the site is live, monitor traffic, rankings, form submissions, error reports and page speed closely.
The first 30 days provide useful evidence. Visitors may reveal navigation issues, content gaps or unexpected device behaviour that did not appear during internal reviews. Prioritise fixes according to commercial impact rather than personal preference.
A well-planned redesign gives your business more than a fresher appearance. It creates a digital asset that is easier to manage, easier to find and more effective at turning interest into action. When the plan is clear, the design and development work can move quickly with fewer surprises – and the website has a far better chance of earning its place in the business.