Before You Redesign a Website: A Practical UX Discovery Checklist

What Should You Check Before Redesigning a Website?

A website redesign usually starts with something that doesn't feel right. The homepage looks outdated. Competitors have cleaner websites. Enquiries are slowing down. Or the team has simply grown tired of looking at the same design. These are understandable reasons to consider a redesign. But they don't necessarily tell you what needs fixing. A website can look dated and still perform its most important tasks well. Equally, a beautiful website can frustrate visitors with confusing navigation, unclear pricing, or forms that are difficult to complete. Before investing in a redesign, you need a clearer picture of what's working, what's getting in the way, and what deserves attention. That's what a UX audit and discovery process provides. This checklist walks through the questions worth answering before your team starts changing layouts, colors, or components.

1. Align on the Business Reason for Redesigning

Before examining individual pages, identify why the redesign is being considered. Ask project stakeholders: • What isn't working with the current website? • What evidence supports that concern? • What should the redesigned website help visitors accomplish? • How will the business know whether the project succeeded? • Which parts of the current experience must be preserved? The answers often reveal that different stakeholders are trying to solve different problems. A marketing team might want more qualified enquiries, while a founder wants a more modern visual identity, and a support team is concerned about customers struggling to find help. All three concerns can be legitimate. But they don't automatically require the same solution.

2. Benchmark Current Website Performance & Analytics

A redesign should begin with a recorded baseline of current website metrics. Otherwise, the team will struggle to determine whether the new design actually improved anything.

• Contextualize metrics: A low conversion rate doesn't automatically prove poor UI design; traffic quality, offer clarity, and pricing all influence results.
• Practical recommendation: Record a 90-day baseline for your most important pages and actions before redesign work begins so post-launch evaluation is meaningful.

3. Audit Critical User Journeys End-to-End

People don't visit websites simply to admire individual pages. They arrive with a specific task they want to accomplish—comparing services, reviewing pricing, evaluating credibility, or starting a trial. A structured UX review follows complete journeys rather than evaluating isolated screenshots. For web apps where user retention hinges on immediate activation, see our step-by-step framework on how to audit SaaS onboarding from signup to first value:

• B2B Service Journey: Homepage ➔ Services Page ➔ Relevant Case Study ➔ Contact Form ➔ Confirmation
• SaaS Product Journey: Homepage ➔ Features Overview ➔ Pricing Comparison ➔ Signup Form ➔ First Product Action
• Is the next action obvious at every step?
• Does the visitor have enough information to make an informed decision?
• Are there unnecessary form fields or redundant navigation steps?
• Can users easily recover from validation errors?
• Does the entire experience function smoothly on mobile devices?

4. Evaluate Navigation and Information Architecture

Navigation problems can make an otherwise well-designed website difficult to use. Visitors shouldn't need to understand your internal company org chart to find relevant information. Review how pages are grouped, named, and connected across viewports:

• Look for overlapping menu categories, unclear labels, deeply buried subpages, and navigation patterns that change unexpectedly between pages.
• Take one important task (e.g. finding service pricing): Starting from the homepage, try to reach the information without using search or prior knowledge.
• Do menu labels match what prospective customers naturally expect?
• For complex websites, consider tree testing or card sorting to validate navigation decisions with representative users.

5. Examine Visual Hierarchy and Content Clarity

Visual design strongly influences which elements visitors notice first. When everything competes for attention, visitors experience cognitive overload and bounce.

• Can a first-time visitor understand the page purpose within 5 seconds above the fold?
• Is the primary call to action visually distinguishable from secondary alternatives?
• Example: If a homepage gives equal visual weight to "Book a Demo", "Start a Trial", and "Contact Sales", establish one clear primary action and de-emphasize alternatives.
• Are headlines informative and benefit-driven rather than cryptic or abstract?
• Is important content easy to scan using descriptive subheadings, bullet points, and high-contrast callouts?

6. Review Mobile Usability Beyond Responsive Layouts

A responsive layout is not automatically a usable mobile experience. A website may technically fit a smartphone screen while still presenting difficult navigation, cramped form inputs, unreadable text, or controls that are awkward to tap. Review key journeys on actual mobile devices, paying close attention to:

• Navigation drawers and multi-level accordion menus.
• Form inputs, virtual keyboard triggers (email, tel, numeric), and tap-target padding (minimum 48x48px).
• Long comparison tables that cause horizontal overflow traps.
• Sticky cookie banners, modal popups, and floating overlays that obscure readable content.

7. Check Accessibility (WCAG) and Technical Performance

Accessibility and performance shouldn't be deferred until after the redesign is built. Carrying low-contrast text, missing focus rings, or script bloat into the new design creates immediate technical debt.

• Review color contrast ratios against WCAG 2.2 criteria (minimum 4.5:1 for body copy).
• Verify visible keyboard focus indicators, form field labels, and descriptive link text.
• Evaluate Google's Core Web Vitals: Largest Contentful Paint (LCP < 2.5s), Interaction to Next Paint (INP < 200ms), and Cumulative Layout Shift (CLS < 0.1).
• Audit third-party scripts: Identify and prune unneeded tracking tags, analytics snippets, and heavy widgets.

8. Protect Existing SEO Value & Plan URL Migration

A website redesign can severely hurt organic rankings if URLs, content, metadata, or internal linking structures are changed without proper planning. Follow these pre-redesign SEO safeguards:

• Reference: Follow official guidance from Google Search Essentials during redesign planning.
• Never delete high-ranking legacy pages simply because they don't fit new aesthetic preferences without establishing permanent redirects.

9. Separate Quick Fixes from Genuine Redesign Requirements

By this stage, you will have a comprehensive list of observations. The challenge is deciding what actually requires a redesign versus what can be resolved with targeted improvements. To establish an objective scoring model across design and engineering, refer to our framework on how to prioritize UX issues:

• Distinguish severity from redesign effort: A critical usability problem doesn't always require rebuilding an entire website.
• A targeted micro-fix can resolve conversion obstacles in days without the cost or timeline of a full site overhaul.

10. The 25-Point Website Redesign Discovery Checklist

Use this 25-point review sheet before approving wireframes or committing engineering resources to a redesign. Once your findings are compiled, consult our guide on essential UX audit deliverables to prepare clear tickets and remediation roadmaps for your team:

• 1. Define the primary business reason and commercial objective for redesigning.
• 2. Identify primary and secondary target audiences and their task goals.
• 3. Agree on the primary conversion metrics that define project success.
• 4. Document stakeholder concerns, assumptions, and must-preserve elements.
• 5. Define criteria and timelines for post-launch ROI evaluation.
• 6. Capture 90-day baseline analytics for traffic, conversions, and bounce rates.
• 7. Identify top revenue-generating entry pages and marketing funnels.
• 8. Audit key visitor journeys from entry to conversion.
• 9. Inspect contact, demo, and checkout forms for interaction friction.
• 10. Record known user complaints, support tickets, and sales feedback.
• 11. Review navigation menu labels, categorization, and hierarchy.
• 12. Assess headlines and content clarity above the fold.
• 13. Check visual differentiation between primary and secondary calls to action.
• 14. Evaluate trust signals, testimonials, certifications, and security markers.
• 15. Identify inconsistent UI component patterns and visual styling debt.
• 16. Test essential user journeys on actual iOS and Android devices.
• 17. Check tap targets (minimum 48x48px) and mobile input usability.
• 18. Review color contrast against WCAG 2.2 AA (minimum 4.5:1 ratio).
• 19. Test full keyboard navigation and visible focus states.
• 20. Identify accessibility issues requiring specialist remediation.
• 21. Benchmark Core Web Vitals (LCP, INP, CLS) and loading speed.
• 22. Inventory all indexed URLs in Google Search Console.
• 23. Map 301 redirects for any altered or consolidated URLs.
• 24. Distinguish high-impact quick fixes from required architectural overhauls.
• 25. Finalize formal redesign brief, technical scope, and validation plan.

Where My Design Audit Fits & Sample Reports

Conducting a manual heuristic audit across dozens of pages can take weeks. My Design Audit accelerates pre-redesign discovery by scanning your website and delivering structured problem cards, visual hotspots, heuristic scores, and prioritized recommendations in minutes. Explore interactive sample audit reports to see how discovery findings are organized: • Browse All Interactive Sample Reports • View the Outseta White-Label Sample Report My Design Audit offers a 14-day trial requiring a payment card. Review subscription terms before starting.

• Explore Interactive Sample Reports
• View Outseta White-Label Agency Report
• View Pricing & 14-Day Trial Details

Frequently Asked Questions About Website Redesign Discovery

Common questions teams ask when preparing for a redesign:

• Should you do a UX audit before redesigning a website? Yes. An audit identifies actual usability friction, establishes priorities, and clarifies scope before committing budget to design.
• How do you know whether a website needs a redesign? If issues are structural, architectural, or content-wide, a redesign is justified. If issues are isolated to forms or copy, targeted improvements are faster and cheaper.
• What is the difference between a UX audit and a redesign? An audit diagnoses current usability problems; a redesign changes the interface to fix them.
• Can a website redesign hurt SEO? Yes, if URLs change without 301 redirects, content depth is lost, or internal links are broken. SEO migration planning is vital.
• Does a UX audit guarantee better conversions? No audit guarantees revenue lift, but it systematically eliminates known conversion obstacles.
• Can you redesign a website without changing branding? Yes. You can overhaul information architecture and usability while preserving established visual branding.