FAQs that get quoted

Why FAQs suit AI answers

Query fan-out turns one customer question into several narrower ones. Many of those narrower questions are exactly the sort that FAQs answer: does the clinic take Kaiser referrals, can the truck cater 80 people, is the patio dog-friendly, how far ahead do custom cakes need ordering. When a page holds that question and a clear answer side by side, an assistant searching for the narrow question finds a passage that matches it in both directions.

Bay Area AEO lists FAQs alongside service pages and structured data in its answer-ready content service, and in its answer to whether a new website is needed: the agency adds what AI needs, meaning clear service pages, FAQs, structured data and accurate business details.

Where the questions come from

The best FAQ questions are ones customers have actually asked. Pull them from four places: the question list collected in chapter 1, the inbox and contact form, the front desk or phone (ask staff to write down questions for two weeks), and reviews, where customers often mention what they were unsure about before booking. Add the follow-up questions assistants raise in the audit (“Do they offer financing?”), since those are questions the assistant itself needed answered.

Avoid inventing questions to fit a sales message (“Why are we the best choice?”). No customer asks it in that form, and no assistant needs the answer.

Writing the answer

The rules are short. Answer in the first sentence. Make that sentence complete on its own, with the subject named, so it still makes sense if quoted without the question. Add one to three sentences of detail: the condition, the exception, the next step. Use the same terms customers use.

The example numbers in that table are illustrative. Each business should use its own real policies. The pattern is what matters: yes or no first, then the specific condition, then the place or the cost.

A model worth copying

Bay Area AEO's own FAQ follows this pattern, and it is a useful template for any business. Its answer to “How long does answer engine optimization take to work?” reads, in full: “Listing and data fixes can start showing up in AI answers within a few weeks, because many assistants pull live information. Content, reviews and third-party mentions build over two to four months. Prompts are re-tested monthly so progress is visible.” Three sentences, each a complete fact, each quotable alone. Its answer to “Do I need a new website for AEO?” starts with “Usually not needed” and then says why. Neither answer hedges, and neither wanders into a sales pitch.

Where FAQs belong

Put most FAQs on the page they relate to: questions about implants on the implants page, questions about catering minimums on the catering page. That keeps each service page complete, and it means an assistant reading the page gets the service description and its common questions together.

A central FAQ page still has a place for questions about the business as a whole: parking, payment methods, cancellation policy, accessibility, languages spoken, how to book. Keep it short and link from each answer to the page with more detail. Avoid repeating the same FAQ word for word on many pages; if a question applies everywhere, it belongs on the central page.

How many questions per page

Enough to cover what customers really ask, which for most service pages is between four and ten. A list of thirty questions on one page is usually a sign that the page is covering several services and should be split, or that the questions were invented to fill space. Order them by how often customers ask, with the most common first.

Marking them up

FAQ sections can carry FAQPage structured data, which states each question and answer in a machine-readable form. Google no longer shows FAQ rich results for most sites, but the markup still gives any crawler a clean statement of the question-and-answer pairs on the page. The markup must match the visible text exactly. Chapter 26 covers how.

Formatting for readers and machines

Write each question as a heading or in bold, followed by the answer in an ordinary paragraph. Accordion-style FAQs that hide answers until clicked are fine for readers, as long as the answer text is in the page's HTML when it loads. Some site builders load the answers only when clicked, using JavaScript, which can leave crawlers with an empty list of questions; chapter 28 explains how to check.

Tone and length

An FAQ answer should sound like the best person at the front desk on a good day: friendly, direct and specific. Avoid legal-sounding hedges unless the profession requires them, and avoid exclamation marks and sales lines, which tend to be skipped when an assistant summarizes. Most answers need between two and five sentences. If an answer needs more than a paragraph, it is probably a topic for a page of its own, with the FAQ giving the short answer and linking to it.

FAQs by trade

Bay Area AEO's niche pages point to the questions that matter most in each trade, and they make good FAQ starting lists. Chiropractors: what happens at the first visit, typical treatment length and cost, accepted plans, cash rates and personal-injury policies. Breweries: whether kids, dogs and outside food are allowed, and whether reservations are taken. Med spas: the consultation process, candidacy, downtime and aftercare. Property managers: management and leasing fees and what they include, and the local rent control rules where they operate. Solar installers: how net billing and batteries affect payback, explained honestly. Each of these is a fan-out search waiting for an answer.

Sensitive trades

Health, legal and financial businesses should write FAQs with their professional rules in mind. Bay Area AEO's pages flag this: law firms working within the State Bar's advertising rules, financial advisors demonstrating expertise without promising returns, acupuncturists writing about focus areas carefully and without overpromising. An FAQ can explain what a treatment involves, how a legal process usually unfolds or how a fee is structured, without promising an outcome. That kind of answer is also what assistants prefer to quote on these subjects.

Writing for the follow-up question

Assistants are conversational, and customers often ask a second question after the first answer: “Which of those is cheapest?”, “Do any of them do Saturdays?”, “Is that one good with kids?” The assistant goes back to its sources to answer, and a business whose FAQ already covers the follow-up stays in the conversation. The audit is a good place to find these: after each discovery question, ask the natural follow-up and note what the assistant had to look up.

Follow-ups tend to be about comparison and logistics, so the FAQs that serve them are the plain ones: prices, availability, parking, how long it takes, what to bring, whether there is a waitlist. They are easy to write and often missing.

Questions people say aloud

Spoken questions are shorter and more direct than typed ones: “Is the bakery on Fourth Street open?”, “Does the clinic take walk-ins?”. FAQs that answer a yes-or-no question with yes or no in the first word suit voice answers well, because the assistant can read the first sentence aloud and stop. Keep at least a few answers that short.

Keeping FAQs current

FAQs go out of date quickly because they hold the details that change: fees, policies, insurance plans, lead times. Review them whenever the master business record changes, and on a fixed schedule at least twice a year. When a new question starts coming up at the front desk, add it. When an answer changes, update the page and the markup together.

Related chapters17. Service pages an assistant can quote · 24. Writing quotable passages · 26. Markup for services, FAQ sections and menus · 16. Pages from real questions