Let's clear up a myth first, because a lot of advice still gets it wrong. Adding FAQPage schema will not put a stack of expandable questions under your Google result anymore. In April 2023 Google reduced FAQ rich results, and in August 2023 it restricted them to "well-known, authoritative government and health websites." For a dentist, a plumber, or a law firm, that rich result is gone and isn't coming back.
So why do I still tell every local business to build a real FAQ section? Because the format — not the schema — is one of the most extractable things you can put on a page, and AI answer engines are extraction machines. The Google snippet died. The FAQ got more valuable. Those two facts are both true.
Why the Q&A format wins with answer engines
An AI engine isn't trying to rank your page. It's trying to lift a passage that directly answers the user's question and drop it into its reply. The research on what gets cited keeps pointing at the same shape of content:
- Google's AI Overviews favour self-contained passages — analyses put the sweet spot around 130–170 words that fully answer the query on their own.
- Studies of Perplexity citations find that the large majority of cited sources answer the core question within roughly the first 100 words.
- The Princeton/Georgia Tech GEO study found that adding clear statistics and cited sources to content meaningfully increased how often generative engines surfaced it.
An FAQ block is that shape by construction. A specific question as a heading, a direct 40–90 word answer immediately beneath it. It's pre-chunked into exactly the units an engine wants to quote. You're not tricking anything — you're writing your knowledge in the format the machine reads best, which also happens to be the format a hurried customer reads best.
What FAQPage schema still does (and doesn't)
To be precise about the markup itself: FAQPage is still a valid schema.org type, and Google has said leftover FAQPage structured data "does not cause problems for Search," so there's no need to rip it out. Its remaining value is modest and indirect — it labels your Q&A pairs as questions and answers in a machine-readable way, a small assist to the Recognize layer of the REAL Method.
But be honest about the mechanism: answer engines read your visible, rendered text first. The schema is a label on content that already needs to be on the page in plain sight. One correlational study even found FAQPage markup on a small minority of AI-cited pages — strong evidence that it's the visible Q&A, not the JSON, doing the work. So: add the schema if it's easy (the Schema Generator will produce it), but spend your energy on the questions and answers themselves.
How to build an FAQ that actually gets quoted
Thirty minutes done well beats three hours of generic filler. The pattern:
- Mine real questions, not invented ones. Pull from what customers email and call to ask, your sales conversations, and the "People also ask" box for your service. "How much does a kitchen renovation cost in [city]?" beats "Why choose us?"
- Lead the answer with the answer. First sentence resolves the question; the rest adds context. Don't bury the number under a paragraph of preamble — engines (and customers) quote the top.
- Put one real fact in each answer. A price range, a timeline, a permit detail, a measurement. Specifics are what make an answer worth citing; "we pride ourselves on quality" is not quotable.
- Keep each answer self-contained. Assume it might be read with no surrounding context, because in an AI answer it will be.
- Match the customer's words, not your industry's. People ask "how long does a bathroom reno take," not "what is your project delivery timeline."
Here's the difference in one example. Weak: "Our pricing is competitive and tailored to your needs." Strong: "A mid-size bathroom renovation in Calgary typically runs $18,000–$32,000 and takes three to five weeks, including permit time." The second one can be lifted straight into an answer with your name attached. The first can't be lifted at all.
Where to put it
Two patterns work. A dedicated FAQ section near the bottom of each key service page keeps the questions next to the relevant context — usually the better choice for local service pages. A standalone /faq/ page works when you have a large, cross-cutting set. Either way, the questions should be real headings (<h3>), not hidden inside an accordion that only loads on click — if the answer text isn't in the rendered HTML, a crawler may never see it.
The honest bottom line
Don't add an FAQ for a Google rich result; that ship sailed in 2023. Add one because it's the cleanest way to turn what you already know into passages that ChatGPT, Perplexity, and Google's AI can quote — which is the whole Answer layer of getting recommended. The schema is a nice-to-have on top. The content is the point.
Want to see whether your current pages give engines anything quotable? Run your domain through the AI Visibility check — it flags thin Answer coverage. hello@rankinglocal.ai reaches me directly.