An FAQ page earns AI citations when it answers questions real customers actually ask, phrased the way they ask them, with direct answers that live on the page about that topic. Most FAQ pages fail all three tests: invented questions, marketing phrasing, all dumped on one orphaned page nobody links to.
Why doesn't your current FAQ page get cited?
Because it was written from inside the building. 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.
There is a second failure mode: real questions, evasive answers. "It depends — call us!" is not an answer, and machines cannot quote a phone-number prompt. Which is fitting, because neither can customers.
Where do real questions come from?
You already have them. They are just not 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 phrasing research, drawn from real search behavior.
- Your site search logs, if your site has search.
The litmus test for every candidate: would a stranger who has never heard of your business ask this of 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: first person, plain words. "Do I need a permit," "how long will it take," "is it worth repairing." Then answer in the answer-shaped pattern — the first sentence resolves the question, the following sentences add the honest nuance. A couple of sentences to a short paragraph is usually right; if an answer wants to grow much longer, it is probably telling you it 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 answer honestly without committing to a number: explain what drives cost, what the typical process looks like, and when an estimate is the right next step. An honest partial answer beats an evasion for citations and for trust alike — that willingness to answer is much of what answer engine optimization comes down to in practice.
Do you still need FAQPage schema?
Yes, with expectations set correctly. 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 cardinal rule is synchronization: the visible HTML and the schema must say the same thing, always. When you edit an answer on the page, the JSON-LD changes 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?
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 — everything a retrieval system uses to decide a page is worth pulling. A handful of genuinely asked questions per service page is a healthy pattern. A general FAQ page still has a job: business-wide logistics like hours, parking, payment methods, and scheduling.
What does not work is the dumping ground — 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 highest-leverage template change available: harvesting real questions per client and placing the answers on topic pages scales; dumping grounds do not.
Then verify the loop is closing. Whether assistants actually cite your answers is observable — a visibility platform like Speak Local can show which questions you are being cited for and which ones a competitor still owns. That list, not another brainstorm, is where next quarter's FAQ additions should come from.
