What to Do Before a Website Redesign: Audit Checklist

A website redesign often begins with “it looks a little dated,” then quickly moves into discussions about reference sites, colors, and motion. Only after launch does the team discover that old articles lost traffic, form fields were not migrated, advertising landing pages stopped working, and the operations CMS became harder to use.

A redesign audit creates an inventory of assets and problems before design begins. It protects existing SEO and content value while preventing the team from mistaking business problems for visual ones.

01 Record the Business Baseline Before Redesign

Compile 6 to 12 months of visits, organic search, inquiries, downloads, registrations, key pages, and device distribution. Without a baseline, the team can only rely on impressions to judge whether the new site performs better.

Distinguish traffic volume from quality. Fewer visits accompanied by more qualified inquiries may be positive; more visits accompanied by more junk leads do not indicate a successful redesign.

02 Build a Complete URL and Content Asset Inventory

Export every accessible URL, title, status code, traffic metric, backlink, and indexing status, then mark each item for retention, consolidation, update, deletion, or redirection. Include important PDFs, images, and landing pages.

Do not inventory pages from navigation screenshots alone. Orphan pages, campaign pages, and old advertising links are often found outside the site.

03 Audit Information Architecture and User Tasks

Interview sales, customer service, operations, and actual users to identify the information they seek most often, the barriers they encounter, and the workarounds they use. Unclear navigation labels, overly deep product hierarchies, and hard-to-filter case studies usually affect results more than outdated colors.

Write each problem as a task: “Can customers find the right product within three steps?” rather than “Improve the navigation experience.”

04 Verify Technical and Integration Dependencies

Confirm the CMS, forms, CRM, analytics, advertising, payments, search, memberships, multilingual capabilities, domain, and server. Record the owner, data location, API, and migration method for each.

A page may look simple while connecting to several business systems behind the scenes. Dependencies discovered too late are a common cause of development delays.

05 Check SEO, Performance, and Accessibility

Review indexing, canonical tags, redirects, sitemaps, internal links, mobile experience, and Core Web Vitals. Problems already present on the old site should become redesign objectives, not be transferred unchanged to the new site.

Also check basic accessibility issues such as contrast, keyboard operation, form labels, and image alternative text.

06 Turn Audit Findings into Priorities, Not an Issue Repository

Rank findings by business impact, user frequency, technical risk, and cost of change. Search assets that must be retained, core conversions, and compliance issues come first; purely decorative enhancements can wait.

The audit should produce redesign goals, scope, a URL migration map, a content responsibility matrix, and a launch monitoring plan.

Pre-Redesign Audit Checklist

Frequently Asked Questions

Is an audit still necessary if the old site is poor?

Yes. Even a visually outdated site may contain URLs with traffic, backlinks, customer bookmarks, and system integrations. Deleting them directly can cause losses.

Who should lead the audit?

Product or business, design, development, SEO, and content teams should ideally participate. A single role is unlikely to see every dependency.

Is user research needed before a redesign?

At minimum, interview frontline employees and review behavioral data. For business-critical websites, add user interviews or usability testing.

Does all old content need to be migrated?

No. Retain, update, merge, or delete content based on its value, but carefully assess pages with traffic and backlinks before deleting them.

What comes after the audit?

First define redesign goals and scope, then address information architecture, content planning, URL migration, and prototypes instead of immediately designing the homepage.