# Direct answer

The 40-60 word paragraph at the top of a page that answer engines lift verbatim.

By AgentSite · 3 min read · Updated 2026-05-23

A direct answer is a 40 to 60 word paragraph at the top of a page that answers the implied question of the page in one cohesive block. Answer engines extract this paragraph and quote it verbatim. Pages that bury the answer under introductions, headers, or marketing copy lose the citation to pages that don't.

## The pattern

The agent reading a page is looking for a quotable block — a self-contained paragraph that stands on its own, names the topic in the first sentence, and answers the implied question without requiring the surrounding context. The Princeton GEO paper measured optimization tactics in a controlled experiment against commercial generative engines and reported "up to 40% visibility gains" when content was restructured to favor extractable answers ([Aggarwal et al., KDD 2024](https://arxiv.org/abs/2311.09735); see also the [project page](https://generative-engines.com/GEO/)). The direct-answer paragraph is the substrate those tactics sit on. It is what the engine quotes from.

A workable block has four properties:

1.  **40 to 60 words.** Shorter is too thin to ground a quote; longer fragments the lift.
2.  **Single paragraph.** No bullets, no sub-headings, no inline links inside the block.
3.  **Names the topic in sentence one.** The agent has to know what the paragraph is about before reading its conclusion.
4.  **Self-contained.** Removable from the page without losing meaning.

## Where it sits

Directly after the H1, before any table of contents, before the first H2. Position matters: the agent weights content from the top of the body disproportionately, and the lede is the first cohesive block it encounters.

## Pairing with schema

A direct-answer paragraph pairs cleanly with `FAQPage` structured data when the page is shaped as Q-and-A. [Schema.org](http://Schema.org) defines `FAQPage` as "a WebPage presenting one or more 'Frequently asked questions'" ([schema.org/FAQPage](https://schema.org/FAQPage)). The lede serves as the answer to the implicit question of the page title:

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What is a direct answer in AEO?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "A direct answer is a 40 to 60 word paragraph at the top of a page that answers the implied question of the page in one cohesive block. Answer engines extract this paragraph and quote it verbatim."
    }
  }]
}
```

The schema redundancy is intentional: agents that parse JSON-LD lift the answer text directly from `acceptedAnswer.text`; agents that read the rendered HTML lift the same content from the paragraph. Same answer, two surfaces, no drift between them.

## In the AEO stack

The direct-answer paragraph is the canonical Layer 4 tactic in the [five-layer AEO model](/five-layer-aeo). Layers 1 through 3 govern whether an agent can read the page; Layer 4 governs whether the page is worth quoting. A page that passes every technical layer but leads with marketing copy loses the citation anyway.

The longer treatment lives in the [AEO essay](/aeo); the extraction mechanics — including how the render service emits a per-page TL;DR when the source page does not — live in the [docs](/docs).