Ask an AI engine something specific — "does X take walk-ins", "can I cancel Y" — and when a business gets quoted, the quoted text is very often a sentence from its FAQ. FAQ pages are quote farms. Most businesses plant the wrong crops on them.
Pick questions people actually ask
The failure mode: FAQs written from the inside out. "What makes us different?" "What is our mission?" Nobody asks an AI that, so those answers never get retrieved.
Source your questions from reality:
- What customers ask your staff — the phone questions, the LINE messages, the pre-sales hesitations. Booking, pricing, timing, coverage, cancellation, requirements.
- What people ask about your category — "is [service] worth it", "how much does [service] cost in [city]", "how long does [service] take". You can answer these credibly even when the asker has never heard of you.
- What people ask when they doubt you — "is [brand] legit", "does [brand] really deliver in [area]". Answer them plainly on your own site, because if you don't, the engine assembles an answer from whatever else it finds.
Five real questions beat twenty invented ones.
Write answers that survive being lifted
An engine lifts one answer at a time, without the surrounding page. So each answer must work alone:
- Restate enough context. Not "Yes, we do." but "Yes — we accept walk-ins at both Bangkok branches, though bookings get priority after 6pm." A reader who sees only this sentence still knows who, where, and what.
- Two to four sentences. One-word answers carry no information; essays get truncated or skipped.
- Concrete facts over reassurance. Hours, prices, areas, timelines, conditions. "We respond within 24 hours" is quotable; "We pride ourselves on responsiveness" is not.
- Only facts you can stand behind. FAQ answers get quoted verbatim, so a wrong number on this page becomes a wrong number in AI answers about you. If a detail changes often, state it more loosely or point to where the current value lives.
Mark it up — on the right page
Add FAQPage structured data (JSON-LD) listing each question and answer. Two rules we enforce on every project, both learned the hard way:
- The schema goes on the page that shows the Q&A — not into a shared site-wide template. We once saw FAQPage markup injected into a shared layout put the same homepage questions on 218 pages of a client site. Search and AI systems treat that as markup spam.
- The schema must mirror the visible content. Same questions, same answers, same language as what a human sees on the page. Markup describing invisible content is a trust liability, not an optimization.
One honest caveat
FAQPage markup makes your Q&A parseable; it does not make it chosen. What earns the quote is the answer itself — specific, self-contained, verifiable. Write the answers first as if the schema didn't exist, then wrap them. A great FAQ with no markup beats perfect markup around empty answers.