Planning a Website Redesign: The Complete Guide

Most website redesigns start from a feeling rather than a problem. The site looks dated, a competitor launched something sharper, or the business has changed and the site no longer describes it. Those are legitimate reasons to rebuild. They are not, on their own, enough to produce a site that performs better than the one it replaced.

A redesign is one of the few marketing projects that can measurably damage a business if handled badly. Sites lose their search visibility, enquiry forms break silently, and businesses discover six months later that the beautiful new site converts at half the rate of the ugly old one. This guide covers how to plan a redesign so that does not happen.

Decide what the redesign is actually for

Before anything else, write down what the new site has to do better than the current one. The useful versions of this are specific: generate more enquiries from the same traffic, let the team publish without developer help, support three new service lines, load acceptably on a phone, or stop losing mobile visitors at the booking step.

Vague goals produce vague outcomes. “Modernise the brand” gives a designer nothing to optimise against, and it is why so many redesigns look better and perform worse. If the honest answer is that the site simply looks old, that is worth saying out loud, because a visual refresh is a much smaller and cheaper project than a full rebuild.

Audit what you already have before you throw it away

The single most expensive redesign mistake is rebuilding without knowing what the current site is doing well.

Pull the data first. Which pages bring in organic traffic, and for which searches? Which pages generate enquiries? Which pages does nobody ever see? Where do people drop out of the journey? A site with two hundred pages usually has a handful producing almost all the value, and those pages need to survive the move with their URLs, their content substance and their internal links intact.

This audit also tells you what to delete. Most older sites carry a long tail of pages that exist because someone once thought they should: thin location pages, abandoned blog posts, duplicated service descriptions. Removing them is usually beneficial, but it should be a decision rather than an accident.

Plan the structure around what people are looking for

Site structure is where SEO and usability meet, and it is decided long before any visual design happens.

The principle that holds up is one page per thing someone searches for. If people look for “emergency boiler repair” and “bathroom installation” separately, those need separate pages with enough substance to answer each. Collapsing them into a single services page, which happens constantly in redesigns aiming for a cleaner look, removes your ability to rank for either and forces visitors to do the filtering themselves.

Our article on how many pages a business website actually needs goes into how to decide where the lines fall. The short version is that the number should come from the searches and services, not from a template.

Protect the search visibility you already have

This is the part that goes wrong most often, and it rarely shows up until weeks later.

Every URL that changes needs a permanent redirect to its closest equivalent. Not to the homepage, which is the lazy default and effectively discards the value of the old page, but to the page that serves the same intent. Build the redirect map during planning, not during launch week.

Beyond redirects, keep an eye on the things that carry ranking signals and are easy to lose in a rebuild: page titles and meta descriptions, heading structure, internal links between related pages, image alt text, and structured data. A new site that drops all of these is starting from a weaker position than the one it replaced, even if the design is better.

When rankings fall after a launch, these are almost always the cause. The patterns are covered in why Google rankings drop, and the recovery work usually sits with technical SEO.

Design for the decision, not for the gallery

A business website has a job: help someone work out whether you can solve their problem, and make contacting you easy. Most of the design decisions that matter are about clarity rather than aesthetics.

The homepage should say what you do, who you do it for and where, above the fold, in words a customer would use. Service pages should lead with the problem rather than the process. Proof needs to be specific and visible: real work, real results, real reviews, rather than a row of logos. Contact options should be present wherever a decision gets made, not only on a contact page.

The copy carries most of this weight, which is why writing it after the design is finished tends to produce pages that look right and say nothing. Our article on writing a homepage that explains what you actually do covers the order that works better.

Build for speed from the start

Performance is cheaper to design in than to retrofit. Google’s Core Web Vitals give concrete targets: largest contentful paint under 2.5 seconds, interaction to next paint under 200 milliseconds, and cumulative layout shift under 0.1, measured on real visits.

The decisions that determine whether you hit those are made early: how many fonts and scripts the site loads, whether images are served in modern formats at sensible sizes, how much the page builder adds to every page, and what the hosting can actually deliver. A site assembled from heavy third-party components rarely becomes fast later. If this is already your problem, why websites load slowly and how to fix it covers the usual causes.

Choose a platform you can live with

Platform choice should follow from who maintains the site and what it has to do. A business whose team needs to publish regularly needs something they can actually use. A business selling products needs commerce handled properly rather than bolted on. A business with complex integrations needs a platform its developers can extend.

The comparison most often faced is covered in WordPress versus Shopify. The decision that causes the most regret is choosing a platform because it was cheap to launch on, then discovering it cannot do the second thing the business needs.

Where outside help is worth paying for

Two parts of a redesign reliably repay expertise. The first is the migration plan, because the cost of getting redirects and structure wrong is paid in lost revenue for months. The second is the conversion thinking, because a site that looks professional and does not generate enquiries is an expensive piece of decoration.

Our website design and development work is built around both, and where the project is a WordPress rebuild specifically, WordPress development covers the technical side including the migration.

Before you launch

Run a proper pre-launch check rather than a quick look. Redirects tested, forms tested and arriving in the right inbox, analytics and conversion tracking installed and firing, titles and descriptions in place, the site crawlable, and the staging site blocked from being indexed. The full list is in our website launch checklist.

Then watch the first month closely. Compare organic traffic, rankings for your main terms, and enquiry volume against the same period before. A dip in the first few weeks is normal. A sustained drop is a signal to investigate rather than wait.

Starting a redesign properly

If you are considering a rebuild, the most valuable hour you can spend is before any design work: establishing what the current site does well, what it is actually failing at, and whether a redesign is the right answer at all. Sometimes it is not, and a handful of targeted fixes would produce more than a new site.

Send us your current site and what is prompting the change. We will tell you what is worth keeping, what is genuinely holding you back, and what the project realistically needs to involve.