Answer Block Shape

Answer Block Shape checks whether your page opens with a direct answer paragraph of 40-60 words placed within the first screen (the first ~200 body words). friendly4AI scores this Content Structure signal on a five-state gradient. A correctly sized, well-placed answer scores 100 (pass). A too_long, too_short, or mis_placed answer lands in partial. No detectable answer block scores 20 (fail).

What does Answer Block Shape measure?

This signal measures one thing: does your page lead with a direct, right-sized answer near the top? friendly4AI strips the nav, header, footer, and aside, then walks the remaining body in document order, hunting for an answer cue:

• a question heading (H2/H3 ending in ?),
• a <dt> / <dfn> definition term, or
• a "{X} is / means / refers to" sentence opener.

Once it finds a cue, the scanner takes the first paragraph that follows and reads two things: its word count and its running-word position. That gives one of five verdicts — present, too_long, too_short, mis_placed, or missing.

Why does the answer block matter for AI-readiness?

AI systems prefer pages that answer the likely user query up front. A tight answer paragraph in the first screen is the chunk a model is most likely to lift into its response. Bury that answer under a long intro, pad it past 60 words, or stub it under 40, and you hand the model a weaker target. A page with no detectable answer block at all rarely earns an answer-block citation. Lead with the answer and your citation rate goes up.

How is Answer Block Shape scored?

The v4.5 methodology scores this Content Structure parameter on a five-state gradient. The scanner checks the answer paragraph's word count against the target range (40-60 words by default) and its position against the first-screen window (the first 200 body words):

| Verdict | Condition | Score | Band | |---|---|---|---| | present | In range and inside the 200-word window | 100 | pass | | too_long | Over 60 words | 60 | partial | | too_short | Under 40 words | 50 | partial | | mis_placed | In range but past the 200-word window | 40 | partial | | missing | No answer block, or a paywall/login signal | 20 | fail |

Note that too_short is penalised harder than too_long: a stub answer helps a model less than a verbose one does. A paywall or login signal in the first 500 body characters also forces missing. One caveat worth flagging — the product's failAction copy quotes a wider 80-200 word guide, but the processor's default target range is 40-60 words. Aim for 40-60 to clear the pass band.

How do I fix Answer Block Shape issues?

• Add a concise 40-60 word answer paragraph near the top of the page that addresses the main user query head-on.
• Keep it within the first ~200 body words, ahead of any long intro or navigation, so it doesn't get flagged mis_placed.
• If the block reads too_long, cut it back to the core answer. If too_short, add a sentence or two of support.
• Put a clear cue in front of the answer — a question heading, a definition term, or an "X is …" opener — so the scanner recognises it.
• Re-scan, then check the answer_block_verdict, answer_block_word_count, and answer_block_position_word evidence fields to confirm the fix held.

Related parameters

• Answer-First Compliance
• Answer Structure
• Paragraph Length Distribution