A website should not answer every possible question. It should answer enough of the right questions that a qualified customer knows whether to call and what will happen next.
Hiding basic information does not reliably create curiosity. More often, it creates another phone call for the office to screen or another reason for the visitor to return to Google.
Start with the questions that determine fit
For a local service business, the most valuable answers are often operational:
- Do you provide the service I need?
- Do you work in my town?
- Do you handle projects of this size or type?
- Do you offer emergency service or schedule normal appointments?
- What should I prepare before requesting an estimate?
- What happens after I contact you?
- Is there a minimum charge, consultation fee, or starting price?
- Are you licensed, insured, certified, or otherwise qualified where that matters?
These answers reduce uncertainty. They also prevent a company from spending time on requests it cannot serve.
Put answers where the question occurs
Do not send every question to one enormous FAQ page. A customer wondering whether you repair existing stone belongs on the repair service page. Someone concerned about disruption needs process information near the project description. A visitor deciding whether to inquire needs response-time expectations beside the form.
A central FAQ page can still help with company-wide questions. But contextual answers are easier to find and more persuasive because they appear at the point of decision.
Be specific without promising what you cannot control
“We respond quickly” is vague. “Requests received during business hours are normally acknowledged the same business day” is useful if the company can consistently do it.
“Most jobs take one day” may be risky when site conditions vary. Explain the variables instead: access, material availability, permitting, weather, and project size. Specificity builds trust only when it is true.
Use questions to improve sales conversations
Good website answers do not replace a skilled conversation. They improve it. The caller can move past “Do you serve Bow?” and discuss the actual project. Staff can link to a page after a call rather than retyping instructions. Owners can notice recurring questions and improve the page.
Create a simple feedback loop. For one month, ask everyone who answers the phone to record questions that callers expected the website to answer. Group them into:
- Missing fact
- Unclear explanation
- Trust concern
- Price or process concern
- Question unique to one service
Update the relevant page, then watch whether the question changes. The goal is not fewer calls at any cost. It is fewer avoidable calls and more useful ones.
Do FAQs still help search?
Google has limited FAQ rich results for most ordinary business websites. That does not make customer questions worthless. Clear answers can improve the page for people and help search systems understand its subject. Do not add repetitive FAQ schema expecting a special result your site is not eligible to receive.
Know what not to publish
Do not expose private customer information, internal security procedures, employee schedules, or details that create safety risks. Avoid giving regulated advice outside your qualifications. For custom work, a range or explanation of pricing factors may be more honest than a fixed quote.
The useful test is simple: would this answer help a good-fit customer make a confident next decision? If so, it belongs on the website even if it never becomes a featured search result.
Which questions should be answered first?
Review the last 20 legitimate calls or inquiries and mark the questions that changed the outcome. Start with questions that determine eligibility, safety, budget, location, scheduling, or preparation.
Use this order:
- 1.Questions that prevent harm or a failed appointment
- 2.Questions that determine whether the company can take the job
- 3.Questions that affect price, timing, or customer preparation
- 4.Questions that establish trust and process
- 5.Background that does not change the next step
A pest-control company should explain whether it handles the pest, whether people or pets must leave, and whether an inspection is required before publishing a long history of the treatment product.
How much should you say about price?
If a fixed price is impossible, explain the estimate process, minimum charge, typical range, or major cost drivers. “Every project is different” is true but incomplete. Customers still need to know whether they are considering a few hundred dollars or a major project.
Do not publish a range that staff immediately contradict. Attach an owner and review date to price-sensitive pages.
What if the answer discourages someone from calling?
That can help when the person is not a fit. A landscaper that does not provide weekly mowing should say so rather than schedule an estimate under a false assumption. “We focus on full landscape installations and do not currently offer weekly lawn maintenance” is respectful and clear.
Maintain a shared list with the question, service, source, frequency, current answer URL, and owner. Each month, add recurring questions, check whether the answer is easy to find, have technicians confirm it, and remove outdated promises.
For regulated, safety-critical, medical, legal, or financial subjects, have the right qualified person review the answer. An owner can collect and draft ordinary questions. A content or web specialist can help when the answers require new site architecture, staff cannot update pages, or inquiry data must be analyzed without exposing private information.
Related reading
Website navigation around customer decisions
What every contractor website should include
Sources
Google: Creating helpful, reliable, people-first content
Before paying for a redesign, audit the questions from your recent calls and inquiries. If you want help turning those questions into clearer website pages, schedule a free strategy call.
