How to Audit a Small Business Website Before Redesigning It
To audit a small business website before redesigning it, start with one customer task and follow it from the entry page to the business’s response. Check whether the offer is understandable, the main action works on a phone, the information is credible, and inquiries reach someone who can handle them. Record what you can verify separately from what you think might be causing the problem.
The audit should help distinguish a visibility problem from a content, usability, or operational problem. If you have no reliable traffic or inquiry data, you can still identify unclear information and reproduce broken interactions. You cannot establish how often those issues affect customers or how much revenue a redesign would recover.
Start with evidence and a business goal
Replace “the website needs updating” with a question you can investigate. For example: “Can a homeowner check whether we cover their address and send a request the office can assess?”
Choose a relevant starting page, such as a service page customers arrive on directly. Identify the intended outcome and the person responsible for the next step. Then check your website’s essential requirements against that task.
Gather the evidence you already have:
- Search and website reports, with their reporting periods and any known measurement gaps.
- Recent inquiries, grouped by suitability and the questions customers ask.
- Staff accounts of missed requests, repeated explanations, or unavailable services.
- Reproducible issues, recorded with the page, device, browser, steps, and result.
Remove personal details from material shared for the audit. A short summary of an inquiry problem may be enough; customer messages do not need to appear in a public report.
Separate the stages of the problem
| Diagnostic question | Evidence to review | What it does not establish on its own |
|---|---|---|
| Are relevant people finding the site? | Search queries, landing pages, and acquisition reports | Whether the site explains the service well |
| Do visitors understand the offer? | Page content and observed attempts to find service information | Why every visitor leaves |
| Can customers complete the main task? | Mobile and keyboard walkthroughs, form checks, user observation | Whether staff follow up successfully |
| Does the business receive and handle inquiries? | Agreed test requests, delivery records, assignment, and response process | Whether the visual design needs replacing |
Google’s Search Console Performance report shows search clicks, impressions, and query and page data. Use it to investigate search discovery. It is not a record of completed jobs, and search clicks alone do not explain inquiry quality.
When reports are unavailable, write “not available.” Missing measurement is an audit limitation, not evidence of zero visitors or failed conversions.
Check whether visitors understand the offer
Read the entry page as someone who does not know the business. Can you identify what it offers, whom it serves, where it operates, and what to do next?
Look for the information needed to make a decision, not just whether a section exists. “Serving the local area” may leave coverage unresolved. “Quality solutions” does not identify which jobs the business accepts.
Check that important statements agree across the site. A homepage, service page, and contact page should not give incompatible opening hours or availability promises. Record the exact discrepancy and ask the business owner which information is correct before recommending replacement copy.
Use customer observation to check your interpretation. Give someone representative of the audience a task such as finding the service area, then watch what they do. Record where they look, what they find, and what remains unclear. If you explain the answer during the task, note that assistance rather than treating the attempt as independent success.
Do not turn an unclear heading into an unsupported claim about lost sales. The heading is observable; its effect on decisions still needs investigation.
Walk through the main mobile task
Use an actual phone where possible and record the conditions. A responsive preview is useful for layout checks, but the audit should also consider real interaction with menus, fields, links, and the on-screen keyboard.
Follow the task all the way through:
- Open the relevant entry page and find the service information.
- Locate coverage, availability, or other conditions that affect suitability.
- Start the primary action, such as calling or requesting an appointment.
- Check required fields, correction messages, and the ability to review information.
- Check what happens after submission and who handles the request.
For a business-owned site, coordinate a labeled test request with the team and verify its receipt. If you are reviewing someone else’s site without permission to test delivery, inspect the public experience and mark the delivery step untested.
Also try the main route with a keyboard. Look for visible focus, reachable controls, labeled fields, and content that remains usable when text is enlarged. The W3C Easy Checks guidance provides a starting point for accessibility review. Passing a few checks does not establish that the website is fully accessible.
Use performance tools as supporting evidence
If loading or interaction seems slow, record the affected page and conditions, then investigate. PageSpeed Insights distinguishes controlled lab diagnostics from real-user field data. Check whether field results apply to the specific page or the wider site, and record when sufficient field data is unavailable.
A performance score does not tell you whether the service is understandable or the office answers inquiries. Use the report to identify technical work to investigate, not as a single verdict on the whole website.
Review trust, forms, and follow-up
Check whether customers can verify relevant claims: who runs the business, what work it undertakes, where it operates, and which evidence supports its experience. Record missing context or conflicting information without assuming that a particular badge or testimonial will improve results.
When you review how your website builds trust, connect evidence to the claim it supports. An original project photograph needs enough explanation to show what the business did. A qualification should identify the relevant person or business and be current where that matters.
Review the form as both an interface and a handoff. Are fields understandable? Can errors be corrected? Does the acknowledgment accurately describe what happened? The W3C guidance on form notifications explains how clear error and success feedback can help users understand submission results.
Then check the business process. A visible “Thank you” message does not prove an email was delivered or a staff member accepted responsibility. Verify the destination, owner, and next step separately. An appointment request should not be presented as a confirmed booking if staff still need to review it.
Worked audit: a fictional plumbing website
This example audits one fictional site using the text specimen below. It is an editorial teaching example, not a client project or a test of a live business. No analytics, user recordings, delivery logs, performance measurements, or rendered mobile screens are available. The findings concern the specimen’s content; behavior and business impact remain unverified.
Audit specimen: a service page and quote route
- E1, opening section: “Plumbing for your home.” Supporting line: “Repairs and installations.” Primary action: “Get a quote.”
- E2, coverage section: “Serving the local area.” No named coverage area is included elsewhere in the supplied specimen.
- E3, work section: Two project photographs with no captions. Their origin and permission to publish are not documented.
- E4, quote form: Name, email, and message fields. No service-location prompt or explanation of information needed to assess a request.
- E5, acknowledgment: “Thank you.” No next-step explanation. The submission destination and responsible staff member are unspecified in the supplied material.
Customer task: Check whether the business serves the property and request an estimate for planned work.
| Finding | Evidence in the specimen | Hypothesis or unanswered question | Priority and next check |
|---|---|---|---|
| Broad services and an inquiry action are named | E1 states repairs and installations and offers “Get a quote” | Can intended customers identify whether their particular job fits? | Retain this useful starting point; check understanding before rewriting it |
| Coverage is not specific enough to check an address | E2 uses “local area” without naming it | Customers may need to contact the business just to establish coverage | Address early: confirm actual coverage, add useful information, and test the task again |
| Project photographs lack supporting context | E3 has no captions or documented provenance | Do the images depict this business’s work, and what do they demonstrate? | Verify before publishing stronger claims; add accurate context or replace unsupported material |
| The request does not explicitly ask where the work is needed | E4 contains no location prompt | Would the office need another exchange before assessing suitability? | Investigate with staff; add a location question only if needed for the next step |
| The acknowledgment does not explain what follows | E5 says only “Thank you” | Does the customer know whether to wait, call, or provide more information? | Address early: agree a real process, then make the message describe it |
| Receipt and ownership cannot be established | No destination, delivery record, or owner is supplied | Does a submitted request reach someone responsible? | Verify first: coordinate a test and trace receipt and assignment before concluding that delivery fails |
The example does not prove that the site loses inquiries. It identifies content gaps and a missing operational check. Those are specific enough to investigate without claiming that the entire website needs rebuilding.
Prioritize fixes before choosing a redesign
Give priority to verified issues that block a customer task or produce a misleading result. Where a potentially serious issue is unverified, prioritize checking it rather than reporting it as a confirmed failure.
Use three working categories:
- Verify first: missing evidence about an important function, such as request delivery.
- Fix next: a reproducible blocker or a confirmed information gap relevant to the main task.
- Investigate further: a plausible explanation whose impact or cause is still uncertain.
These are editorial triage categories, not a universal scoring system. Record confidence, effort, and dependencies separately. A small wording change may still depend on the owner agreeing what the business can promise.
Copyable audit record
Start with one row per finding. Add a date, page address, device, and browser to interaction evidence so someone else can repeat the check.
| Page and task | Finding | Evidence or reproduction steps | Hypothesis and confidence | Priority and owner | Proposed change | Verification after the change |
|---|---|---|---|---|---|---|
| __________ | __________ | __________ | __________ | __________ | __________ | __________ |
| __________ | __________ | __________ | __________ | __________ | __________ | __________ |
For example, the coverage issue might produce a scoped action: “The owner confirms the supported locations; the editor updates the service page; a representative customer checks whether their address is covered.” This identifies both the information dependency and a way to review the change.
Keep what already works. After changes, repeat the affected tasks and confirm that unrelated contact routes still function. Review comparable measurement periods when sufficient data is available, accounting for campaigns, seasonality, and changes in traffic quality. An increase after a change does not, by itself, isolate that change as the cause.
Use the resulting evidence to decide between a redesign and targeted fixes. The audit’s output should be a documented problem, its supporting evidence, and the next action needed to resolve or investigate it. That gives the redesign discussion a concrete starting point.
Share your website and the problem you see. Include the customer task that matters and any evidence you already have, such as a repeatable issue or an anonymized summary of inquiry problems.