Practical engineering guide
A Practical Website Audit Checklist Before a Redesign
A structured way to review content, performance, accessibility, search visibility, forms, and analytics before changing a website.
Begin with the visitorβs goal
A redesign should solve a user or business problem, not just replace colors. List the important visitor tasks: compare a service, evaluate credibility, find an answer, contact the team, or complete an account action. Review the current paths for each task before proposing a new layout.
Use analytics, support questions, sales conversations, and user testing as evidence. If a page receives little traffic but is essential to a customer journey, do not remove it based on traffic alone.
Inventory pages and content
Create a simple spreadsheet with each URL, its audience, purpose, owner, last-reviewed date, and next action. Mark pages that are duplicated, outdated, empty, or based on temporary sample data.
- Keep pages that answer a distinct user need and are maintained.
- Combine overlapping pages when they offer the same information.
- Update or remove sample listings, placeholder copy, and unsupported claims.
- Redirect retired URLs to the closest useful replacement.
Check the mobile experience
Test key pages on a narrow phone viewport and on a real device if possible. Check that navigation, buttons, forms, tables, and dialogs remain usable without horizontal scrolling. Ensure that the primary action is visible and that text remains readable at default zoom.
Review performance and stability
Measure important page templates, not only the homepage. Inspect image dimensions and formats, unused scripts, slow third-party requests, layout shifts, and server response time. Prioritise fixes that affect frequently used journeys and repeat the measurements after changes.
A performance report is a diagnostic, not a complete user experience review. Confirm that optimisation has not broken menus, forms, analytics, or assistive technology.
Check accessibility and forms
Use the site with a keyboard and verify that focus is visible and follows a logical order. Check headings, labels, error messages, color contrast, alt text, and link purpose. For every form, test valid input, invalid input, network failure, success confirmation, and the privacy notice.
Review search and trust signals
Check that each important page has a clear title, a unique description, a canonical URL, and links from relevant parts of the site. Confirm that robots rules and the sitemap match the pages you intend to publish.
Use accurate company details, contact routes, service descriptions, and examples you can substantiate. Do not publish invented client results, testimonials, listings, or claims to fill space.
Validate analytics and conversion paths
Test that important events are recorded once, consent choices are respected where required, and form submissions reach the intended inbox or database. Follow the journey from landing page to confirmation and verify that every step gives the visitor clear feedback.
Turn findings into a prioritized backlog
For every issue, record the affected page, evidence, user impact, owner, and a way to confirm the fix. Prioritise broken or misleading journeys first, then accessibility and security risks, then improvements supported by user evidence. Re-audit after release instead of treating a redesign as a one-time event.
Have a project that needs a clear plan?
Share your goals and constraints. Rdelab can help turn them into a scoped engineering conversation.
This guide is general information, not legal, security, or other professional advice. Your project requirements and applicable obligations may differ.