Writing for machines that quote you

Most writing assumes a reader who arrives at the top and moves down: context first, then the point, often with the direct answer a few paragraphs in after some setup. That works for a person reading start to finish. It works badly for an answer engine. The engine is not reading the page. It retrieves the passage that best matches a question and presents that passage, often one or two sentences, with no guarantee the reader ever sees anything else.

If the direct answer is buried under three paragraphs of setup, the passage most likely to be lifted is not the answer. It is whatever sentence scores as the best semantic match to the query. That might be a hedge, a caveat, or a half-formed thought never meant to stand alone. Writing for this pattern means putting the complete, standalone answer first. Not as a summary of what follows, but as the actual answer. If nothing else from the page is read or quoted, that sentence alone is still correct and useful.

Three properties make a passage more likely to be lifted, and lifted correctly. First, it is self-contained. No "as mentioned above", no "this approach", no pronoun that only resolves by reading three sentences earlier. A sentence quoted alone still names what it is about. Second, a table beats the same claim in prose whenever the content is comparative or numeric. A table with headers and units is already machine-readable data, not a paraphrase an engine has to build and might get slightly wrong.

Third, and less obvious, a claim with its source named inside the sentence survives extraction with its credibility intact. "CAN-SPAM requires a working opt-out mechanism, honored within 10 business days" carries its own verification. A bare claim about a law, with the citation two paragraphs away, loses that verification the moment only the claim gets quoted.

This site is built on that structure, and it is checkable. Every answer and blog page here opens with a block of key takeaways: standalone sentences meant to be the whole answer for a reader who stops there, before any supporting argument. That is not a claim about how well it performs with any engine. It is a description of the page structure, which anyone can verify by reading one.

The practical rule is to scope a page to one question and answer it in the first hundred words. Not as a teaser for the rest, but as the complete answer a reader could stop at. If a second, related question needs its own explanation long enough to earn a heading, it usually belongs on a different page. Otherwise it competes for the same passage-extraction slot.

Numbers and comparisons belong in a table with real headers and units, not folded into a sentence where the unit has to be inferred. Any claim about a law, a policy, or a competitor's pricing should name its source and a date in the same sentence. The sentence then stays checkable even when it travels alone, quoted by a person or a machine, with nothing else from the page attached.