Direct Answer Block: Write a 40-60 Word Answer
Learn how a 40–60-word direct answer block improves AEO extraction, helps scanning readers, fits each question type, and earns measurable AI citations.
Direct answer
A direct answer block is a 40–60-word passage placed immediately after a page’s main H1 heading. It answers the page’s primary question completely, names its subject and necessary scope, and remains accurate when read alone. Supporting evidence, exceptions, and detail follow below; the block gives readers and retrieval systems the usable conclusion first.
Why this element matters
People scan a title, opening lines, headings, and visible structure before committing to every paragraph. A direct answer rewards that behavior with a usable conclusion, then lets the reader decide whether the supporting depth is relevant. The block and body are not duplicate prose: the block states the conclusion; the body proves it, applies it, documents evidence, and handles exceptions.
It also does not “spoil” the article. An instructional, definitional, or decision page is not a mystery whose value depends on withholding the ending. A scanning reader wanted the answer first. A careful reader still needs the method and proof below it. If revealing the conclusion makes the rest of a page unnecessary, the remaining material was not adding useful depth.
The machine reason is equally important. A retrieval system selects a passage from a larger page for use in an answer. Machine extractability is the degree to which that passage keeps its meaning after the title, preceding paragraph, visual design, and neighboring caveat disappear. A direct answer is written for that separated state: it names the subject, gives the answer, preserves decisive scope, and avoids external references.
This is a core practice in answer engine optimization, or AEO: making useful, supported content easier for answer systems to interpret and cite. It is not a promise that a particular engine will select the passage. It reduces ambiguity at the exact point where ambiguity is most expensive.
When to use it
Use a direct answer when the page has one primary question that can be resolved accurately in 40–60 words. The question may be explicit—“What is customer churn?”—or implied by the page type—“Which option fits this use case?”, “How do I complete this task?”, or “What result did this project produce?” The answer may include a condition, but it must still reach a conclusion.
Use it for definitional, procedural, comparative, and numeric questions. Commercial pages can state what the product, category, or use case does before features; case studies can state the result with its subject, period, and limitation.
Do not use a direct answer when the page has no single dominant question, when the answer would be unsafe without substantial prerequisites, or when evidence is too weak to support a conclusion. A breaking-news live page, a collection with no selection claim, or a narrative essay may need an orientation paragraph rather than a direct answer.
Near misses cause most misuse:
- A two-sentence description of what the article will cover is a preamble, not an answer.
- A list of five lessons is a summary, not a direct answer to one question.
- A safety instruction that requires several conditions belongs before the relevant action, not compressed into an opening claim.
- A slogan such as “The smarter way to win AI search” is brand positioning, not an answer.
- A number without its unit, population, date, or source is incomplete, even when it is technically 40–60 words long.
If safety requires more than 60 words, state the highest useful complete conclusion and put detailed conditions immediately below. Never remove a decisive exception to meet the limit.
Where to place it
Position is part of the element’s meaning. The direct answer appears immediately after the rendered H1, before the table of contents, opening image, author commentary, history, methodology, or first H2. Nothing may force the reader to cross an informational threshold before receiving the page’s answer.
Direct answer position rules
| Location | Allowed? | Why | Required action |
|---|---|---|---|
| Immediately after the H1 | Yes—required | The block can inherit the page question while remaining the first readable conclusion. | Render the complete 40–60-word passage here. |
| After a deck or scene-setting introduction | No | The introduction delays the answer and becomes the passage a scanner or retrieval system encounters first. | Move the answer above the introduction or remove the preamble. |
| Before key takeaways | Yes | The answer resolves one question; takeaways may then summarize several conclusions. | Keep the two elements visually distinct and avoid repeated wording. |
| Beside an advertisement, call to action, or competing callout | No | A competing action or emphasis weakens the answer's boundary and may look promotional. | Place supporting prose, evidence, or takeaways next. |
| Repeated later in the body | No | Two canonical answers create uncertainty about which passage owns the conclusion. | Refer back through normal prose and develop the evidence instead. |
| Next to a source marker | Yes, when needed | A numeric, policy, or research claim needs evidence close enough to survive extraction. | Keep the citation attached without pushing the qualifier outside the block. |
No adjacent opening element may perform the same job. A following scope line cannot repair an incomplete block; the answer must remain accurate alone.
Anatomy
The element has four regions. The question identifies the query and normally comes from the H1 or question attribute. The answer sentence names the subject and conclusion. The qualifier narrows that conclusion by audience, condition, market, date, or evidence boundary. The conditional source marker stays attached to a verifiable claim.
Rendered legend:
- Question association: connects the block to the H1 without repeating a second visible heading unnecessarily.
- Answer sentence: opens with the subject and reaches the conclusion without a preamble.
- Qualifier: preserves the condition that prevents a short answer from becoming falsely universal.
- Source marker: supports a factual claim at the point of use; it is not a badge of authority.
Borders, tints, and labels may aid scanning, but the words must still work in plain text and document order.
Design examples
The gallery covers every approved answer shape with realistic line lengths and the element immediately after the H1. Narrow viewport behavior belongs in the procedural capture, not a separate editorial variant.
Do not create a generic “marketing” variant. Changing color or adding a product slogan does not create a new answer shape; it weakens the element’s stable purpose.
Parameters
Parameters separate the question from the displayed answer and preserve an essential qualifier across platforms.
Direct answer parameters
| Name | Type | Required | Min/max | Default | Source |
|---|---|---|---|---|---|
| question | Plain string | Yes | 3–20 words | None | Attribute; normally matches the H1's primary question |
| answer | Markdown text | Yes | 40–60 words including any qualifier; 1–3 sentences | None | Body after the optional first heading |
| qualifier | Plain string | Conditional | 0–20 words and included in the 40–60-word total | Empty | Attribute when scope changes the answer; rendered after the body |
| label | Plain string | No | 1–3 words; 30 characters maximum | Direct answer | First heading in the body; omitted heading uses the default |
| variant | Enum | No | definitional, procedural, comparative, or numeric | Inferred from the question | Attribute |
| source | URL plus descriptive anchor | Conditional | 0–1 primary source marker | None | Body, attached to the supported sentence |
The qualifier is required when a plan, country, date, audience, or test setup changes the answer; otherwise omit it. Follow the shared element writing rules for attributes, body mapping, and versioning.
Syntax and code examples
The canonical name is direct-answer. The portable directive, Hugo shortcode, and registered WordPress block below carry the same 47-word answer and question.
Portable Markdown directive
:::direct-answer{question="What is a direct answer block?" variant=definitional}
## Direct answer
A direct answer block is a 40–60-word passage immediately after the H1 that resolves the page's main question. It names the subject, conclusion, and necessary scope so the passage remains accurate when extracted alone, while the rest of the page supplies evidence, examples, exceptions, and practical depth.
:::
Hugo shortcode
{{< direct-answer question="What is a direct answer block?" variant="definitional" >}}A direct answer block is a 40–60-word passage immediately after the H1 that resolves the page's main question. It names the subject, conclusion, and necessary scope so the passage remains accurate when extracted alone, while the rest of the page supplies evidence, examples, exceptions, and practical depth.{{< /direct-answer >}}
WordPress block
<!-- wp:amicited/direct-answer {"question":"What is a direct answer block?","variant":"definitional"} -->
<p>A direct answer block is a 40–60-word passage immediately after the H1 that resolves the page's main question. It names the subject, conclusion, and necessary scope so the passage remains accurate when extracted alone, while the rest of the page supplies evidence, examples, exceptions, and practical depth.</p>
<!-- /wp:amicited/direct-answer -->
These notations do not authorize platform-specific copy or fields. Until a renderer supports the type, use an immediately placed plain paragraph, not an unrelated callout.
Examples
Good: the passage survives extraction
For a regulated enterprise, Product A is the better choice when approval records, single sign-on, and 24-month audit history are mandatory. Product B is the better fit for a small team that values faster setup and does not need those controls. Compare the current plans before purchase because packaged features can change.
This names both products, audience, deciding conditions, and change risk. It remains understandable without the H1.
Bad: context disappears with the surrounding page
As mentioned above, it is usually the better option because it includes those features, although that may depend on what you need.
This fails despite its brevity. “As mentioned above” points outside the passage; “it” hides the option; “those features” hides the evidence; and “usually” hides the condition. Extraction would require missing context.
Before and after: remove the dangling pronoun
Before: “It lasts for 30 days, so check it again after that.”
After: “AmICited’s Starter plan retains daily citation-history data for 30 days. Export the required history before the retention window closes, then compare a later 30-day period on the same prompt set.”
The revision carries the subject, plan, metric, duration, action, and comparison boundary. Concision follows completeness.
Correct opening sentence by question type
Answer shape by question type
| Question type | Correct opening shape | Example opening | Common failure |
|---|---|---|---|
| Definitional | [Subject] is [category plus distinguishing function]. | A direct answer block is a self-contained 40–60-word response to a page's main question. | Opening with the history of the term or “In simple terms.” |
| Procedural | To achieve [outcome], complete [ordered actions]. | To validate a content change, record the baseline, publish one controlled revision, and compare the same tracked prompts after the observation window. | Saying “There are several ways” without giving the route. |
| Comparative | Choose [A] when [condition]; choose [B] when [different condition]. | Choose Product A for approval controls; choose Product B for faster setup when those controls are unnecessary. | Calling one option “best” without naming the audience or criterion. |
| Numeric | [Metric] is [value and unit] for [population and period]. | The approved direct answer length is 40–60 words, excluding its optional label and including every necessary qualifier. | Leading with a number that lacks a unit, scope, date, or source. |
For measured results, replace every scope placeholder with verified facts and an attached source.
Schema markup and accessibility
Schema.org is the shared vocabulary used to describe entities and properties in structured data. A direct answer has no dedicated Schema.org type or search feature. It remains visible text within the honest enclosing type and contributes to articleBody. Do not copy it into FAQPage.acceptedAnswer, HowToStep.text, or another JSON-LD property unless the visible page and schema requirements genuinely match.
JSON-LD is machine-readable structured data embedded in a page. It may repeat a visible fact in an appropriate property, but the block and markup must agree.
Accessible Rich Internet Applications (ARIA) attributes communicate interface roles and states to assistive technology. No ARIA landmark or live-region behavior is required here. The block should remain in normal document order immediately after the H1. If the renderer adds a container, use ordinary semantic HTML, associate any visible label with the block, and preserve readable focus order for its source link. Do not use role="alert", because the answer is not a time-sensitive interruption. Do not rely on tint, border, or an icon to identify the block.
Descriptive nouns, explicit units, expanded abbreviations, and meaningful links help both screen-reader users and automated systems by reducing missing context.
Writing rules
Write 40–60 words, excluding the label but including every qualifier. Use one to three sentences and normally one paragraph. Open with the subject and answer. Prefer concrete nouns when a pronoun’s referent would disappear outside the page.
Include the primary subject, a complete conclusion, and every condition that materially changes it. Numeric answers need the metric, value, unit, scope, period, and source. Comparisons name both options and deciding condition; procedures name the outcome and sequence; definitions state the category and distinguishing feature.
Do not put these inside the block:
- Hedging that conceals a missing decision, such as “generally,” “perhaps,” “often,” or “it depends” without stating the actual dependency.
- Brand positioning, slogans, superlatives, or unsupported claims.
- A preamble about what the article will discuss, explore, cover, or reveal.
- Background history, secondary examples, multiple takeaways, or a miniature table of contents.
- A claim the body does not support with reasoning or evidence.
- A call to action, promotional link, navigation link, or request to keep reading.
- A caveat placed outside the block when removing it would make the answer misleading.
Necessary uncertainty is not forbidden. Replace vague hedging with a bounded condition: “The recommendation applies to teams that require audit logs” is accurate; “Product A is probably better for most companies” is evasive. The body may introduce nuance, but it may not reverse the opening answer without correcting the block.
Relationship to key takeaways
The direct answer answers the page’s main question. Key takeaways summarize the most important conclusions developed across the article. Both may appear, in that order, when the page is complex enough to justify them.
If the block works better as several bullets, it may be takeaways. If the bullets reduce to one complete response to the H1, they may be an overbuilt answer. Never repeat sentences across both elements.
Post types that use it
The postTypes frontmatter lists every post type that can carry the element. Position stays fixed; answer shape changes with intent.
Direct answer use by post type
| Post type | Answer shape | What the block resolves |
|---|---|---|
| [Ultimate guides](/seo-playbook/post-types/ultimate-guide/) | Definitional or scoped synthesis | The guide's main conclusion before the complete topic model. |
| [How-to guides](/seo-playbook/post-types/how-to-guide/) | Procedural | The outcome and essential route before prerequisites and detailed steps. |
| [Listicle guides](/seo-playbook/post-types/listicle-guide/) | Comparative shortlist | The selection basis and the few choices that best fit the named audience. |
| [A-versus-B comparisons](/seo-playbook/post-types/comparison-a-vs-b/) | Comparative | Which option fits each decisive condition; no universal winner is required. |
| [Best-X-for-Y pages](/seo-playbook/post-types/best-x-for-y/) | Comparative recommendation | The leading choice for the defined use case and the condition behind it. |
| [Alternatives pages](/seo-playbook/post-types/alternatives-to-x/) | Comparative shortlist | The strongest alternatives by reason for switching, not a generic list. |
| [Glossary terms](/seo-playbook/post-types/glossary-term/) | Definitional | The canonical meaning and distinguishing boundary of the term. |
| [What-is pages](/seo-playbook/post-types/what-is-x/) | Definitional | What the subject is and why it matters before mechanisms and examples. |
| [Product pages](/seo-playbook/post-types/product-page/) | Definitional or outcome-led | What the product does, for whom, and the problem it resolves. |
| [Category pages](/seo-playbook/post-types/category-page/) | Definitional plus selection | What belongs in the category and the primary basis for choosing. |
| [Use-case pages](/seo-playbook/post-types/use-case-page/) | Outcome-led procedural | How the named audience reaches the desired outcome with the solution. |
| [Case studies](/seo-playbook/post-types/case-study/) | Numeric or outcome-led | The measured result, subject, period, and attribution boundary. |
Post-type requirements decide whether it is mandatory. Do not force one answer onto a genuinely exploratory page.
Measurement in AmICited
The edited passage can appear in an answer engine’s cited response, making this element unusually observable. That is not automatic proof of causation: competitors publish, indexes refresh, prompts drift, and engines change.
Use prompt tracking to keep a stable set of questions that express the page’s primary intent. Before editing, record which engines mention the brand, which answer text they produce, and which URLs they cite. Publish the direct answer without bundling unrelated title, schema, link, and page-design changes when a clean comparison matters.
Then use source and citation intelligence to see whether the URL earns citations for the same prompts and whether responses preserve its scope. Compare equivalent windows, retain the baseline, and note publication. A later citation is evidence to investigate, not proof that word count caused it.
Success means the engine cites the intended page and preserves the subject, conclusion, and qualifier. If it repeatedly drops a decisive caveat, revise grammar that lets the caveat separate from the claim.
QA checklist
Final test: paste the 40–60 words into a blank document. Reject the block if the subject, conclusion, or limiting condition becomes unclear.
FAQ
Frequently asked questions
Why must a direct answer block contain 40–60 words?
Does giving the answer first spoil the article?
Can direct answers and key takeaways appear on the same page?
Should a direct answer contain a citation?
Does a direct answer block guarantee an AI citation?
The academy layout supplies the final conversion panel. This page defines the direct answer’s editorial and implementation contract without adding a page-specific layout, shortcode, CSS rule, or nonexistent image reference.
More tutorials in this section
Ready to put it into practice?
Free check · 7-day trial · no credit card