An AEO FAQ page gets cited when each answer stands on its own. One question, one direct answer, 40 to 80 words, with a real number or a real name in it. That is the format. Everything else on this page is detail.
The reason is mechanical. When ChatGPT or Perplexity or Google's AI Overview answers a customer question, it needs a chunk of text it can lift without inventing anything. A paragraph that says "our pricing varies depending on your needs" cannot be lifted. A paragraph that says "Emergency after-hours calls in Tampa carry a $149 dispatch fee, waived if you book the repair" can be lifted word for word. Guess which one gets quoted.
Most FAQ pages on local service sites were written for a different job. They were written to fill space, or to catch a few long-tail keywords, or because a template had an FAQ section and somebody had to put something in it. Those pages do not get cited. They are not broken, they are just not built for the question they now have to answer.
What makes an AEO FAQ page different from a normal one
A normal FAQ page assumes a reader who is already on your site, scrolling, half-committed. It can afford to be vague because the reader can click around and fill in the gaps.
An AEO FAQ page assumes the opposite. The reader is never on your site. An AI tool read the page, pulled one answer out of it, and showed that answer to somebody who typed a question into a chat box. Your answer is travelling alone, with no homepage around it, no phone number in the header, no context.
So every answer has to carry its own context. That means the city goes in the answer, not just in the page title. The service name goes in the answer. The price range, the timeframe, the license type, the insurance list. If the answer would confuse somebody reading it cold, it will not get cited, because the AI is judging exactly that.
The one-sentence test
Read the first sentence of any answer on your page. If it does not resolve the question by itself, rewrite it.
Weak: "Great question! There are a few factors that go into how long a root canal takes."
Strong: "A standard root canal takes 60 to 90 minutes in one visit. Molars sometimes need a second appointment."
The second one can be quoted. The first one is throat-clearing, and an AI summarizing your page will skip past it to find something usable, or skip your page entirely.
Where the questions come from
Do not invent the questions. You already have them, in four places, and they are more specific than anything you would make up at a desk.
Your phone
The questions people ask before booking are the questions to answer. Ask whoever answers the phone to write down every question they get for two weeks. You will end up with something like: do you charge for the estimate, how fast can you get here, do you work on Trane units, do you take Delta Dental, is there a warranty, do I need to be home.
Those are the real ones. They are boring and specific, which is exactly why they get cited.
Your email and text threads
Search your sent folder for question marks. The follow-up questions customers ask after the first quote are the highest-intent questions you own, and almost nobody puts them on a website.
Your reviews
Reviews that explain something usually contain a question the customer had. "I was worried about the cost but they quoted a flat fee before starting" is a review that tells you to write an FAQ answer about flat-fee quoting.
The AI tools themselves
Ask ChatGPT or Perplexity the questions a customer in your city would ask. Read what it returns. If it names a competitor, open the page it pulled from and look at how that answer is written. This costs nothing and takes twenty minutes. More on this in our guide to how local businesses show up in AI search.
The format that gets cited
Structure each entry the same way, every time.
- The question, phrased the way a customer says it. Not "Service Area Information." Write "Do you service Brandon and Riverview?"
- The answer in the first sentence. Yes or no or the number, immediately.
- Two or three sentences of specifics. The exception, the price, the timeframe, the qualifier.
- Stop. Do not add a sales line. Do not add "contact us today to learn more." It dilutes the chunk.
Keep each answer between 40 and 80 words. Shorter than 40 and there is not enough substance to cite. Longer than 120 and the AI has to summarize it, which means it may summarize it wrong.
A worked example
Here is a weak entry from a med spa page:
How much does treatment cost? Pricing depends on the treatment plan we design for you. Contact us for a complimentary consultation to discuss your goals and we will build a custom package.
Here is the same entry rebuilt:
How much does a Botox appointment cost in Orlando? Botox at our Orlando office is priced per unit, typically $12 to $15 per unit, with most forehead and frown-line treatments running 20 to 40 units. A first appointment usually lands between $240 and $600. Consultations are free and we quote the full amount before anything is injected.
The second version answers the question somebody actually typed. It also answers the follow-up question they were about to type. That is what a cited answer looks like.
What to cut from your existing FAQ page
Questions nobody asks. "Why choose us?" is not a question. It is a headline pretending to be a question. Nobody types it into ChatGPT.
Marketing language inside the answers. "Our team of highly trained professionals is committed to excellence" is uncitable. It contains no fact. Cut the sentence, keep the credential: "Both hygienists are licensed in Florida with over ten years each."
Answers that link out instead of answering. "See our services page for details" gives the AI nothing. Put the detail in the answer.
Accordion sections that hide the text. Most collapsible FAQ widgets are fine, since the text is usually still in the page source. But if your FAQ answers load only after a click, they may not be readable at all. View the page source and search for one of your answers. If it is not there, that is a real problem and worth fixing before anything else on this list.
Schema helps, but it is second
FAQPage schema markup gives search engines a structured version of your questions and answers. It is worth adding. It is not the thing that makes you get cited.
The order matters: write specific, standalone answers first, then mark them up. Schema on a vague page just describes a vague page more precisely. This is the same principle behind making your business easier to understand online, where clarity in the copy does the work and the technical layer follows.
How to check whether it worked
Give it a few weeks after publishing, then ask the AI tools the exact questions you answered. Use the phrasing a customer would use, including the city. If your business comes back, read the sentence it returns and check whether it matches what you wrote.
If a competitor comes back instead, open their page. Usually the difference is that they put a number where you put an adjective.
Also watch your call log. The tell is a customer who arrives already knowing your dispatch fee or your insurance list, and who did not come through a Google search. That is your FAQ page being read out loud somewhere you cannot see. For the wider picture of how these pieces fit together, our overview of what AEO means for local businesses covers the rest of the setup.
Start with ten questions
Ten real questions, answered properly, beat forty questions answered vaguely. Pull the ten most common calls from the last month, write each answer to the format above, and publish. Add more as the phone tells you what is missing.
If you want the questions pulled, written, and marked up for you, see GeoLocally pricing and we will build the page from your own call history.