An FAQ page earns AI citations when it answers questions real customers ask, phrased the way they ask them, with direct answers that live on the page about that topic. Most FAQ pages fail all three, with invented questions and marketing phrasing on one orphaned page nobody links to.
Why doesn't your current FAQ page get cited?
Usually it was written from the business's side, not the customer's. The typical FAQ is a list of questions the business wishes people asked: "What makes your team different?" "Do you offer free estimates?" "Are you licensed and insured?" Some of those have a place, but they are not what people type into Google or ask ChatGPT. Assistants field questions like "how long does a bathroom remodel take," "can you patch part of a roof or does the whole thing need replacing," and "is a crack in the foundation always serious." When an engine goes looking for material to answer those, a page of self-congratulatory filler offers nothing to cite.
The other common problem is real questions with evasive answers. "It depends. Call us!" is not an answer, and machines cannot quote a phone-number prompt. Customers can't do much with it either.
Where do real questions come from?
You already have them, though they probably aren't written down in one place:
- Phone calls and the front desk. Whoever answers your phone hears the same questions every week. Ask them for the list.
- Sales conversations and email threads. The questions people ask right before saying yes are the highest-value FAQs you can publish.
- Reviews (yours and your competitors'). Reviewers explain to each other what they wish they had known going in.
- People Also Ask boxes and autocomplete. Free data on how people actually phrase their searches.
- Your site search logs, if your site has search.
For each candidate, ask whether a stranger who has never heard of your business would put this question to an assistant. If the question only makes sense with your brand name in it, it belongs on a sales page, not in the FAQ.
How should you phrase and answer them?
Phrase questions the way people ask assistants, in the first person and in everyday words: "Do I need a permit," "how long will it take," "is it worth repairing." Then answer so that the first sentence resolves the question and the following sentences add the nuance. A couple of sentences to a short paragraph is usually right. If an answer needs to run much longer, it probably deserves its own page.
Do not dodge the awkward ones. Price and timeline questions are the ones customers most want answered and businesses most want to avoid. You can give a straight answer without committing to a number: explain what drives cost, what the typical process looks like, and when an estimate is the right next step. A partial answer earns more citations and more trust than an evasion. In practice, much of answer engine optimization is being willing to answer questions like these.
Do you still need FAQPage schema?
Yes, as long as you know what it will and won't do. Google has become far more selective about showing FAQ rich results, so do not add the markup expecting dropdown listings in search. Add it because it hands answer engines your questions and answers as cleanly labeled pairs instead of prose to be guessed at.
The main rule is that the visible HTML and the schema must always say the same thing, so when you edit an answer on the page, change the JSON-LD in the same edit. Drifted schema (where the page says one thing and the markup another) is worse than no schema, because it hands machines two conflicting versions of your own answer and invites them to trust neither.
Where should FAQs live?
Put them on the pages about their topics. A roof-repair question belongs on your roof-repair service page, where it inherits that page's relevance, internal links, and context. Those are what a retrieval system uses to decide whether a page is worth pulling. A handful of real customer questions per service page is a healthy pattern. A general FAQ page is still useful for business-wide logistics like hours, parking, payment methods, and scheduling.
What doesn't work is one enormous FAQ page holding every question about every service. It competes with your own service pages, ranks for nothing in particular, and buries strong answers next to weak ones. For agencies managing many local clients, this is the template change that pays off most. Collecting real questions for each client and putting the answers on topic pages works across every account.
Then check whether assistants are citing your answers. A visibility platform like Speak Local can show which questions you are being cited for and which ones a competitor still owns. Base next quarter's FAQ additions on that list rather than on another brainstorm.
