Field notesContent readinessWriting
Writing passages an answer engine can actually lift
Extractable content is not dumbed-down content. It is writing where a specific claim survives being removed from its surroundings — and most business writing does not.
AI Detective7 min read
A system assembling an answer does not read your page the way a person does. It looks for passages that state something specific and survive being lifted out of context. Most business writing fails that test, not because it is bad, but because it was written to be read in order.
The portability test
Take any sentence from your page, remove everything around it, and ask whether it still means something. Consider:
This makes it significantly easier for teams to manage the process at scale.
Lifted out, it conveys nothing. What is it? Easier than what? Which teams, which process, what scale? Every referent lives in a previous paragraph. Compare:
Batch approval lets one reviewer clear up to 200 asset requests in a single pass, replacing individual sign-off on each.
Same claim, portable. It names the feature, quantifies the effect, and states what it replaces. It can be quoted without its neighbours, which is precisely what makes it usable.
Specificity is the mechanism
The single highest-leverage habit is replacing vague intensifiers with facts. Numbers, dates, named things, stated limits. Not because precision is inherently virtuous, but because a specific claim is checkable and a vague one is not.
| Vague | Portable |
|---|---|
| Our platform is highly scalable | The service handles 50,000 concurrent connections per node |
| Setup is quick and easy | Setup requires a DNS record and takes about 15 minutes |
| We work with leading brands | We work with 40 retailers, including three of the UK's ten largest grocers |
| Pricing is flexible | Plans start at £29 per month; annual billing saves 20% |
The right-hand column is harder to write. It requires knowing the answer and committing to it in public, which is why the left-hand column is so common.
Structure that helps extraction
- Headings that state the question or claim, not just a topic. 'How long does setup take?' beats 'Setup'.
- The answer immediately after the heading, before the elaboration. Do not build to it.
- One idea per paragraph, so a paragraph can be lifted whole.
- Real lists and tables for comparisons and steps, rather than prose describing them.
- Definitions stated plainly and early on pages introducing a concept.
On FAQ sections
Question-and-answer formatting genuinely suits extraction, which has made FAQ blocks a reflexive addition to every page. Two cautions.
First, invented questions nobody asks produce filler with a question mark on top. Use questions your customers actually ask — support tickets and sales calls are the source. Second, an FAQ is not a substitute for the page answering its own subject clearly; if the real information only appears in an appended accordion, the page structure is the problem.
This is not dumbing down
None of this argues for shorter or simpler content. Long, technical, demanding writing extracts perfectly well when it makes specific claims in clear structures. What extracts badly is writing that is vague, that defers its point, or that depends heavily on what came before.
The useful reframing: write so that any single paragraph could be quoted by someone who has not read the rest. That constraint improves the page for human readers too, most of whom did not read the rest either.