/terms/answer-block · 4 min read · intermediate
Answer block
Citation status
Last checked 2026-06-22
What is an answer block?
The smallest extractable unit of GEO content. Distinct from a passage: a passage might span 300 words and cover two claims; an answer block is one tightly-scoped paragraph or short list answering exactly one question. Featured snippets, AI Overview citations, and voice-assistant replies commonly surface content at roughly the answer-block scale (one paragraph or a short list rather than full pages or single sentences). Observable behavior is consistent with engines preferring self-contained units over partial extracts from longer prose; the underlying selection mechanism (whether engines have a discrete answer-block-level scoring step, or whether this is a byproduct of LLM generation choosing what to quote) varies per engine and is generally not vendor-documented.
Status in 2026
Answer block is a glossary-coined practitioner shorthand, used by AI-search and SEO practitioners but not standardized in any industry vocabulary. Practitioners describe overlapping concepts with phrases such as featured snippet candidate, answer paragraph, snippet-eligible content, and position-zero candidate; none of these are formal terms-of-art and they cover overlapping but not identical scope. (A closely related industry term, "answer box," typically refers to the SERP visual display of a featured snippet rather than the underlying content unit; readers may conflate "answer block" with "answer box.") This entry uses "answer block" to emphasize the GEO-era reframing: from optimizing for one Google-controlled featured snippet slot to designing extractable units that any AI engine might surface. Distinct emphasis: the same content can serve as both a passage in a long-form article and as an answer block surfaced by an AI engine, if structured carefully (question-form heading, direct answer in the first sentence, supporting detail in 1-3 follow-up sentences).
Note on this entry's territory (paired with the passage-level optimization and sub-passage extraction entries' mirror observations): answer block is a writing discipline derived from observable AI-engine citation behavior, not a description of engine internals. The underlying selection behavior (featured snippet extraction, AI Overview quoting, voice-assistant reply synthesis) is non-vendor-canonical because none of the major engines publish their selection algorithms; the term "answer block" itself is glossary-coined. This entry's own content sits in practitioner-discipline territory, because writing methodology is something publishers can directly measure (the isolation test below) without needing vendor-confirmed citation mechanisms. Together with the passage-level optimization entry, this page forms the smallest-citable-unit layer (this entry) to its paragraph-structure layer (passage-level optimization).
How to apply
The answer block is the smallest extractable unit of GEO content, a practical building block for content that may be quoted, summarized, or cited. The writing discipline:
- One claim per answer block, front-loaded: the first sentence should state the answer in full. Subsequent sentences elaborate, qualify, or provide examples. If your first sentence requires context to make sense, restructure.
- Roughly 40-60 words per block (practitioner consensus from observation of typical featured snippets1; not a Google-published standard): short enough to extract cleanly, long enough to carry nuance. Under ~30 words tends to lose substance; over ~80 risks getting truncated mid-thought.
- Test in isolation with a locked prompt template: copy each answer block into a fresh ChatGPT or Claude conversation and ask "Read this paragraph as if you have never seen the page it came from. Summarize it in one sentence and flag any references to context outside the paragraph that prevent the summary from being self-contained." The flags are the rewrite candidates; restore self-contained meaning by inlining the needed context or by tightening the block's scope.
What to skip: turning every paragraph into an answer block. Use them where there is a real user question worth answering directly. Body prose between answer blocks is where you build narrative and authority. It is not all extractable, and that is fine.
How it relates to other concepts
- Sub-unit of a passage. Passage-level optimization covers paragraph-level structure; this entry covers the smallest "integrally-citable" unit.
- Distinct from sub-passage extraction, which is engine behavior (selecting a sentence-level fragment from a retrieved passage). Answer block is writing discipline (designing a paragraph that holds together as a quotable unit). The two work in opposite directions: sub-passage extraction narrows the engines' citation choice toward a sentence; answer block design resists that narrowing by ensuring the paragraph reads as one cohesive citable unit.
- Direct targeting unit for both AEO and Google featured-snippet optimization1.
- Pairs naturally with visible Q&A content; FAQPage schema can describe that structure where appropriate, but it is a machine-readability aid, not a confirmed AI citation factor2. Note: Google fully deprecated FAQ rich results on May 7, 2026; FAQPage schema is still valid markup and may still be parsed by AI engines for question-answer extraction, but no longer triggers in-SERP visual treatment. See the FAQ schema entry for the full deprecation context.
- Implementation pattern of cite-ability. Well-written answer blocks can improve cite-ability, but citation still depends on retrieval, authority, source fit, and engine behavior.
Footnotes
-
Google Search Central documentation on featured snippets. Describes featured snippet types, markup optimization, and exclusion controls; does not publish specific length conventions for snippet eligibility. The "40-60 word" length norm cited in this entry is practitioner consensus derived from observation of typical featured snippets, not from official Google guidance. developers.google.com/search/docs/appearance/featured-snippets. ↩ ↩2
-
Schema.org FAQPage type specification: canonical schema for question-and-answer markup. Note: Google fully deprecated FAQ rich results on May 7, 2026 (see the FAQ schema entry for full context); the schema vocabulary remains valid for machine-readability purposes. schema.org/FAQPage. ↩
Part of Search foundations· editorial cluster, not a semantic link
Also in this cluster: AI Overview · Authority signals · E-E-A-T (AI search context) · Entity-based SEO · Featured snippets · +5 more
Related terms
Mentioned in· auto-generated from other terms' related lists
FAQ
- How long should an answer block be?
- Roughly 40-60 words for a direct one-sentence answer, echoing classic featured-snippet length norms. Longer blocks may be partially extracted by AI engines, reducing the value of carefully-curated framing. Optimal length varies by surface and is not formally disclosed.
- Should every paragraph be an answer block?
- No. Only paragraphs that align with an explicit user query should be structured as answer blocks. Use them at the start of each section under question-form headings, and inside FAQ blocks. Body prose should flow as normal between answer blocks.
- How do answer blocks differ from definitions?
- A definition is one type of answer block. Answer blocks broadly cover any direct response to a specific user question, including 'how do I X' and 'why does Y' patterns. Definitions answer 'what is X' specifically.
Sources & further reading
Get the monthly digest
New terms shipped that week, plus one observation from the AI-citation tracker.