Collect questions from the work, not a keyword list
Review recent calls, emails and quote conversations. Our recommendation is to note the customer’s wording and the decision behind it. “Do I need to be home?” may really concern access and supervision. “How long does it take?” may refer to the appointment, the work itself or the wait for availability. Those deserve different answers.
Choose questions that occur often or create significant misunderstandings. A new business can start with questions raised during discovery conversations and clearly stated service policies. Avoid inventing a dozen “frequently asked” questions about why your company is the best. A useful section can be short when the main page already explains the service well.
Use a direct answer, then the relevant condition
Illustrative question: “Do I need to move furniture before a painting estimate?” Illustrative answer: “You do not need to move furniture for the initial estimate. We discuss access and any moving arrangements before work is scheduled.” This is sample copy; publish it only if it matches your actual process. It answers the immediate question without using the response as a sales pitch.
For questions with variable answers, identify the variable. Instead of “Every project is unique—contact us”, explain what you need to know and why. Our example: “Job duration depends on the room count and preparation required. After viewing the surfaces, we include an estimated schedule in the proposal.” The customer now understands the next step and its purpose.
Keep FAQs usable and avoid obsolete search promises
Google’s documentation updates state that FAQ rich results stopped appearing in Search from May 7, 2026. Do not buy or create an FAQ section on the promise that FAQ markup will produce that retired display. Our reason for recommending FAQs is practical: a relevant answer can help a visitor assess fit and prepare a more useful enquiry.
If answers expand and collapse, the controls must remain usable. W3C’s disclosure pattern describes button controls with an exposed expanded state and keyboard activation. Ask your developer to implement and test the component. For a short section, always-visible answers may be simpler. Do not hide an essential exclusion only inside a collapsed answer that many customers will never open.
Assign ownership and remove stale answers
Keep a small working list containing the question, approved answer, responsible person and last review date. When your service process changes, update the relevant answer and any other page containing the same commitment. Conflicting cancellation information, preparation instructions or service-area statements create avoidable follow-up work even if each page looks professional.
After a month of using the FAQ, ask whoever handles enquiries which questions still arrive and why. Sometimes the answer is missing; sometimes it is difficult to find; sometimes the customer needs a conversation. Move a crucial recurring answer into the service page instead of continually expanding the FAQ. Its job is to support the decision, not become a warehouse for every paragraph.
Your practical checklist
- Use actual customer wording where possible.
- Identify the decision behind each question.
- Answer directly before explaining conditions.
- Keep essential scope and price information visible.
- Test expandable answers with keyboard controls.
- Review answers when business processes change.
Written with AI-assisted research and drafting, with source checks and editorial review for this guidebook. Platform facts link to official documentation. Examples and recommendations are our own; no client results are implied. Sources reviewed October 8, 2026. About Getting Found Local