Writing Definition Blocks That AI Answers Quote

What is a definition block? A definition block is a self-contained answer of 40 to 60 words placed directly under a heading, stating what something is or how it works before any elaboration. It gives search engines and AI systems a passage they can quote whole, without needing surrounding context.

You are reading one right now. Every section of this post opens the same way, and that is not a stylistic tic. It is the single highest-return writing habit for AI-era search, because every major answer system works by extracting passages, and a passage that needs its neighbours to make sense cannot be extracted.

With AI Overview citations from top-10 ranking pages down from 76% to 38% across published studies, the quotable paragraph is often what separates the cited page from the merely ranking one.

The format, precisely

What makes a passage quotable? A quotable passage names its subject explicitly, defines or answers in the first sentence, runs 40 to 60 words, and survives being read with no heading and no surrounding text. Pronouns without antecedents, references to “as mentioned above”, and cliffhanger first sentences all disqualify a passage.

The rules I apply on client content:

Start with the subject, not a pronoun. “A citation audit is…” not “It is…”. The extracted passage travels alone, and a model will not gamble on what “it” means.

Answer in sentence one. Support in sentences two and three. Most writers build up to their point. Extraction rewards collapsing that order.

Keep it 40 to 60 words. Shorter reads thin next to competing passages. Longer gets truncated mid-thought, and truncated passages lose to complete ones.

Bold the opening question. It mirrors how people phrase queries, and it tells skimming humans exactly what the block answers. The machine benefit and the reader benefit are the same benefit, which is how you know the technique is sound.

Before and after

A real example, anonymised, from a page that ranked fourth but never got cited.

Before: “There are many factors to consider when thinking about how often you should send marketing emails, and the honest answer is that it depends on your audience and your goals.”

Forty words spent saying nothing a machine or a human could use. After: “Most small email lists perform best at one to two sends per week. Below that, subscribers forget who you are and spam complaints rise on each send. Above that, unsubscribes climb faster than clicks. Start weekly, watch unsubscribe rate per send, and adjust.”

The rewrite states a position, gives the mechanism, and tells the reader what to do. It was cited in an AI Overview within a month of publishing. One rewrite will not always do that, but across a site the pattern holds: pages with extractable positions get quoted, pages with throat-clearing do not.

Where to place them

Where should definition blocks go on a page? Place one directly under the H1 answering the page’s main query, and one under every H2 that maps to a question people actually search. Skip them for purely narrative sections, since forcing definitions where no question exists produces filler that dilutes the real ones.

Do not convert your whole site into a stack of definitions. The blocks earn their keep because the writing between them has voice, evidence and experience. A page that is nothing but extraction bait reads as thin to humans and increasingly scores as thin to quality systems. The balance is covered in the content marketing guide: definition blocks open sections, real writing carries them.

Common questions

Do definition blocks hurt readability for humans?
Done properly, they help. Skimmers get the answer immediately, and readers who want depth continue. What hurts readability is writing definitions where no genuine question exists.

Should every H2 be phrased as a question?
No. Use question headings where they match real queries, and statement headings elsewhere. A page of ten forced questions reads like an FAQ farm.

Does this replace schema markup?
No, they work together. Schema removes ambiguity about the page’s entities and author, and the definition block provides the passage worth quoting. Do both, starting with the schema guide basics.