Answer engine optimization (AEO): how to write pages that get selected as the answer

What counts as an answer engine

Anything that returns an answer rather than a list: the featured snippet at the top of a Google results page, the AI Overview above it, Google’s AI Mode, a voice assistant reading one result aloud, and the chat engines — ChatGPT, Gemini, Perplexity, Copilot. They differ in how they choose, but they share one behavior: they pull a passage from a page and present it as the answer, with or without the rest of the page.

That is why AEO is about passages. A page can be excellent as a whole and still contribute nothing, because no single stretch of it answers the question on its own.

Answer-first writing, exactly

The pattern is simple and it is the same on every page we build:

1. The heading is the question. Written the way a customer says it, not the way an agency does. “How long does a roof replacement take?” — not “Roof Replacement Timeline Considerations.”
2. The first sentences are the whole answer. Forty to sixty words that would still be correct and complete if they were the only thing shown. “Most residential roof replacements in Middle Tennessee take one to two days. A tear-off and re-deck on a larger or steeper roof can take three. Weather is the usual reason a job runs longer.”
3. Then the specifics. What decides the variation, what the day looks like, what the homeowner needs to do, what it includes. This is what earns the answer and what a generative engine quotes.
4. Then the next question. A page is a sequence of these, each self-contained, ordered the way a customer would ask them.

Two things the pattern rules out: the warm-up paragraph (“In today’s fast-paced world, homeowners have many options…”) and the answer that depends on something above it (“as we mentioned, this varies”). An engine that lifts the passage lifts neither.

Which questions to answer

Not the ones a keyword tool invents. The ones you already answer every week:

• The phone questions. How much, how long, do you do X, do you come to Y, are you licensed and insured, what is the warranty, can you come today.
• The “People also ask” box on a Google search for your trade in your city — those are questions Google has evidence people ask.
• The question a customer asks an assistant. “Best plumber near me for a water heater,” “who replaces roofs in Spring Hill” — ask the engines and look at what they answer and what they cite.
• The objections. Why so expensive, why not the cheaper quote, what if it rains, do I need a permit, what happens with my insurance.

Each belongs on the page where a customer would expect it — the water heater question on the water heater page, the service-area question on the city page — not collected into one FAQ page nobody visits.

FAQ blocks and FAQPage schema

Every page should end with a short FAQ: the three to eight questions about that service or that city, each answered in two to four sentences that stand alone. Two technical rules make it count.

First, the answers must be in the HTML when the page loads. A FAQ that is only rendered after a click — or worse, fetched by a script — is invisible to an engine that does not run the script. A collapsed <details> element is fine; the text is in the document either way.

Second, the same questions and answers go in FAQPage structured data, so a machine reads them as questions and answers rather than as paragraphs. Google has limited the FAQ rich result in its own listings to a narrow set of sites since 2023, so do not expect the dropdowns under your blue link; the markup still tells every engine exactly what was asked and what was answered, which is what AEO is for.

Speakable and voice

A voice assistant reads one answer aloud, so the passage it picks has to make sense with no screen. The answer-first pattern already produces that. The Speakable schema property marks which parts of a page are suitable to be read — the headline and the answer — and every page we build declares it. It is a small signal; the large one is the passage itself.

What AEO is not

It is not a hundred thin pages each titled with a question nobody asked. It is not rewriting every heading as a question until the page reads like an interrogation. It is not a chatbot on the site. It is the discipline of making sure that, for every real question a customer brings, there is one place on your site where the complete answer can be lifted whole — and that the machine can find it.

The AEO checklist

• Every service page and city page opens with a direct answer to the question its heading asks.
• Headings are written as customers speak.
• Each answer would be complete on its own, with no reference to something above it.
• Specifics follow every answer: process, timelines, inclusions, area, credentials.
• A FAQ block of three to eight questions ends the page, answers in the HTML on load, marked up as FAQPage.
• Speakable declared on every page.
• The questions came from the phone, the People-also-ask box, the engines and the objections — not from a tool.

The free scan checks for FAQ markup, speakable and answer-readiness on any page. The AI SEO program is where this gets written.