A website redesign audit is a structured review of your current site before you change its visual design, content structure, technology, or user experience. Its purpose is not simply to find pages that look dated. It is to identify what is working, what is limiting performance, what must be preserved, and what could be lost during the redesign.
The most useful audit covers six connected areas: business goals, UX and accessibility, content and information architecture, SEO and technical signals, analytics and conversion paths, and CMS or migration requirements. Reviewing these areas together helps your team make informed trade-offs instead of treating the redesign as a purely visual project.
For broader context on how the work fits together, see the website redesign process.
What a website redesign audit should answer
Before approving a new design direction, the audit should answer practical questions such as:
- Which business outcomes should the redesign improve?
- Which pages, templates, journeys, and features currently perform well?
- Where do users encounter friction or uncertainty?
- Which content, URLs, metadata, structured data, and backlinks need protection?
- What should be removed, consolidated, rewritten, migrated, or rebuilt?
- How will success be measured after launch?
This makes the audit a decision document, not just a list of defects. Every finding should connect to an impact, recommendation, priority, and owner.
1. Start with goals, audiences, and constraints
A redesign can have multiple stakeholders, but it still needs a clear hierarchy of goals. Document the primary business objective and the user actions that support it. For example, a B2B site may need to generate qualified inquiries, explain complex services, support sales conversations, and improve recruiting. These objectives can influence different parts of the experience.
Record the main audience segments, their buying questions, and their level of familiarity with your offer. Then identify constraints that could affect recommendations:
- Launch deadlines, campaign dates, or seasonal requirements
- CMS, hosting, CRM, marketing automation, or ecommerce dependencies
- Legal, accessibility, security, or compliance requirements
- Internal publishing capabilities and approval workflows
- Existing integrations, custom functionality, or technical debt
Without this context, teams often optimize for subjective visual preferences rather than measurable business and user needs.
2. Review UX, navigation, and accessibility
Evaluate the site as a user would, starting with the highest-value journeys. Common paths include arriving from organic search, learning about a service, comparing options, submitting a form, contacting sales, or locating support information.
Navigation and information architecture
Check whether labels are understandable, menus reflect user priorities, and important pages are reachable without excessive clicking. Review the relationship between global navigation, utility navigation, footer links, breadcrumbs, category pages, and calls to action.
Look for duplicated destinations, orphaned pages, unclear parent-child relationships, and terminology that makes sense internally but not to customers. A redesign may need a new navigation model rather than a new menu style.
Page-level experience
Sample representative page types rather than reviewing only the homepage. Include service pages, landing pages, blog or resource pages, contact flows, search results, and any authenticated or transactional experiences. Assess:
- Clarity of the value proposition and next step
- Content hierarchy and scanability
- Consistency of components and interaction patterns
- Form length, error handling, and confirmation states
- Mobile behavior and touch target spacing
- Loading states, empty states, and error messages
Accessibility
Include accessibility in the audit before visual direction is finalized. Review heading structure, keyboard navigation, focus visibility, color contrast, alternative text, link purpose, form labels, motion, and responsive behavior. Automated checks can identify some issues, but manual keyboard and screen-reader testing may reveal problems that tools miss.
Accessibility findings should be prioritized by user impact and implementation effort. They should also become acceptance criteria for the new design system and templates.
3. Audit content and information architecture
Content is one of the largest sources of redesign risk. A new interface cannot compensate for unclear positioning, outdated claims, thin explanations, or missing decision-stage information.
Create a content inventory that records each important URL, page type, topic, business owner, status, traffic, conversions, backlinks where available, and recommended action. Useful actions include:
- Keep: The page is accurate and valuable with limited changes.
- Improve: The page has potential but needs clearer messaging, structure, or evidence.
- Consolidate: Several pages overlap and should become one stronger destination.
- Redirect: The page should be retired with a relevant replacement.
- Remove: The page has no useful successor and should not remain indexed.
- Create: A missing topic or journey requires a new page.
Review whether page titles, headings, calls to action, internal links, and supporting media align with user intent. Check for outdated screenshots, inconsistent terminology, duplicate copy, unsupported claims, and content that depends on a subject-matter expert who is no longer available.
A redesign should also define content governance: who owns updates, which fields are required, how redirects are requested, and how new pages follow the approved structure.
4. Protect SEO during the redesign
SEO preservation should be planned before templates and CMS migrations are finalized. A visually improved site can lose visibility if valuable URLs, content, internal links, or technical signals are changed without a controlled plan.
URL and redirect mapping
Build a URL map comparing current destinations with their planned replacements. Identify pages that will change paths, pages that will be consolidated, and URLs that will be removed. Each retired URL should have a relevant successor when one exists. Avoid sending large groups of unrelated URLs to the homepage.
Plan one-to-one permanent redirects, update internal links, and test for redirect chains and loops. Keep the mapping available as a launch and post-launch reference.
Canonical and indexing controls
Document current canonical behavior, indexability directives, XML sitemaps, robots.txt rules, pagination where relevant, and any staging protections. Confirm that the new templates will preserve or intentionally revise these signals.
Pay particular attention to faceted navigation, filtered URLs, duplicate template pages, trailing slash conventions, parameter handling, and staging environments that could accidentally become crawlable.
Structured data and search appearance
Inventory existing structured data and determine which types remain accurate after the redesign. Validate organization, website, breadcrumb, article, product, local business, or other applicable markup against the content actually visible on the page. Do not add schema solely because it is available; it should represent the page accurately.
Also review title tags, meta descriptions, heading structures, image alternatives, internal linking, and XML sitemap inclusion. The audit should distinguish between technical preservation and intentional SEO improvements.
5. Review analytics, conversions, and measurement
Analytics can reveal which pages matter even when stakeholders disagree about their importance. Before changing the site, document current measurement so the redesign does not erase useful comparisons.
Audit analytics properties, tag management, consent behavior, event names, conversion definitions, form tracking, phone or chat tracking, campaign parameters, and reporting dashboards. Separate primary conversions from secondary engagement signals such as downloads, video plays, or navigation clicks.
Identify gaps between what the business considers a conversion and what the analytics setup records. If a form generates a lead but only the thank-you page is tracked, confirm that the measurement remains reliable after the new interaction is implemented.
Establish a baseline for important metrics before launch. The baseline should include the relevant date range, traffic segments, device types, landing pages, conversion actions, and attribution assumptions. This prevents teams from judging the redesign on one unusually strong or weak week.
6. Assess CMS, technology, and migration requirements
The audit should explain how the existing site is built and what the redesign will change. Document the CMS version, hosting environment, themes or frameworks, plugins, integrations, custom fields, reusable components, and editorial workflows.
Ask whether the current system supports the content model the new experience requires. A design that depends on flexible page sections may be difficult to maintain if editors must request developer support for every update. Conversely, excessive flexibility can produce inconsistent pages, poor performance, and governance problems.
Review technical dependencies such as:
- Forms, CRM connections, payment tools, and marketing automation
- Search, filtering, personalization, or account functionality
- Image processing, video delivery, fonts, and third-party scripts
- Authentication, permissions, backups, and deployment workflows
- Performance budgets and Core Web Vitals considerations
For implementation planning, the web development team or partner should receive this dependency inventory before technical estimates are finalized.
7. Create a risk-based audit scorecard
A scorecard makes findings easier to prioritize. Score each area by user or business impact, implementation effort, and launch risk. A simple four-level model can work:
| Priority | Meaning | Typical response |
|---|---|---|
| Critical | Likely to cause material loss, failure, or compliance risk | Resolve before launch or formally approve an exception |
| High | Significant UX, SEO, measurement, or operational impact | Include in launch scope with a named owner |
| Medium | Meaningful improvement but not launch-blocking | Schedule for the first optimization cycle |
| Low | Polish, convenience, or low-impact refinement | Backlog for later consideration |
Do not score findings only by how visible they are. A small redirect error or broken conversion event may matter more than a prominent visual inconsistency.
8. Decide what belongs in the redesign scope
After the audit, separate recommendations into four groups: must preserve, must fix, strategic opportunities, and out of scope. This prevents the redesign from becoming an unlimited collection of requests.
For each proposed change, record the problem, evidence, expected benefit, dependency, effort, and acceptance test. If a recommendation changes navigation, content, CMS behavior, analytics, or SEO, identify the related workstreams rather than treating it as a design-only task.
It is also useful to distinguish a design refresh from a broader rebuild. A refresh may retain the platform, URL model, and content architecture while improving interface patterns. A rebuild may involve new templates, a new CMS, content migration, integrations, and a different information architecture. The distinction affects budget, schedule, testing, and risk. For a deeper comparison, read website redesign vs. rebuild.
9. Turn audit findings into a launch and monitoring plan
The audit is incomplete if it ends when the new design is approved. Convert the findings into launch requirements and a monitoring checklist.
Before launch
- Approve the URL and redirect map.
- Complete content migration and review representative templates.
- Validate forms, integrations, analytics events, and conversion paths.
- Test responsive layouts, accessibility, performance, and browser behavior.
- Check canonicals, indexability, structured data, internal links, and XML sitemaps.
- Confirm backups, rollback procedures, permissions, and launch ownership.
After launch
- Test priority URLs, redirects, forms, navigation, and tracking in production.
- Monitor crawl errors, indexation, organic landing pages, and unusual traffic changes.
- Review conversion quality, not only conversion volume.
- Collect support, sales, and user feedback about newly introduced friction.
- Compare performance with the pre-launch baseline after a suitable period.
- Prioritize fixes and experiments based on observed evidence.
Use the website redesign checklist as a companion when translating the audit into project tasks.
Website redesign audit checklist
- Business goals and audience priorities are documented.
- Key user journeys and page types have been reviewed.
- Accessibility and responsive behavior are included in testing.
- Content inventory decisions are assigned to owners.
- URL changes, redirects, canonicals, and sitemaps are mapped.
- Structured data and on-page SEO elements are reviewed.
- Analytics, events, forms, and conversion definitions are baselined.
- CMS, integrations, permissions, and migration dependencies are documented.
- Findings are prioritized by impact, effort, and risk.
- Launch validation and post-launch monitoring have named owners.
Final decision: redesign, rebuild, or improve in stages?
A website redesign audit should give decision-makers enough evidence to choose the right scope. If the current platform and architecture are sound, a focused redesign may address the most important experience problems. If content structure, technology, measurement, and SEO foundations are also failing, a broader rebuild or staged program may be safer.
The goal is not to change everything. It is to make deliberate changes while preserving the assets that already support visibility, trust, usability, and revenue. When the audit identifies a need for a larger redesign engagement, review the website redesign service page for the appropriate next step. For visual system considerations that cross into brand expression, the design overview provides additional context.
