Run a website audit before paying for a redesign
A redesign changes the surface. An audit helps you decide which conversion problems the new site must actually solve.
Written by LeadPathScore Editorial Team
June 25, 2026
A redesign is exciting because the change is visible. New colours, cleaner pages and modern photography make progress easy to see. The harder question is whether the new website fixes the reason customers were leaving the old one.
An audit gives the redesign a job beyond looking newer. It identifies unclear messages, broken contact paths, weak proof and pages that do not match what people searched for.
Redesign the buying path, not only the surface around it.
Do not redesign without a diagnosis
A new visual style can improve credibility, but it cannot automatically fix unclear positioning, weak proof or a difficult contact process. Document the current problems first so the redesign has measurable jobs to do.
Collect evidence from the current site
Review mobile pages, test forms and calls, note the questions customers repeatedly ask and identify pages where visitors leave. Pair analytics with direct observations instead of treating either as the full story.
Redesign brief template
Turn audit findings into redesign requirements
A redesign brief should describe what the new site must fix, not only how it should look.
Existing problem
What is unclear, broken or hard to use?
Observed evidence
Where did you see the issue: mobile test, form test, analytics or customer question?
Business consequence
How could this reduce calls, quote requests or trust?
Required change
What must the new site include or improve?
Success condition
How will you know the issue is fixed after launch?
Turn observations into requirements
Do not stop at the homepage feels dated. Write what happens because of the problem: mobile visitors cannot see the call button, service-area information is unclear or the quote form asks for details the team does not need. That language gives designers and developers something concrete to solve.
Collect a small set of evidence: analytics, search terms, customer questions, form tests and a recording of someone using the site. You do not need a hundred-page report. You need a prioritised list that connects each change to a customer decision.
Illustrative LeadPathScore finding
What we found
The redesign brief may be missing conversion requirements.
Evidence
The audit identifies friction in the buying path, but the proposed redesign language focuses mainly on appearance.
Why it matters
A new visual design can keep the same lead leaks if the brief does not name them directly.
Recommended direction
Convert each audit issue into a required change before comparing design proposals.
Quick checklist
What to check on your own website
- Test calls and forms before writing the brief
- List repeated customer questions
- Review the site on a real phone
- Identify the highest-value pages
- Define how the new site will be judged
Turn findings into requirements
Write requirements such as show the emergency phone action on every mobile page or place service-area proof above the first quote form. Specific requirements make proposals easier to compare and the finished redesign easier to evaluate.
The bottom line
A redesign should make the business easier to understand and contact. If that outcome is not in the brief, add it before comparing proposals.
Scan your own homepage
See the first lead leaks this guide is talking about
Run the same free scan flow from this article. The result opens a dedicated report link for the submitted homepage.
About LeadPathScore
LeadPathScore publishes practical guides for local service businesses that want clearer websites, stronger trust signals and easier paths to calls or quote requests.
