Follow one customer task on mobile, record what you can verify, and propose a scoped website fix without inventing lost bookings or revenue.
A useful mobile audit follows one customer task from the service page to a call, booking, or quote request. Record where the path works, where it stops, and what you could not verify. A low speed score or a missing homepage button does not tell you how many customers a business has lost.
For a web agency or freelancer, this creates a smaller and more credible proposal: fix one observed problem and agree how to test the result.
Pick one service and one intended action. Examples include asking a plumber for a quote, enquiring about a dental appointment, or checking a gym's trial-session process. These are task examples, not a claim that one industry is the best niche.
First verify the business and branch. Then record the page URL, service, device or viewport, browser, date, and entry point. A homepage check and a service-page check are different observations.
For a fictional Harbour Plumbing, your task might be: “From the leaking-tap service page on a phone, find how to request a non-urgent quote.” Do not create a real job or send a test request to an unsuspecting prospect.
| Step | Check | Record |
|---|---|---|
| Service page | Is the service and coverage area understandable? | Exact page and any missing information |
| Call to action | Can you find Call, Book, or Request a quote? | Button text, position, and destination |
| Contact route | Does the link open the intended form or provider? | Working destination, error, or uncertain redirect |
| Mobile form | Are labels, fields, and validation usable? | A specific obstruction, not “bad UX” |
| Submission | Can receipt be verified with permission? | Not tested, or owner-confirmed test result |
Opening a telephone link is different from placing a call. Loading a booking page is different from completing a booking. Reaching a success screen is different from confirming delivery to the business. Keep those steps separate in the report.
If testing requires a submission, agree it with the business first. Use its designated test route or a clearly labeled authorized test, and have the owner confirm receipt. Avoid reserving a real appointment or triggering a customer's operational workflow just to gather sales material.
No link found on checked pages. Name the pages. Ask whether there is another route before proposing a replacement.
Link opens. You reached a form or booking provider. This verifies the destination, not the whole process.
Usable flow observed. You could read the fields and navigate the permitted steps. Record which steps you stopped before.
Owner-confirmed delivery. An authorized test reached the expected destination and the owner confirmed it. Record the test conditions without publishing personal details.
These statuses help prevent a common leap: turning “there is no Book Now button on the homepage” into “you are losing bookings every night.” The first may be observable. The second needs traffic, customer behavior, and business outcome data.
Use a mobile performance test to investigate loading or interaction problems. Save its URL, date, and test conditions. A lab score can vary and does not measure the website's enquiry conversion rate.
Google's page-experience guidance recommends considering the overall experience, including mobile usability and Core Web Vitals. It does not turn a good score into guaranteed search placement or sales.
Treat AI-answer readiness the same way. You can inspect readable service information, contact details, crawl access, and truthful structured data. Those checks do not measure actual AI citations. Google's AI-features guidance says its normal SEO fundamentals apply; it does not require a special AI text file or special schema.
For the fictional plumbing example, a useful finding is:
On the mobile leaking-tap page, the quote button opens an error page. The main contact page loads, but I did not submit a request.
A scoped proposal could be: repair that button's destination, make its label clear, and check the form on the agreed phone sizes. Acceptance means the link opens the right form and an authorized test is confirmed in the intended inbox. It does not mean a promised number of leads.
Ask the owner what happens after a request arrives. Who responds? What information do they need? A website change that increases requests is not useful if the business cannot handle or qualify them. Do not invent an answer from a public-page scan.
A template preview can make a proposed layout easier to review. Label sample text, proposed features, and placeholder content clearly. A drawn booking button is not an installed booking integration, and a displayed testimonial must not imply an endorsement that does not exist.
MyLeadBots provides audits, draft pitches, and template previews for local-business prospecting. Use them as material to review against source pages and the owner's answers. See a fictional template preview, compare the broader website audit checklist, or check pricing and credits before starting a campaign.
How agencies and freelancers auto-generate demo sites for dental and local prospects in 2026, which tools fit, and how a demo turns a cold pitch into a yes.
A practical website audit checklist that finds conversion, trust, mobile, and local SEO gaps—and turns each signal into a sales pitch local owners understand.
A practical checklist for web agencies to catch same-name businesses, wrong branches, and unverified contacts before turning an audit into outreach.