Website Audit Checklist for Local Business Prospects: opportunora

A website audit for a prospective client should answer one practical question: what is making it harder for a customer to call, book, visit, or request a quote?

That is different from producing a long technical report. Before a sales conversation, you need enough evidence to decide whether the business is a good fit, identify the most important problem, and explain a credible improvement.

Quick answer

Use this website audit checklist in two passes. First, spend five minutes checking whether the business is active, whether you found the correct website, and whether a real customer action is difficult. Only then inspect the site in more detail.

Check these areas:

Business identity and listing accuracy
Mobile usability and primary actions
Service, location, and trust information
Forms, calls, bookings, and other conversion paths
Search visibility and crawlability
Performance, security, accessibility, and technical quality
Content accuracy, ownership, and legal basics

Record the page, evidence, customer impact, and confidence for every issue. A useful audit prioritizes a few verified problems instead of presenting a client with a generic list of everything a website could contain.

Start with a five-minute prospect screen

Do not run a full audit on every business in a lead list. Most candidates should be accepted or rejected with a short first pass.

Confirm that the business is active

Check recent evidence such as current opening hours, recent public reviews or posts, a working phone number, and consistent business details. Save the source and the date you checked it.

A directory entry can remain online after a business has closed. A missing website is not a sales opportunity when the business itself cannot be verified.

Confirm that you found the correct website

Search the exact business name together with its town or service area. Compare the phone number, address, branding, and linked social profiles.

Classify what you find:

No website found after checking the business name, listings, and profiles
Social profile or marketplace page used instead of a website
Parked, expired, broken, or insecure domain
Working website with a clear customer problem
Working website that is already fit for purpose

Do not label a business as having no website only because its map listing has no URL. The site may exist under a different domain or may not be connected to the listing.

Identify the primary customer action

Decide what a visitor is most likely trying to do. Common actions include:

Call the business
Request a quote
Book an appointment
View a menu or price list
Find opening hours or directions
Confirm that a service is available in their area
Check qualifications before making contact

Open the current site on a phone and try to complete that action. If it works quickly and the information is clear, do not manufacture a problem merely to create a pitch.

Decide whether a deeper audit is justified

Continue only when all three statements are true:

The business appears active.
The website status or problem is supported by evidence.
Fixing the problem could improve a meaningful customer action.

This screen prevents you from wasting production time on inactive businesses, false positives, or redesigns based only on personal taste.

Create an evidence log before scoring the site

An audit becomes more useful when someone else can reproduce it. For each issue, record:

The page or source you checked
The date and device used
What you attempted to do
What happened
The customer action affected
A screenshot or exact error where appropriate
Whether the finding is verified or still an assumption

Use neutral language. “The quote button opens a missing page on mobile” is an observation. “The business is losing thousands of dollars” is a claim you cannot make without the business's own data.

Keep assumptions separate from findings. If you suspect the opening hours are wrong because two sources disagree, mark that as a fact to confirm with the owner rather than choosing one source as truth.

Check business identity and local information

Local customers need to know that they found the right business and that it can serve them.

Review the website against public business sources and check:

Business name is consistent
Phone number works and matches the intended location
Address or service area is clear
Opening hours are current where relevant
Main services match what the business actually offers
The correct website is linked from major business profiles
Contact details are easy to find
Duplicate or conflicting locations are explained

Google's Business Profile guidelines explain how business names, addresses, service areas, and categories should represent the real business. Use the official profile and the website together, but treat disagreements as questions for the owner.

A strong audit note connects the inconsistency to a decision:

The website says the workshop closes at 5:00 p.m., while the business profile says 6:00 p.m. Confirm the correct time before publishing a replacement site.

That is safer and more useful than declaring either source correct.

Audit the mobile experience first

Many local customer journeys begin on a phone. Test at least one modern mobile viewport and, where possible, a real device.

First-screen clarity

Without scrolling, can a visitor understand:

What the business does
Where it operates
Who the service is for
What action to take next

A slogan without a service or location may look polished while still forcing a visitor to investigate.

Check whether:

The menu opens, closes, and remains readable
Buttons are large enough to use without precision
Text can be read without zooming
Content does not overflow horizontally
Cookie or promotional banners do not hide essential controls
Forms and booking widgets fit the screen
The browser back button behaves normally

Call, booking, and direction links

Tap the important actions instead of only looking at them.

Phone links should open the dialer with the correct number.
Email links should address the intended mailbox.
Direction links should point to the correct location.
Booking links should load the right service or provider.
Quote buttons should lead to a working form or contact route.

Record the complete path. A homepage button can work while the form it opens fails at submission.

Review services, locations, and trust information

A local business website should reduce uncertainty before contact.

Service clarity

Check whether the site explains:

The main services in plain language
Important exclusions or boundaries
The towns, regions, or radius served
Whether the service is residential, commercial, or both
What the customer should prepare before making contact
What happens after an enquiry

Do not recommend creating dozens of thin location pages. The goal is to answer real service-area questions, not to repeat the same paragraph with a different town name.

Trust claims

List claims that require confirmation, including:

Licenses and professional qualifications
Awards and memberships
Years in business
Guarantees
Insurance
Customer counts
Testimonials and review ratings
Staff names and biographies

A replacement site should not copy an unverified claim simply because it appears on the old one. Ask the owner for the source, current wording, and any limits that need to be stated.

Images and proof

Check whether images are relevant, properly sized, and used with permission. Look for missing images, stretched logos, unreadable text embedded in graphics, and stock photos presented as if they show the real team or premises.

When proof is thin, recommend collecting real project photos, staff information, or process details rather than inventing social proof.

Test every conversion path

The most commercially important audit findings often appear after the first click.

Contact forms

Submit a test only when you have permission or a safe test route. Otherwise, inspect the form without sending it.

Check:

Required fields are clearly marked
The form asks only for information needed at this stage
Validation messages explain how to fix an error
Privacy information is available where data is collected
The success state confirms what happened
The message reaches the correct destination
Spam controls do not trap normal users
The form works with a keyboard

Do not promise that a form reaches the owner unless you verified delivery with them. A success message proves only what the browser displayed.

Booking, checkout, and third-party widgets

Follow the flow far enough to identify dead ends, unexpected account requirements, unavailable dates, unreadable embeds, and broken hand-offs to another domain.

Note where the visitor leaves the website and whether the destination still shows the correct business, service, location, and price.

Measurement

If analytics or conversion tracking is visible, record what appears to be installed. Do not claim that events are accurate without access to the account and a controlled test.

The useful recommendation may be to define the conversion first: successful form submission, completed booking, tapped phone link, or paid order. Tracking every click is not a substitute for choosing a meaningful outcome.

Check search visibility and page structure

A prospect audit is not a full enterprise SEO engagement, but it should catch basic problems that prevent a useful site from being understood or discovered.

Review:

One descriptive page title for each important page
A clear main heading that matches the page purpose
Service and location language used naturally
Crawlable navigation to important pages
Canonical URLs that match the preferred page
A sitemap and robots rules that do not block intended pages
Redirects from old or duplicate URLs where needed
Useful page descriptions for search results
No obvious placeholder, duplicate, or empty pages

Google's documentation on how Search works and technical requirements is a better reference than an automated score alone. A tool can identify a missing title, but it cannot decide whether the page satisfies the customer's question.

Search the business name and its main service with the location. Record what is actually shown, but avoid promising rankings. Search results vary, and a website redesign does not guarantee a particular position.

Check performance and technical reliability

Technical checks should support the customer journey rather than become a list of unexplained numbers.

Loading and responsiveness

Test representative pages with PageSpeed Insights and inspect the site on a normal mobile connection. Google's Core Web Vitals cover loading performance, interaction responsiveness, and visual stability.

Record whether the result uses field data from real visits or laboratory data from a simulated test. Do not present a single test run as a permanent property of the site.

Look for practical causes such as:

Oversized hero images
Video loaded before the visitor requests it
Fonts or scripts that delay visible content
Third-party widgets that block interaction
Layout movement while the page loads
Pages that become unusable when a script fails

Security and domain basics

Check:

The preferred domain loads over HTTPS
HTTP redirects to the secure version
The certificate matches the domain and is current
Internal links do not return obvious errors
Forms do not submit to insecure addresses
Mixed-content warnings are absent
The domain does not redirect through suspicious or unrelated hosts

A browser warning is evidence of a problem. The absence of one is not a complete security audit. Do not claim that a site is secure based on a visual inspection or a basic scanner.

Broken pages and redirects

Test navigation links, primary calls to action, prominent footer links, and any URLs already ranking or receiving links when that data is available.

Record the original URL, final URL, status, and user-visible result. Replacing a site without mapping valuable old URLs can turn a redesign into a collection of 404 pages.

Run a practical accessibility review

Accessibility is broader than passing an automated scanner. Start with simple manual checks and use automation to support them.

The W3C's Easy Checks provide a practical starting point. Review:

Keyboard access to menus, links, forms, and dialogs
Visible focus as you move through interactive elements
Meaningful alternative text for informative images
Labels for form fields
Headings in a logical order
Link text that makes sense out of context
Sufficient text and control contrast
Captions or alternatives for important media
Page zoom without hidden or overlapping content
Error messages that do not rely on color alone

Describe what you tested and what remains untested. A preliminary review should not be sold as a conformance certification.

Check content ownership and launch dependencies

Before proposing a rebuild, identify what the project depends on.

Ask who owns or controls:

The domain and DNS account
Hosting
Business email
Analytics and search accounts
Booking, payment, and form tools
Logo and brand files
Photography and video
Existing copy
Review platform profiles
Legal and policy text

Also list content that needs client confirmation:

Services and service areas
Prices and payment terms
Staff and qualifications
Opening hours
Contact details
Guarantees and regulated claims
Privacy, cookie, refund, and cancellation information

This part of the audit prevents a technically finished website from waiting on an unknown password, missing photograph, or disputed sentence.

Prioritize findings by impact and confidence

A prospect does not need fifty red warnings. They need to understand which problems matter and why.

Score each finding on two dimensions.

Customer impact

3, blocked: the customer cannot complete an important action
2, difficult: the action works but creates avoidable friction or doubt
1, weak: the issue reduces clarity, trust, or quality without blocking the action
0, cosmetic: preference with no demonstrated customer effect

Evidence confidence

3, verified: reproduced directly and documented
2, strongly supported: several reliable sources agree
1, needs confirmation: plausible but requires owner access or context
0, assumption: no adequate evidence yet

Lead with high-impact, high-confidence findings. Put assumptions in a separate question list. Cosmetic preferences should not outrank a broken booking link or incorrect phone number.

Then group the work into:

Fix now: blocks contact, booking, payment, access, or trust
Improve in the rebuild: clearer services, navigation, content, and performance
Confirm with the owner: claims, account access, ownership, and business rules
Consider later: useful enhancements that are not required for launch

Turn the audit into a focused proposal

Your proposal should not repeat the complete checklist. It should summarize the business problem, evidence, proposed outcome, scope, and approval process.

A useful summary can follow this structure:

Customers searching on mobile can find the business, but the quote path fails after the first button and the service area is unclear. The proposed site will provide a working quote route, clearly state the verified service area, and preserve the useful existing pages. Business details and claims will be confirmed before publication.

Connect each deliverable to a finding:

Broken mobile quote flow becomes a tested contact path.
Conflicting opening hours become one approved source of truth.
Unclear service coverage becomes a verified service-area section.
Slow oversized imagery becomes properly sized website media.
Missing ownership information becomes an account handover checklist.

Define pages, features, revision rounds, client inputs, exclusions, timeline, payment stages, ownership, and post-launch support. The companion guide on how to sell websites to local businesses covers the wider process from prospecting through approval and invoicing.

A reusable website audit checklist

Use this condensed version for each qualified prospect.

Prospect fit

Business activity is supported by current evidence
Correct website or website substitute is identified
Primary customer action is defined
Real website problem is verified
Legitimate business contact route exists

Identity and local details

Name, phone, address, and hours are consistent
Services and locations are accurate
Business profile points to the correct website
Important disagreements are listed for owner confirmation

Mobile and usability

First screen explains service and location
Navigation works with touch and keyboard
Text is readable without zooming
Calls, bookings, forms, and directions work
Banners and widgets do not hide essential controls

Content and trust

Main services and boundaries are clear
Service area is understandable
Trust claims have sources or confirmation requests
Images are relevant and usable with permission
Customer questions are answered before contact

Search and technical quality

Important pages have descriptive titles and headings
Navigation, canonicals, sitemap, and robots rules are sensible
HTTPS and redirects work
Main pages avoid obvious broken links and errors
Performance issues are tied to customer impact

Accessibility

Core tasks work with a keyboard
Focus is visible
Images, forms, headings, links, and errors are understandable
Contrast and zoom are checked
Automated results are supplemented by manual review

Delivery readiness

Domain, hosting, email, and platform owners are known
Required access is listed
Content requiring approval is listed
Old URLs that need redirects are recorded
Launch and enquiry paths have acceptance tests

How Opportunora fits the audit workflow

Opportunora is designed around the same evidence-first process. It finds local business opportunities with a reason, keeps source material with the company, generates a site for review, and leaves publishing under the operator's control. The operator still decides whether the prospect is suitable, verifies claims, sets the scope, and obtains approval.

If you want to move from a qualified audit to a private client preview without splitting the work across several tools, you can start a free trial.

Frequently asked questions

How long should a prospect website audit take?

Use a five-minute screen before doing deeper work. A qualified prospect may then justify a focused review of the main customer journey and representative pages. The exact time depends on site size, integrations, access, and the promise you make in the proposal. Do not perform a full technical engagement for every name in a lead list.

Should I give the complete audit away for free?

A concise pre-sales audit can demonstrate that you understand the problem. Keep it focused on a few verified findings and the proposed outcome. Detailed analytics, accessibility, security, content, or SEO investigations can be scoped as paid work when they require specialist testing or account access.

Which website audit issue should I mention first?

Lead with the highest-impact issue you can prove. A broken booking path, incorrect phone number, inaccessible menu, or missing service information is usually more persuasive than a subjective comment about colors or visual style.

Can an automated website audit replace manual review?

No. Automated tools can find certain technical, performance, and accessibility signals, but they do not know whether the business information is correct or whether the customer journey makes sense. Use them as evidence sources inside a manual review.

Should I audit a business that has no website?

Yes, but the checklist changes. Verify that the business is active, confirm that no official site exists, identify the customer's main action, inspect the business's current profiles, and list the facts and assets a new site would need. Do not invent missing details for a preview.