Writing for answer engines: the structure that gets quoted

A language model does not quote pages; it quotes paragraphs. So what decides whether you get named is not the quality of the piece but whether individual sections can stand alone. That is a question of structure, not of content.

A small sharply defined shard has been lifted out of a soft glowing mass and floats freely

In short

  • Paragraphs get quoted, not pages — so the arrangement decides more than the overall quality.
  • The answer sits in the first two sentences under the heading; the reasoning comes after.
  • Six phrases make a paragraph unquotable — back-references like "as described above" above all.
  • Figures, timeframes and conditions belong in the same paragraph as the statement, not the next one.

The usual advice is to write "good content". That is true and does not help, because many good pieces still never get quoted — and the reason is nearly always the same.

A model building an answer looks for the shortest passage that fully answers the question. If it finds none, it takes another source. The best piece in the world delivers nothing if its statements are spread across seven paragraphs.

The basic rule: answer first

Not quotable

"The question of what marketing automation costs occupies many companies. Before we get into it, it is worth looking at the different kinds of cost. Because as so often: it depends. Broadly, four layers can be distinguished …"

Why: after four sentences there is still no answer. Extracted, the paragraph is worthless.

Quotable

"For a one-person business with around 500 contacts, the licence runs at roughly 300 to 900 a year. On top come setup and ongoing upkeep, which over three years usually add up to more than the licence itself."

Why: a complete answer in two sentences, with a figure, a reference size and context — understandable without any surroundings.

The reasoning, the derivation and the caveats come afterwards. They are not lost — they are simply no longer in front.

Six phrases that make a paragraph unquotable

PhraseWhy it hurtsBetter
"As described above …"points at missing contextrestate the point, briefly
"That depends."does not answer"With X it is A, with Y it is B."
"In this case …"which case?name the case
"We have seen that …"presupposes earlier paragraphsthe statement directly
"More on that later."defers the answershort answer now, detail later
"There are various options."empty formulaname the options

Worth knowing

Three elements make a paragraph citable as evidence: a figure, a timeframe and a condition — and all three have to sit in the same paragraph as the statement.

"Introduction takes two to five days" is weaker than "With two to three people in sales, introduction takes two to five working days, most of which goes on cleaning up the existing data." The second version is quotable because it carries its own scope — and is therefore usable without a follow-up question.

The structure of a quotable piece

  1. A short summary at the very top. Three to five points, each a complete statement. The most quoted part of any piece — and the cheapest measure there is.
  2. Headings as a question or a clear statement. Not "Costs", but "What marketing automation costs per year". The heading is the anchor the search happens under.
  3. The answer in the first two sentences of every section. Without exception.
  4. Tables for comparisons. A table is already structured and often gets taken over whole. It needs a header row and has to make sense without the surrounding prose.
  5. A questions section at the end. Each answer understandable on its own, three to five sentences, no back-references. Marked up as FAQPage.
  6. Author with role, date of last review. Visible and in the structured data — with the same value in both.
From practice

The most effective test takes two minutes: copy any paragraph from your piece into an empty document and read it. Is it understandable without anything else? Does it fully answer a recognisable question?

On most pieces, two out of ten paragraphs pass that test. That is the real metric — not the word count, not the reading time. Take it from two to six and you triple the number of places where a system finds something usable.

The conflict with good writing

These rules contradict what you learn about structuring text: lead in, build tension, put the insight at the end. That is not a misunderstanding but a genuine conflict of goals.

It can be resolved, but not argued away:

  • For technical writing, quotability wins. Someone looking for a guide wants the answer, not the dramatic shape.
  • For narrative formats, the arc wins. A case story, a founding account, a position piece — putting the answer up front would destroy the text.
  • The summary is the compromise. It supplies the quotable version at the top and leaves the text below it unchanged.
Tip If you would rather not choose: write the piece the way you think it should be written, then put a summary of four complete statements above it. That takes fifteen minutes and is the only measure on this list that demands no compromise in the writing.
Prompt
Check this piece for whether individual paragraphs are quotable.
Be strict; praise nothing; do not rewrite the text.

Piece:
[paste text]

Tasks:
1. Run the extraction test on each paragraph: would it be
   understandable standing alone, and does it fully answer a
   recognisable question? Output the result as a list:
   paragraph number | passed yes/no | what is missing.
2. State the share of passing paragraphs as a percentage.
3. Mark each of the following phrases with its location:
   "as above", "that depends", "in this case", "we have seen",
   "more on that later", "there are various options".
4. Name the paragraphs where a statement appears whose figure,
   timeframe or scope only follows in the next paragraph.
5. For the three weakest paragraphs, write a better version –
   answer in the first two sentences, no back-reference.

Use no detail that is not in the text.

In closing

Quotability is a property of paragraphs, not of pieces. Know the extraction test and write towards it, and you change not the content but only its arrangement — and that is exactly what decides.

The cheapest measure remains the summary at the very top: fifteen minutes per piece, no compromise in the writing, and the part that gets taken over most often.

Common questions

How do you write content that AI answers will quote?

By having every section fully answer its question in the first two sentences and remain understandable without the surrounding text. Figure, timeframe and scope belong in the same paragraph as the statement. Add a summary at the very top, headings phrased as a question or clear statement, and a questions section at the end.

Which phrases should you avoid?

Back-references above all — "as described above" and "we have seen that" — plus "that depends", "in this case", "more on that later" and "there are various options". All six make a paragraph either incomprehensible or empty once extracted.

How do you test whether a paragraph is quotable?

With the extraction test: copy the paragraph into an empty document and read it. Is it understandable without anything else, and does it fully answer a recognisable question? On most pieces two out of ten paragraphs pass — that share is the real metric, not word count or reading time.

Does this not contradict good writing?

For technical writing it is a genuine conflict of goals, and it resolves in favour of quotability — someone looking for a guide wants the answer, not the dramatic shape. For narrative formats such as case stories or position pieces, the arc wins. The compromise is a summary at the top that leaves the text below unchanged.

What makes a paragraph citable as evidence?

Three elements in the same paragraph as the statement: a figure, a timeframe and a condition. "Introduction takes two to five days" is weaker than the same figure with team size and an explanation of where the time goes — the second version carries its own scope and can be used without a follow-up question.

Marketing that sets itself up

The Studio Engine beta is live. Claim your spot and help shape it from the start.

Join the beta →
← Back to overview