Write the answer before the introduction
The most common reason a good page never gets quoted is that its best sentence is in the middle. An assistant assembling an answer takes what is short, complete and unambiguous. A paragraph that begins "In today's fast-moving landscape…" contains nothing to take.
The fix is mechanical: state the answer in the first paragraph, in one or two sentences, so that it stands alone if you cut it out and paste it somewhere else. Then write the rest of the page. The introduction you wanted to write can go after — readers skip it too.
A useful test: take your opening sentence out of the page and read it cold. If it needs the heading to make sense, it is not an answer, it is a lead-in.
Give it something specific to repeat
Vague copy is unquotable copy. "Affordable pricing" cannot be repeated by an assistant without it inventing a number; "from €39 a month" can. The same applies to dates, quantities, model names, materials, delivery times — anything a person would actually want to know.
Note what that finding is not. It is not a licence to sprinkle invented numbers through a page. A statistic with no source is worth nothing to an assistant that is trying to decide whether to trust you, and it is worth less than nothing to a reader who checks. Cite where the figure came from, or leave it out.
Structure it so a machine can find the parts
Headings, lists and tables are not decoration. They mark where one idea ends and the next begins, which is what lets an assistant take the relevant chunk instead of the whole page or nothing.
- One question per heading, phrased the way someone would ask it — headings are the strongest hint about what a section answers.
- A list wherever you find yourself writing "first… then… also…" in prose.
- A comparison as a table, not as three paragraphs the reader has to hold in their head.
- A short FAQ at the end, covering the questions the page raises but does not answer inline. It is also the block that produces valid FAQ markup — see structured data for GEO.
Say who wrote it and when
An author name, a publication date and a visible recent year do not make the writing better, but they change how a page is weighed. Assistants are answering questions where being out of date is a real failure, so a page with no date is a page with unknown risk attached.
If a page is genuinely evergreen, say so rather than back-dating it. If it is not, update it and change the date honestly. A page that claims freshness it does not have is the one that eventually gets you quoted saying something wrong.
What this does not do
Shape gets you quotable. It does not, on its own, get you chosen for a competitive question — for "best X in 2026", the assistant is mostly reading other people's pages about your category, and that is a different lever. Off-site authority covers it.
Write for the reader first and this mostly takes care of itself. Every item above is also what makes a page easier for a person in a hurry: the answer up front, real numbers, clear sections, a name and a date. The overlap is not a coincidence — the models were trained on what people found useful.
Frequently asked questions
Does length matter?
Only through what length usually indicates. A very short page rarely contains enough specific material to quote; a very long one is not penalised, but padding it to hit a word count adds nothing quotable. Write until the question is answered, then stop.
Should I write a separate page for every question?
Not usually. One page that answers a cluster of related questions with clear headings gives an assistant several liftable sections and gives you one page to keep current. Split only when the questions have genuinely different answers or different audiences.
Will an AI-written page get quoted?
Nothing detects and penalises it reliably today, so the honest answer is that the shape matters more than the author. But the failure modes of generated copy are exactly the ones that stop a page being quoted — confident vagueness, invented specifics, no real source — so it usually needs more editing, not less.