Website Redesign Checklist: What to Audit Before You Touch the Design

A redesign should not begin with colours, fonts or a new homepage mock-up. Before changing the visual layer, you need to understand what the current site is doing well, where it is failing and what you cannot afford to lose. That means auditing the website before the design phase starts.

Teams that skip this step often rebuild the same structural problems in a prettier skin — or delete pages that were quietly generating inquiries. A short, disciplined audit keeps website redesign work connected to business outcomes instead of taste alone.

Why audit before design

Design answers “how should this feel and guide attention?” The audit answers “what must this system continue to do?” Without the second answer, stakeholder feedback becomes a sequence of aesthetic preferences with no baseline.

An audit also surfaces whether you need a full redesign, a conversion-focused refresh, a content restructure, a platform change — or several of those in combination. Not every complaint about the website requires the same remedy.

1. Benchmark the current site

Capture a snapshot you can compare after launch:

• Organic sessions and landing-page traffic (at least 3–6 months if available)
• Top converting pages and form or call events
• Key rankings or Search Console queries for priority services
• Backlink profile highlights for important URLs
• Core Web Vitals or practical speed notes on key templates
• Lead quality notes from sales (even qualitative)

These numbers become the baseline. Without them, it is difficult to tell whether the redesign improved the business or simply changed how the site looks.

Document seasonality. A spring spike or a campaign-driven month can distort “before vs after” if nobody notes the context.

2. Inventory every important URL

Export the current URL set — crawl the site rather than relying on the navigation alone. Orphaned pages can still carry traffic or links.

For each URL, mark roughly:

Pages with traffic, links, conversions or strategic value deserve explicit decisions. A redesign without a URL inventory is how valuable pages get accidentally orphaned or deleted. Pair this with the website migration checklist once build work begins.

3. Audit content and messaging

Review whether service pages still match what you sell, who you sell to and how buyers evaluate you. Look for:

• Outdated offers, markets or proof
• Homepages that try to say everything at once
• Service pages that are thin or duplicated
• Missing answers to common sales questions (process, fit, timeline, what happens next)
• Inconsistent naming between sales language and site language

Content debt is one of the most common reasons a “new design” still underperforms. If the words are unclear, better typography will not fix them.

4. Audit the user journey

Review navigation, mobile behaviour, calls to action, forms and the path from a service page to a qualified inquiry. If session recordings or heatmaps exist, watch real behaviour on mobile and desktop.

Questions worth answering:

• Can a first-time visitor find the primary service in two clicks?
• Do forms ask for more than the sales team needs at first contact?
• Are CTAs generic (“Learn more”) where a specific next step would convert better?
• Does the mobile experience bury contact or make forms painful?

The redesign should remove friction that is visible in behaviour, not only friction somebody assumes exists.

5. Review conversion and tracking

Confirm analytics is installed correctly, key events fire and conversion definitions match how the business actually works. Broken tracking is common on older sites — and dangerous during a redesign, because you lose the ability to validate the new site.

Check thank-you pages, spam patterns, phone-click tracking and whether marketing and sales agree on what a “lead” means. Redesigning without trustworthy measurement guarantees arguments later.

6. Review the technical foundation

Check page speed, rendering, tracking, forms, integrations, accessibility basics, security, hosting and the current CMS or framework. The new stack should solve actual limitations.

Replatforming for its own sake creates migration risk without necessarily creating business value. Ask:

• What can the current platform not support that we need?
• What maintenance pain is real vs anecdotal?
• Will a new stack require new training or vendor dependency?

7. Competitive and search context

You do not need a 40-page competitor report. You do need a clear view of how peers structure services, proof and inquiry paths — and which search intents matter for your priority offers. That informs sitemap decisions before wireframes lock in the wrong hierarchy.

If organic structure is already weak, the redesign is the moment to fix service-page architecture, not to recreate a single overloaded homepage. See also 12 signs your business website needs a redesign.

Common audit mistakes

• Starting mood boards before the URL and analytics inventory
• Treating “new brand guidelines” as a substitute for journey and SEO review
• Deleting blog or resource URLs without checking traffic and links
• Planning visual novelty while leaving the same unclear service taxonomy
• Skipping mobile form testing because “we’ll handle responsive later”

Turn the audit into a brief

Finish with a written set of priorities in four buckets:

1. Protect — URLs, content and conversions that must survive
2. Remove — pages, modules and tech that create noise or cost
3. Improve — journeys, copy, speed and proof that stay but need work
4. Create — new pages or capabilities the current site lacks

That document becomes the redesign brief. It keeps design decisions connected to measurable objectives rather than preference alone, and it gives every stakeholder a shared definition of success before the first concept is presented.

Pre-design checklist (print this)

• Analytics and Search Console access confirmed
• Traffic, conversion and top-landing baselines saved
• Full URL crawl exported and prioritized
• Keep / merge / redirect decisions drafted for important pages
• Mobile journey and form friction notes captured
• Tracking and lead-definition gaps listed
• Platform constraints and integration requirements written down
• Protect / remove / improve / create brief agreed by stakeholders

Complete that list before anyone opens Figma. If an item is still fuzzy, resolve it in discovery — not during visual revisions — so the redesign starts with evidence instead of assumptions.