How to Redesign a Website: A Complete Step-by-Step Guide

First, work out what is actually wrong

"The site looks dated" is a symptom, and acting on it directly produces a better-looking site with the same underlying problems. Spend an hour establishing which of these you have, because they need different responses.

If visitors arrive and leave without going deeper, you may have a relevance problem — the page is not about what they searched for. If they go deeper but never convert, the journey is probably unclear. If they convert at a reasonable rate but you are embarrassed to send people to the site, you have a presentation problem, which is the cheapest kind to fix.

Your analytics will answer most of this. Landing pages with high exit rates, funnel steps where people drop, and the search queries bringing people in are all more informative than opinions about the design.

Decide the scope honestly

There are three sizes of this project and conflating them is the most common way redesigns overrun.

A refresh changes how the site looks and leaves structure and content alone. A redesign reconsiders how the content is organised and presented. A rebuild replaces the underlying platform as well. Each is roughly an order of magnitude more work than the one before.

Most sites that people feel bad about need a refresh. Choosing a rebuild because the site "needs sorting out" is how a two-week job becomes a six-month one that stalls.

Inventory your content before you touch the design

List every page, with its traffic, its conversions and a decision: keep, rewrite, merge or delete. This is tedious and it is the step that saves the most pain later.

It tells you how big the project really is, it stops you rebuilding pages nobody visits, and it produces the URL map you will need at launch. Sites almost always have fewer pages worth keeping than expected, and finding that out early is a gift.

Pay particular attention to pages with external links pointing at them. Those pages carry authority that is expensive to replace, and they should survive the redesign with their URLs intact even if their content changes.

Structure before surface

Decide what pages exist and how they connect before deciding what they look like. Navigation is a content decision that gets treated as a design one.

A practical test: can someone who has never seen the site name the thing you sell within five seconds of the homepage, and reach the page for it in one click? If not, no amount of visual work fixes it.

Keep the top-level navigation short. Sites accumulate menu items the way garages accumulate boxes, and a nav with eleven top-level entries is a nav nobody reads. Anything that is not a route people actually take belongs in the footer.

Then the design, and how to review it

Review designs against your real content, not placeholder text. Layouts that look balanced with lorem ipsum fall apart against a nine-word product name and a testimonial that runs to sixty words.

Review on a phone first. Most sites now take the majority of their traffic on mobile, and reviewing a desktop mockup on a large monitor is reviewing the minority case.

And be careful about consensus. Design by committee reliably produces a page where every stakeholder's section is above the fold, which means nothing is emphasised. One person should hold the decision, informed by the others.

Build, then check the things nobody drew

Designs describe one state at one width. The build has to handle everything else, and this is where quality is actually determined.

Check what happens between the breakpoints someone designed for — the awkward middle widths where columns are too narrow for their content but not yet stacking. Check hover, focus and disabled states on every interactive element; focus states in particular get removed for looking untidy and their absence makes the site unusable by keyboard.

Check the empty and overflow cases: a heading that runs to three lines, a price with four digits, a product with no image, a form that has been submitted with errors. These are never in the design file and they are most of what users encounter.

Launch carefully, then leave it alone for a bit

If URLs are changing, every old one needs a 301 redirect to its actual replacement — not to the homepage, which search engines treat as a soft 404. Regenerate and resubmit your sitemap, confirm the production robots.txt does not carry a staging block, and check that analytics fires on every template.

Then resist changing things for a couple of weeks. Rankings and behaviour metrics move after a launch regardless of quality, and reacting to the first week's numbers means reacting to noise. Give it a month before drawing conclusions, and watch Search Console's indexing report for genuine mechanical errors in the meantime.