A well-built FAQ page can serve three goals at once: ordinary search rankings, featured snippets or People Also Ask boxes, and AI-generated citations. It needs real questions customers actually ask, a direct answer in the first sentence, and genuinely useful detail beyond the minimum. FAQPage markup is optional. No one can guarantee a snippet or a citation.
A well-built FAQ page can work for three goals at once: ordinary search rankings, featured snippets and People Also Ask boxes, and AI-generated citations. It does that only if the questions are real and the answers are good. No FAQ page can guarantee any of the three, but a weak one will never earn them.
Start with real questions, not invented ones
The common mistake is writing questions that sound plausible instead of ones customers actually ask. Better sources are:
- the questions you answer by phone, text and email every week
- the People Also Ask box for your target search, which our PAA guide covers in detail
- queries in Search Console that start with how, what, can or do
- objections that come up at quote time
Say a Riccarton physio writes down the five things new patients ask before booking: do I need a referral, how long is the first appointment, what should I wear, does ACC cover this, and can I claim anything on insurance. Those five questions are a better FAQ than twenty invented ones, because each is something a real person has wanted to know.
Answer directly in the first sentence
Google's guidance on featured snippets describes them as concise answers pulled from a page. If your actual answer arrives after three sentences of preamble, there is nothing clean to extract. State it first.
Compare two answers to "do I need a referral to see a physio?"
- "Physiotherapy is a rewarding journey and we are here to help you every step of the way."
- "No, you do not need a referral to see a physio in New Zealand. You can book directly, though some funding routes have their own requirements, so ask us before your first visit."
The second answers, stays honest about the exception, and can be quoted as it stands. Always check the facts in your own answers are current before publishing.
Add detail the competitors skip
A one-line answer helps a snippet but under-serves a reader. After the direct answer, add what only a real practitioner would know: a typical price range with what changes it, how long the job takes, what to prepare, what can go wrong, and when to call someone else. That is the part that builds trust, and it echoes the "helpfulness" Google describes in its guidance on creating helpful content.
Read each answer aloud once. If it sounds like a brochure, rewrite it the way you would explain it to a customer standing in your workshop. Keep promotional lines out of the answers. "Call us on" belongs in your closing paragraph, not inside an answer that you hope someone quotes.
Should you use FAQPage schema?
Be realistic. FAQPage markup labels each question and answer so a machine can see where one ends and the next begins. That is tidy, but Google has scaled back FAQ rich results, so you should not expect a visible reward in the search results. It is also not required for a snippet. For the full picture, see what schema markup actually does.
The practical rule: the visible text must match the markup, every marked-up question must really appear on the page, and you do the writing first. If your site builder adds it easily, fine. If it is a fight, skip it.
Why the same page can suit AI tools
AI tools that cite sources tend to favour pages that state facts plainly, so a clean question-and-answer entry is easy to lift accurately. Writing a page for snippets usually also suits getting cited by ChatGPT, without needing separate content for each. The same caution applies: nobody controls what an AI tool decides to quote, so treat citations as a possible by-product of being clear and useful, not a result to promise.
Where to put it
Two reasonable setups:
- A section on a service page. A Papanui electrician with a switchboard upgrade page can finish it with four or five questions about price, power cuts during the job and certification. This catches people just before they enquire.
- A standalone FAQ page. Useful when the topic is broad, such as everything a landlord needs to know about rental property wiring.
Either way, give every question a proper heading, keep answers under the question directly, and link to your related service page.
Common mistakes
- Using the same templated answers across every location page.
- Repeating the same question five ways to pad the list.
- Hiding answers behind tabs or scripts that crawlers or readers struggle with.
- Never updating answers when prices, rules or opening hours change. An out-of-date answer is worse than none, because it gets quoted.
- Answering a question you cannot genuinely answer better than the next business. Leave it out.
For spoken queries, the same pages also serve voice search, since short direct answers read aloud well.
If you want an FAQ page written from your real customer questions, our AEO service does exactly that. Or begin with a free SEO review and we will show you which questions your site already answers and which ones are missing.
