A website redesign is one of the few marketing projects that can either lift every number you care about or quietly wipe out years of search traffic. The difference is rarely the design itself. It's the preparation: knowing what the current site does well, protecting what already ranks, and testing properly before anything goes live. This checklist walks through every stage, in the order we follow on real projects.
Before you start: decide why you're redesigning
A redesign without a clear goal tends to become an expensive change of colour. Write down the two or three outcomes the new site must achieve, and how you'll measure them.
| Common goal | How to measure it | Baseline to record now |
|---|---|---|
| More enquiries | Form submissions, calls, bookings | Last 12 months of conversions |
| Better search visibility | Organic clicks and rankings | Search Console clicks by page |
| Easier to update | Time to publish a page | How long edits take today |
| Faster site | Core Web Vitals | Current LCP, INP and CLS |
| Clearer positioning | Bounce rate on key pages, sales feedback | Current engagement by page |
If you can't name a goal, a full redesign may not be the right project. Our guide to 12 signs your website needs a redesign can help you decide.
Stage 1: Audit what you already have
Content and performance audit
- Export every URL from your sitemap or a crawler.
- Pull 12 months of data for each page: organic clicks, conversions and backlinks.
- Tag each page: keep, improve, merge or remove.
- Identify your top performers: the pages that bring most traffic, links or leads. These need the most protection.
Technical audit
- Current page speed and Core Web Vitals
- Crawl errors, broken links and redirect chains
- Structured data in use
- Tracking: analytics, ad pixels, conversion events
- Integrations: CRM, booking, payments, email
A free AI Website X-Ray gives you a quick snapshot of speed, SEO and accessibility before you begin.
Stage 2: Plan structure and content
- Sitemap: decide the new page structure, based on what visitors look for, not your org chart.
- Content plan: list every page, its purpose, its owner and whether content is reused, rewritten or new.
- Messaging: agree headlines and calls to action for key pages before design starts.
- Content deadlines: late content is the most common reason redesigns slip.
Write the copy before, or alongside, the design. Designing around placeholder text creates layouts that don't fit the real story.
Stage 3: Design and build
- Wireframe the key templates first: home, service or product, article, contact.
- Design on real content and test on real phones, not just a large monitor.
- Build on a staging site you can share, with search engines blocked from it.
- Design every state: empty, error, loading and success, not just the happy path.
- Check accessibility as you go, using our WCAG 2.2 checklist.
Stage 4: Protect your SEO
This is where most redesigns lose traffic. Treat it as its own workstream.
Build a redirect map
| Old URL | New URL | Redirect type | Checked |
|---|---|---|---|
| /services/web-design | /services/web-development | 301 | ✓ |
| /blog/old-post | /articles/new-post | 301 | ✓ |
| /team.html | /about | 301 | ✓ |
- Map every old URL with traffic or backlinks to its closest new equivalent.
- Use permanent (301) redirects, and avoid chains. Our guide to 301 vs 302 redirects explains why.
- Don't redirect everything to the homepage; it's treated like a missing page.
Carry over on-page SEO
- Titles and meta descriptions for every important page
- Headings and the core content that ranks
- Structured data, canonical tags and hreflang if you use it
- Image alt text and file names
Stage 5: Test before launch
- Every redirect tested, ideally with a redirect checker
- No broken links (run a broken link checker on key pages)
- Forms send to the right inbox and CRM
- Analytics and conversion tracking fire correctly
- Pages pass Core Web Vitals on mobile
- Staging "noindex" removed from the live site
- XML sitemap updated and valid
- Tested in Chrome, Safari, Firefox and on iOS and Android
Stage 6: Launch and the first 30 days
| When | What to check |
|---|---|
| Launch day | Redirects live, robots.txt correct, sitemap submitted, forms working |
| Day 1–3 | Search Console for crawl errors and 404s; analytics data arriving |
| Week 1–2 | Rankings and organic clicks on top pages versus baseline |
| Week 3–4 | Conversions versus baseline; fix any pages that dropped |
Small dips in rankings for a week or two are normal while search engines recrawl. Sustained drops usually point to a missing redirect, removed content or a technical block. Google Search Console will show you where.
Common redesign mistakes
- Launching on a Friday with nobody available to fix problems
- Removing content that ranked because it didn't fit the new design
- Forgetting tracking, so you can't prove whether the new site performs better
- Leaving noindex on from the staging site
- Changing everything at once (domain, platform, structure and content), which makes problems hard to diagnose
Who should be involved
A redesign touches every part of the business, so agree roles before kick-off.
| Role | Responsibility | Typical time needed |
|---|---|---|
| Project owner | Final decisions, budget, priorities | A few hours a week |
| Content owner | Gathers, writes or approves copy | Significant in weeks 1–4 |
| Subject experts | Check accuracy of service and product pages | Short reviews |
| Sales or customer service | Shares common questions and objections | One or two workshops |
| Marketing | Tracking, campaigns, SEO priorities | Ongoing |
| Agency or developer | Design, build, testing, migration | Full project |
Projects run fastest when one person has the authority to say "yes, ship it".
Questions to ask before signing off the design
- Does the homepage make it obvious what we do, for whom, within a few seconds?
- Can a visitor reach the main action from every key page?
- Have we designed for the phone first, not just the desktop mock-ups?
- Does every important old page have a home in the new structure?
- Are we keeping the content that currently ranks and converts?
- Do the designs meet accessibility standards for contrast, text size and focus states?
- Have we planned how we'll measure success after launch?
If any answer is "not sure", resolve it before development starts. Changing a design is cheap; changing a built site is not.
How we run redesigns at Zelvorm
Our custom business website projects follow this checklist, with the redirect map, tracking and testing built into the plan rather than bolted on at the end. Clients see progress in their Mission Control dashboard, including a live launch forecast.
The short version
Set measurable goals, audit your current site, plan content early, design on real copy, build a full redirect map, carry over on-page SEO, test everything on staging, and watch Search Console closely for the first month. Protect what already works, and the redesign can only add to it.
