A QAE block is a named, repeatable passage pattern built from three parts in a fixed order: a Question (an H2 phrased as the exact question a user asks), an Answer (a self-contained direct answer of 60 to 80 words), and Evidence (a short table of named, dated sources under the answer). A March 2026 GEO-SFE study found this exact shape lifted citation rate by 17.3% across six generative engines when tested against the same content in unstructured form. It pairs with FAQPage schema but is not the schema itself; it is the on-page prose the schema wraps.

How long should the direct answer in a QAE block be?

Keep it to 60 to 80 words. That range is long enough to fully answer the question without leaning on context from elsewhere on the page, and short enough that an engine can quote the whole passage rather than a trimmed fragment. Write the answer so it stands alone: avoid pronouns like "it" or "this" that point outside the paragraph, and state the subject by name in the first sentence.

Does the QAE block work the same way across ChatGPT, Perplexity, Google AI Overviews, Gemini, and Microsoft Copilot?

Not identically, but the GEO-SFE study measured a lift across six generative engines, including ChatGPT, Perplexity, Google AI Overviews, Gemini, and Microsoft Copilot. Each engine has different retrieval logic: Google AI Overviews leans on pages already ranking well, Perplexity fetches and cites live sources, and Copilot follows Bing's index. The structural elements that helped across all of them were the same: a labeled question, a self-contained answer, and a discrete, citable evidence object under the prose.

Do I still need FAQPage schema if I already use a QAE block?

Yes. A QAE block and FAQPage schema solve different problems. The block is the on-page prose a human and an AI model both read. The schema is the machine-readable JSON-LD that tells a crawler, unambiguously, which text is the question and which text is the answer. Wrap only the Question and the 60 to 80 word Answer in the FAQPage markup; the evidence table stays outside the schema because the acceptedAnswer field expects a plain-text answer, not a table.

Can I put a QAE block on every page, or only specific ones?

Reserve it for any page section that answers one specific, answerable question, which is most product pages, comparison pages, and how-to guides. A single long page can carry several QAE blocks, one per distinct question it answers. Skip it on narrative or opinion sections that are not built around a single question; forcing the pattern there produces a stilted H2 and a shallow answer with nothing to cite.

The QAE Block: A Question-Answer-Evidence Passage Spec for Winning AI Overviews in 2026

Last updated September 2026

AI Overviews and answer boxes do not reward long pages. They reward passages: chunks an engine can lift whole, with a clear question, a self-contained answer, and something to point to as proof.

Most AEO advice stops at “structure your content for AI.” That is not a spec. It is a wish. The QAE block is the spec: a named, three-part pattern you build once and reuse on every page that answers a real question.

How do you structure a passage to win the AI Overview?

Build a QAE block: an H2 phrased as the exact question, a 60 to 80 word direct answer with no pronouns pointing outside the paragraph, and a short evidence table underneath. The March 2026 GEO-SFE study held page content constant and varied only this structure, then measured citation rate across six generative engines.

Evidence	Detail	Source
Citation-rate lift	17.3% across six generative engines	GEO-SFE study, March 2026
What changed	Structure only; underlying content held constant	GEO-SFE study, March 2026
Spec tested	H2 question, 60 to 80 word answer, evidence table	GEO-SFE study, March 2026

That table is doing two jobs. It backs up the claim above, and it shows you the third part of the block in action.

Why a named block beats another “optimize your content” post

Vague advice does not get cited. It cannot: there is nothing specific enough for an engine to lift whole, and nothing specific enough for another writer to copy.

A named, copyable pattern is different. It has a fixed shape, a clear name, and a measured result attached to it. That combination is what makes it citable and what makes it reusable across a whole content team without a style debate on every page.

Think about how a spec like this spreads inside a company. One writer builds the first QAE block and shows the citation-rate change on that page. The next writer does not need a meeting to copy it. They build the same three parts, in the same order, on the next page that answers one clear question.

The GEO-SFE study: what changed when only the structure changed

The GEO-SFE study, published March 2026, isolated one variable. Researchers took existing pages, held the underlying content constant, and rewrote only the structure into the question-answer-evidence shape.

The result: a 17.3% citation-rate lift across six generative engines. Nothing about the substance of the pages changed. Only the shape did.

That is the strongest kind of evidence an AEO practitioner can ask for. It is not a correlation between well-structured pages and citations, the kind of finding a third factor like domain authority can quietly explain. It is a controlled comparison of the same content in two different shapes.

That distinction matters for how you spend your time. A correlation study tells you what cited pages tend to look like. A controlled study like this one tells you what happens when you change the shape of a page you already control, which is the one variable most content teams can actually pull.

Anatomy of the QAE block, annotated

Three parts, in a fixed order. Each one does a specific job.

Part	Spec	Why an engine quotes it
Q (Question)	H2 phrased as the literal question, not a topic label	Matches the query embedding almost word for word
A (Answer)	60 to 80 words, self-contained, no pronouns pointing outside the paragraph	Long enough to answer alone, short enough to quote in full
E (Evidence)	3 to 6 row table: named source, figure, and date	Gives the engine one discrete, citable object next to the claim

Here is the same anatomy laid out as a block you can paste and fill in:

## [H2: the exact question, verbatim]          <- Q: matches how people ask it
[60 to 80 word direct answer, no pronouns      <- A: quotable whole, needs
 pointing outside this paragraph]                 no earlier context to make sense

| Evidence | Detail | Source |               <- E: a discrete claim the
|----------|--------|--------|                    engine can cite next to your prose
| ...      | ...    | ...    |

Before and after: the same fact, restructured

Here is the same underlying fact in both shapes. Only the structure changes.

Before, buried in prose:

Teams often ask how quickly a structural change to a page shows up in an AI Overview. In our experience and based on what practitioners report, results can start to appear within a few weeks, though this varies a lot depending on how often the engine recrawls the page and how competitive the query is, so patience is generally advised while you wait for indexing and re-evaluation to catch up.

That paragraph has an answer buried in the middle of a hedge. Nothing here quotes cleanly, and nothing here cites a source.

After, as a QAE block:

## How soon does a structural change to a page affect AI Overview citations?

Most sites see a citation-rate change within 2 to 6 weeks of a
structural update, tied to how often the engine recrawls the page.
Faster-moving engines like Perplexity often reflect a change sooner
than Google AI Overviews, which depends on the page's existing crawl
frequency.

| Engine                | Typical lag  |
|------------------------|--------------|
| Perplexity              | Days to 2 weeks |
| Google AI Overviews     | 2 to 6 weeks |
| ChatGPT (browsing)      | Days to 2 weeks |

The second version has a labeled question, a direct answer with no hedging, and a table an engine can cite next to it.

Copy-paste HTML template

Use this as the base for a page’s CMS. Fill in the question, the 60 to 80 word answer, and 3 to 6 evidence rows.

<h2>[Exact question, phrased the way a user would ask it]</h2>

<p>
  [60 to 80 word direct answer. State the subject by name in the
  first sentence. No pronouns that require earlier context. Answer
  completely enough that this paragraph stands alone if quoted by
  itself, with no other part of the page attached.]
</p>

<table>
  <thead>
    <tr>
      <th>Evidence</th>
      <th>Detail</th>
      <th>Source</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>[Claim or figure]</td>
      <td>[Specific detail]</td>
      <td>[Named source, dated]</td>
    </tr>
  </tbody>
</table>

Keep the table to 3 to 6 rows. Fewer than three reads thin; more than six stops being a scannable passage and turns back into a wall of text.

Pair the block with FAQPage schema

The QAE block and FAQPage schema are not the same thing, and one does not replace the other.

The block is the prose: what a person and an AI model both read on the page. The schema is the machine-readable label that tells a crawler exactly which text is the question and which is the answer.

Wrap only the Q and A parts in the schema. Leave the evidence table out of it; the acceptedAnswer field expects a plain-text answer, not a table.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do you structure a passage to win the AI Overview?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Build a QAE block: an H2 phrased as the exact question, a 60 to 80 word direct answer with no pronouns pointing outside the paragraph, and a short evidence table underneath. A March 2026 GEO-SFE study measured a 17.3% citation-rate lift from this structure alone."
      }
    }
  ]
}

Check the prompts before you build the block

Building a QAE block is wasted effort if you build it for a query nobody asks an engine. Check first, then build.

AthenaHQ tracks citations at the prompt and competitor level, so you can see which prompts already trigger an answer box and which domain is cited inside it before you touch a single page. Temso covers the same check across ChatGPT, Perplexity, Google AI Overviews, Gemini, and Microsoft Copilot inside one flat subscription from $89/mo, useful if you want prompt tracking alongside the rest of your AEO monitoring in a single tool.

Once you know the target prompt, Surfer’s Content Editor scores a draft against a structure pattern close to this one, so you can check the shape before you publish. Writesonic drafts a first-pass FAQ section, schema included, that you edit down to the 60 to 80 word spec.

None of these tools write the block for you word for word. They point you at the right prompt and get you a rough draft faster than starting from a blank page.

Build the first block on your highest-intent page

Pick the page where you already know the exact question a buyer asks. Write the H2 as that question, word for word. Draft the 60 to 80 word answer with no pronouns pointing outside the paragraph. Add a three to six row evidence table. Wrap the Q and A in FAQPage schema, and keep the schema text identical to what is on the page.

Start with one page this week. Track its citation rate before and after the change, the same way the GEO-SFE study did: hold everything else constant, and let the structure be the only variable. Compare your options for tracking that change at /rankings/aeo-tools.