Most website redesigns go wrong in the same way. The team starts with how the new site should look instead of what it needs to do, and a few months after launch the site looks fresh while leads are flat and organic traffic has slipped because old URLs were never redirected.
This guide is for founders and marketing or operations leads at small and mid-sized companies who are planning a redesign. The short version: a sound website redesign process runs in eight phases, from setting goals and recording baseline numbers to monitoring results after launch, with SEO protection planned from the first week. Below you will find the signs that you actually need a redesign, what to do in each phase, the mistakes that cost the most, and a checklist table you can copy into your project plan.
Signs it is time to redesign your website
Age alone is not a reason. These are the signals that justify a full redesign:
- Your business has changed. New services, audiences or pricing that the current site does not reflect.
- Visitors arrive but do not convert. Traffic is steady, yet enquiries and sales stay low. Check our guide on why a website is not generating leads before you commit.
- The site is hard to update. Every small change needs a developer.
- It performs badly on phones. Slow pages, tiny tap targets, broken layouts.
- Technical debt is piling up. Outdated plugins, an unsupported theme or a platform that costs more than it is worth.
If only one or two of these apply, a targeted fix may get you most of the gain for far less effort. If three or more apply, plan a proper redesign.
| Option | What changes | Choose it when |
|---|---|---|
| Refresh | Visual styling and copy on key pages | Structure and platform still work |
| Redesign | Structure, navigation, design and content | Your goals or audience have shifted |
| Rebuild | Platform and code, often URLs too | The technology blocks your team |
Phase 1: Set goals and record baseline metrics
Write down two or three goals a redesign can actually move, and attach a number to each. “Look more modern” is not a goal. “Increase demo requests from organic visitors by 25 percent within six months” is.
Then capture a baseline before anyone touches the design. Export at least 12 months of organic sessions, top landing pages, conversions by source and rankings for your most valuable keywords. If conversion events are not set up properly, fix that first with our GA4 conversion tracking guide.
Record your Core Web Vitals too: Google’s metrics for loading, responsiveness and visual stability. A page counts as good when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of page loads (web.dev).
Phase 2: Audit your existing content
Crawl the current site with a tool such as Screaming Frog and list every URL in a spreadsheet with its traffic, conversions and backlinks. Then give each one a decision:
- Keep: performs well and is accurate. Move it as is.
- Improve: right topic, weak execution. Rewrite it.
- Merge: several thin pages on one topic. Combine them.
- Remove: no traffic, no links. Retire it and redirect the URL to the closest relevant page.
This spreadsheet becomes your redirect map, so do it carefully. Give every page you plan to rewrite an owner and a deadline, because late content holds up everything else.
Phase 3: Plan the sitemap and user flows
Draft the new sitemap: the pages and how they are grouped in navigation. Keep the main menu short and use your customers’ words, not internal jargon.
Next, map user flows for your two or three most important visitor types. A user flow is the path from landing on the site to completing a goal. A B2B buyer might arrive on a blog post from search, read a service page, check your portfolio, then book a call.
Then wireframe key pages: simple layouts without colors or images that are cheap to change. Our UI/UX design process guide covers this stage in depth.
Phase 4: Design
Turn approved wireframes into high-fidelity mockups or a clickable prototype, usually in Figma. Design mobile layouts alongside desktop, not afterward, and build a small design system (shared colors, type styles, buttons, form fields) so new pages stay consistent.
Check accessibility now, while fixes are cheap: contrast, font sizes, visible focus states and clear form labels. WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, and Level AA is the usual target (W3C). For help with this phase, see our UI/UX design services.
Phase 5: Build
Start development once designs and key-page content are approved. Building around placeholder text causes rework, because real copy is rarely the same length.
- Platform. Stay on your CMS if it works for your team, or move if it is the bottleneck. A move usually changes URLs, which raises the SEO stakes.
- Staging site. Build on a password-protected staging environment with search engines blocked.
- Performance. Compressed images, few third-party scripts and sensible caching are easier to build in than bolt on.
- On-page SEO. Carry over or rewrite titles, meta descriptions, headings, canonical tags and schema for every page you keep.
If you need a team for the build, our web development services cover React, Next.js and Jamstack sites.
Phase 6: QA before launch
Test the staging site as a visitor would, then as a search engine would.
- Functional: every form reaches the right inbox or CRM, and checkout and search work.
- Cross-device: Chrome, Safari, Firefox and Edge, plus real iOS and Android phones.
- Content: no placeholder text, broken images or dead links.
- Redirects: every old URL returns one permanent server-side redirect (301 or 308) straight to its closest new equivalent, with no chains and no mass redirects to one unrelated page (Google Search Central).
- Tracking: analytics, conversion events and ad pixels fire correctly.
- Speed: run main templates through PageSpeed Insights.
For deeper crawl and indexing checks, use our technical SEO checklist.
Phase 7: Launch
Launch early in the week during working hours, never on a Friday afternoon. On launch day:
- Back up the old site and keep the copy.
- Deploy, then remove the staging noindex tag and password protection.
- Check that robots.txt is not blocking the site.
- Spot-check redirects for your highest-traffic pages.
- Submit the new XML sitemap in Google Search Console.
- Send a test entry through every form.
To redesign without losing SEO, treat redirects as long-term infrastructure. Google recommends keeping them generally at least one year and warns that rankings can fluctuate temporarily during a move (Google Search Central). The full sequence is in our guide to website migration without losing SEO.
Phase 8: After launch
The first 90 days tell you whether the redesign worked.
- Week 1: check Search Console daily for crawl errors and 404s, and add missing redirects quickly.
- Weeks 2 to 4: compare traffic and conversions with your baseline. Google notes a medium-sized site can take a few weeks or more to settle, so look at trends, not single days.
- Months 2 and 3: review heatmaps or session recordings, then test headlines, calls to action and forms.
Report results against your phase 1 goals.
Website redesign checklist by phase
| Phase | Key tasks | Done when |
|---|---|---|
| 1. Goals and metrics | Measurable goals, 12 months of analytics, rankings, Core Web Vitals | Baseline saved, goals signed off |
| 2. Content audit | Crawl every URL, tag keep, improve, merge or remove | Every URL has a decision and owner |
| 3. Sitemap and flows | Sitemap, user flows, wireframes | Wireframes approved |
| 4. Design | Mobile and desktop mockups, design system, accessibility | Prototype approved |
| 5. Build | Staging site, real content, performance, on-page SEO | All pages built with final copy |
| 6. QA | Forms, devices, links, redirects, tracking, speed | No open blockers |
| 7. Launch | Backup, deploy, remove noindex, submit sitemap | Live site verified |
| 8. After launch | Monitor errors, compare to baseline, test changes | 90-day report against goals |
Common mistakes
- Starting with visuals. Picking a look before agreeing on goals produces a prettier site that does the same job as the old one.
- Skipping the redirect map. Missing redirects are a frequent cause of traffic drops after a relaunch, and the phase 2 spreadsheet prevents them.
- Deleting pages that rank. A dated page can still bring steady search traffic or backlinks. Check the data first.
- Leaving the noindex tag on. Staging settings that block search engines sometimes go live by accident.
- Changing everything at once. A new domain, platform, URL structure and content in one release makes it hard to tell what caused a drop. Stage the riskiest changes if you can.
Plan your redesign with a clear checklist
A good website redesign checklist keeps the project tied to business results. Set goals and a baseline, audit what you have, plan structure before visuals, build with real content, test thoroughly, protect search traffic with a complete redirect map, then measure for 90 days.
If you would like a team to plan and build your redesign, from discovery and architecture through to deployment, take a look at our web development services and tell us about your project. We will work through the scope, stack and timeline with you during discovery.
