A website redesign UX audit is the evidence-gathering stage before visual concepts, templates, or migration work begin. Its purpose is not to declare the existing site good or bad. It is to identify which experiences create friction, which assets already perform well, and which technical or content dependencies must survive the redesign. A related planning guide is Multi-Location Website Redesign: Local SEO, Templates and Governance.
The best audit connects user experience with business outcomes. It reviews behavior, content, accessibility, information architecture, search visibility, analytics quality, and implementation risk. The result should be a prioritized redesign brief—not a long list of subjective design preferences.
What a website redesign UX audit should answer
Before commissioning research or reviewing screens, define the decisions the audit needs to support. A useful audit should answer questions such as:
- Where do users struggle to find information, complete tasks, or understand the next step?
- Which pages, templates, and navigation paths contribute to leads, revenue, support deflection, or other defined goals?
- Which content is still accurate, useful, and valuable in organic search?
- Which design patterns create inconsistency, accessibility barriers, or unnecessary cognitive load?
- What must remain stable during a content management system or URL migration?
- Which problems should be solved before launch, and which can be monitored after launch?
These questions keep the audit tied to decisions. Without them, teams often produce an inventory of observations but no agreement about priorities.
Measure the current experience before changing it
Use multiple evidence sources because no single method explains the whole experience. Analytics can show that users leave a page, but not always why. Interviews can reveal confusion, but not how common it is. Search data can show demand, but not whether the page satisfies it.
Behavior and conversion data
Start by documenting the measurement setup. Confirm that key events, form submissions, phone interactions, ecommerce actions, downloads, and navigation events are tracked consistently. Review trends rather than treating one short reporting period as definitive.
Useful questions include:
- Which landing pages attract qualified organic, paid, referral, or direct traffic?
- Where do users abandon important flows?
- Which calls to action receive engagement, and are those actions meaningful?
- Do mobile and desktop users encounter different problems?
- Are internal search terms, site errors, and zero-result queries available?
Do not optimize a page solely because it has a high conversion rate. A low-volume page may look efficient while contributing little overall value, whereas a high-traffic page may assist conversions that happen elsewhere.
User research and qualitative evidence
Review customer-support questions, sales objections, stakeholder interviews, usability sessions, session recordings where legally and ethically appropriate, and feedback from people who recently completed a key task. Look for repeated language and patterns, not isolated opinions.
For example, if prospects repeatedly ask whether a service is available in their location, the problem may involve information architecture, content clarity, local page structure, or an incomplete inquiry flow. The correct redesign response is not necessarily a new visual component.
Accessibility and inclusive use
Assess keyboard navigation, focus visibility, heading structure, link purpose, color contrast, form labels, error handling, image alternatives, zoom behavior, motion, and responsive layouts. Accessibility should be considered alongside task completion rather than as a final compliance inspection.
Document the severity and reach of each issue. A keyboard-blocking navigation problem affecting every page deserves different treatment from a minor spacing inconsistency on a low-priority template.
Audit the parts that are easy to lose in a redesign
A redesign changes more than appearance. It can alter URLs, page relationships, metadata, structured data, tracking, content ownership, and publishing workflows. Create a preservation inventory before approving a new sitemap or component system.
Content and CMS inventory
Catalog pages, templates, authors, media, downloadable assets, forms, integrations, taxonomies, redirects, and structured content. Record each item’s purpose, owner, freshness, performance, and proposed disposition.
Classify content as:
- Keep: accurate content that supports users, search visibility, or conversion.
- Improve: useful content that needs clearer structure, updated evidence, or a better task path.
- Consolidate: overlapping pages that create duplication or dilute intent.
- Retire: obsolete content with no continuing audience or business purpose.
- Create: genuinely missing content supported by user or business evidence.
Content decisions should be made before templates are finalized. The article Website Redesign Content Migration provides a related framework for organizing this work.
URLs, redirects, and canonical signals
Export the current URL set and map each page to its future destination. Include pages that receive little current traffic but have backlinks, rankings, referrals, or historical value. A redirect map should specify the old URL, new URL, redirect status, owner, and validation method.
Also record canonical tags, indexation directives, XML sitemap inclusion, pagination behavior, hreflang where relevant, and internal links. A redesign should not assume that a new navigation automatically replaces every important internal relationship.
Structured data and metadata
Inventory title tags, meta descriptions, headings, image alternatives, Open Graph fields, schema markup, author information, and other metadata that supports discovery or interpretation. Preserve valid signals when the underlying content remains, and revise them when the page purpose changes.
Schema should describe the visible, relevant content on the new page. Copying markup mechanically from the old site can create inaccurate or unsupported entities.
Analytics and consent behavior
Document tags, events, data-layer variables, consent categories, dashboards, attribution rules, and third-party integrations. Establish a baseline before implementation so the team can distinguish a real business change from a measurement failure after launch.
Use a practical prioritization model
Audit findings become useful when the team agrees on how to rank them. A simple scoring model can combine user impact, business impact, evidence strength, implementation effort, and launch risk.
| Dimension | Question | Example evidence |
|---|---|---|
| User impact | How seriously does the issue block or slow a task? | Usability findings, support requests, accessibility testing |
| Business impact | Could resolving it affect qualified demand, revenue, retention, or cost? | Conversion paths, sales feedback, service goals |
| Evidence strength | How consistently is the issue observed? | Analytics, research, search data, stakeholder input |
| Effort | How difficult is the change to design, write, build, migrate, or test? | Template dependencies, integrations, CMS constraints |
| Launch risk | What could be lost if the change is implemented incorrectly? | Rankings, tracking, redirects, content relationships |
Do not let effort become the only prioritization factor. A difficult problem may deserve early planning if postponing it would lock the new architecture into a weak pattern.
Separate redesign improvements from preservation requirements
A clear audit distinguishes what should change from what should be protected. This prevents the common mistake of treating every existing element as disposable simply because the visual system is being replaced.
Potential improvements
- Clarify navigation labels using user language.
- Reduce competing calls to action on high-intent pages.
- Make service comparisons, requirements, and next steps easier to scan.
- Improve mobile task flows and form error recovery.
- Standardize components without forcing unrelated content into identical layouts.
- Strengthen page relationships through contextual internal linking.
Potential preservation requirements
- High-value URLs and their closest relevant replacements.
- Content that earns qualified organic traffic or supports sales conversations.
- Accurate redirects, canonical signals, metadata, and schema.
- Analytics events, consent controls, and business-critical integrations.
- Accessible interaction patterns that users already rely on.
- CMS workflows, permissions, and publishing responsibilities that keep content current.
For visual system decisions, connect the website audit to broader design system and communication considerations without allowing brand preference to override evidence about usability or findability.
Connect the audit to the redesign process
The audit should produce deliverables that designers, writers, developers, SEO specialists, and stakeholders can use together. A practical package includes:
- Research summary: methods, limitations, key user needs, and recurring friction.
- Experience map: important audiences, tasks, entry points, decision stages, and exit points.
- Page and content inventory: ownership, performance, status, migration notes, and dependencies.
- Information architecture recommendations: navigation, taxonomy, search, and page relationships.
- Template requirements: content fields, modules, states, accessibility rules, and responsive behavior.
- Technical preservation plan: redirects, canonicals, schema, analytics, integrations, and monitoring.
- Prioritized backlog: decisions, evidence, owners, dependencies, and acceptance criteria.
When these outputs are separate documents with conflicting assumptions, implementation slows down. A shared requirements backlog is often more valuable than a polished audit presentation that no delivery team can act on.
Plan validation before launch
Testing should begin while the redesign is still flexible. Test proposed navigation and page structures with representative users, then validate prototypes for comprehension, task completion, keyboard use, mobile behavior, and content clarity.
Before launch, stage the new site and verify:
- Internal links, forms, search, filters, and interactive states.
- Redirects from the approved mapping, including important legacy URLs.
- Canonical tags, indexation controls, sitemaps, robots directives, and structured data.
- Analytics events, consent behavior, attribution, and third-party integrations.
- Page titles, headings, content, image alternatives, and sharing metadata.
- Performance and responsive behavior across representative devices and connections.
After launch, compare the new site with the baseline. Monitor indexation, crawl errors, redirects, organic landing pages, engagement with key tasks, form completion, search queries, support contacts, and revenue or lead quality where applicable. Avoid making major judgments from the first few days unless there is a clear technical failure; traffic patterns and search systems may need time to stabilize.
Common website redesign UX audit mistakes
Starting with visual critique
Color, spacing, and style matter, but beginning there can conceal deeper problems with page purpose, content hierarchy, or task flow. Establish the evidence and architecture first.
Auditing pages instead of journeys
A page can be usable in isolation while the journey between search result, landing page, proof, form, and confirmation is confusing. Evaluate the sequence users must complete.
Removing low-traffic pages automatically
Traffic alone is not a sufficient retirement criterion. Consider backlinks, assisted conversions, customer use, search demand, and the availability of a genuinely relevant replacement.
Leaving migration until development
Late URL and content decisions create rushed redirects, duplicated pages, incomplete metadata, and preventable launch risk. Migration planning belongs in the audit and information architecture stages.
Changing everything at once
A dramatic redesign can make it difficult to identify which change affected performance. Where practical, preserve known strengths, document major changes, and define post-launch monitoring for the highest-risk decisions.
When to bring in specialist support
Internal teams can often complete a strong initial review, especially when they understand customers and have reliable analytics. Specialist support becomes useful when the redesign spans many templates, locations, products, integrations, legacy URLs, or stakeholders—or when the team needs independent research and technical validation.
The right scope depends on risk. A small brochure site may need a focused task and content audit. A complex or revenue-critical site may require coordinated UX research, content strategy, SEO migration, CMS architecture, analytics engineering, accessibility testing, and post-launch monitoring. The website redesign overview can help frame that broader engagement without replacing the audit decisions described here.
A website redesign UX audit is successful when it gives the team confidence about both sides of the decision: what needs to improve and what must not be lost. Treat user evidence, content, SEO signals, analytics, accessibility, and migration controls as one connected system, then carry the highest-priority findings into design, development, launch validation, and monitoring.
