What a Small-Business Website Needs to Turn Interest Into Inquiries

Give each main service its own page

Someone who needs a water heater replaced or a will drafted wants to know quickly whether you do that, for people like them, where they live. Each main service page should cover:

• What’s included, and common things that aren’t.
• Who it’s for: homes or businesses, the problems you take on, the jobs you refer elsewhere.
• Where you work. Name the towns or areas, matching your Google Business Profile.
• Price guidance. A starting price, a typical range or the factors that move the price. If every job is quoted, explain how quoting works.
• The next step, and how soon you reply.

On whether Google has a preferred word count, its people-first content guidance says: “(No, we don’t.)” Write what the service needs, then stop.

Show proof a stranger can check

Proof is something a visitor could verify: photos of real jobs (with the customer’s permission where needed), license numbers where your trade issues them, insurance, memberships you actually hold, the people who will do the work and how long you’ve been in business.

Quote real reviews as written and link to where they were posted, so readers can see the rest. If you have few, ask every customer the same way; see how to ask for Google reviews without review gating.

The FTC’s rule on reviews and testimonials makes it unfair or deceptive for a business to write a testimonial that materially misrepresents whether the person exists, used the service or had that experience, or, with some exceptions, to publish one it knew or should have known did. Your site’s reviews section also can’t imply it shows most or all submitted reviews while hiding negative ones.

Under the FTC’s Endorsement Guides, a customer story about a central or key attribute of your service is likely to be read as “representative of what consumers will generally achieve.” Don’t present an unusual result as typical. This is general information, not legal advice.

Make contact easy on a phone

Test every contact path on a phone.

• Tap to call. web.dev’s click-to-call guidance: “Wrap all phone numbers in hyperlinks with the tel: schema.” Include +1 and the area code, and show the number in every page header.
• Hours beside the number, including what happens after hours. Match your Google Business Profile; Google draws on public information, including a business’s official website, for profiles.
• The booking tool you already use. Link to it rather than adding a second calendar or a form nobody checks.

Keep the form short and honest

web.dev’s form guidance is blunt: “Don’t ask for data you don’t need.” A name, a phone number or email, the town and a few words about the job are usually enough.

• One field for the full name.
• A visible label on every field. “Don’t use placeholders on their own instead of labels”; placeholder text vanishes once someone types.
• Fields set up so phones show the right keyboard and can autofill name, email, phone and town.
• Required fields marked, with the mark explained.
• Beside the button: who replies, how and by when.

Show a success message only after your system confirms receipt; if sending fails, say so and show the phone number. Send a test inquiry monthly and check that a person gets it.

Make pages fast for real visitors

web.dev’s Web Vitals “good” thresholds are:

• Largest Contentful Paint (LCP), when the main content appears: within 2.5 seconds.
• Interaction to Next Paint (INP), how quickly the page responds to a tap: 200 milliseconds or less.
• Cumulative Layout Shift (CLS), how much the layout jumps: 0.1 or less.

Each is judged at “the 75th percentile of page loads, segmented across mobile and desktop devices,” and a page passes only if it meets all three. PageSpeed Insights and Search Console’s Core Web Vitals report use real-user data from Chrome; lab tests help while building but are “not a substitute for field measurement.”

If a page is slow, start with the heaviest things: large photos, sliders and unneeded third-party scripts. Google says Core Web Vitals “are used by our ranking systems,” but good scores don’t guarantee top rankings. Speed matters because people are waiting.

Cover the accessibility basics

WCAG 2.2 has been a W3C Recommendation since October 2023 (current edition: 12 December 2024). Hand this list to whoever builds or edits your site:

• Labels or instructions (3.3.2, Level A) wherever input is required.
• Error identification (3.3.1, A): the error is “described to the user in text,” not just outlined in red.
• Error suggestion (3.3.3, AA): say how to fix it, for example that the phone number needs an area code.
• Identify input purpose (1.3.5, AA): mark fields with autocomplete values such as name, email, tel and address-level2 (town).
• Target size (2.5.8, AA, new in 2.2): at least 24 by 24 CSS pixels, with listed exceptions. W3C suggests considering the enhanced 44 by 44 (2.5.5, AAA) for important controls; your call link and submit button are obvious ones.
• Contrast and focus: 4.5:1 for regular text (1.4.3) and a visible keyboard focus indicator (2.4.7).

Whether a law requires WCAG of your business is a question for a lawyer.

Measure inquiries, not just visits

In Google Analytics 4, a key event measures “an action that’s particularly important to the success of your business.” Google’s recommended event when someone “submits a form or a request for information” is named generate_lead. Send it when your system confirms receipt or, if a thank-you page loads only after success, create it from that page view without code. Then mark it as a key event; that “doesn’t change historic data,” so do it early. Keep names, emails and phone numbers out: Google requires that “no personally identifiable information” is collected.

A tap on your phone link isn’t a connected call; Google Business Profile’s Calls metric likewise counts call-button clicks. A tap, a form submission and a booked job are three different things, and only the last one pays.

Keep a simple log beside the analytics: calls answered and missed, inquiries, booked jobs and where customers heard of you. Compare your own months, not someone else’s average.

When to do it yourself

Most of these fixes are edits, not a rebuild: a tel: link, hours in the header, a clearer service page, fewer form fields, a key event. If your site works on a phone and you can edit it, start there. Google makes a similar point about search: “If you run a small local business, you can probably do much of the work yourself.”

A rebuild makes sense when the site can’t be changed without a developer, breaks on phones, stays slow after the easy fixes or doesn’t explain your services anywhere. Either way, the business should own the domain, the site and the analytics account.

A self-audit you can do on your phone

Open your site and check:

1. Does each main service have a page with scope, audience, area and price guidance, and could a stranger verify your proof?
2. Does tapping the phone number start a call on every page, with hours shown that match your Google Business Profile?
3. Does the form ask only what you need, with visible labels? Does a test inquiry arrive?
4. Leave a required field empty: is the error explained in text?
5. Does PageSpeed Insights show mobile passing LCP, INP and CLS? With no real-user data, check the lab LCP, CLS and Total Blocking Time.
6. Is a confirmed inquiry a GA4 key event, with calls and booked jobs logged separately?