A list you choose from, an answer you accept
A results page hands over a column of links and delegates the judgement. The reader scans titles, forms an impression of who is credible, opens two or three, and compares them. Position decides who gets scanned, but the reader still does the choosing, and a page further down can still win on the strength of its first paragraph.
An assistant collapses that. It reads the sources, writes one answer, and names a few of them. The reader does not compare; they accept, or they ask a follow-up. There is no second place in that moment, and no impression of your design, your cases or your brand. There is only whether a sentence of yours was usable enough to be carried into the answer.
What the assistant is actually doing with your page
The mechanism is retrieval. A question goes in, the system finds passages that look like they answer it, and a model writes a reply out of those passages. It does not read your site the way a person does, top to bottom, picking up context on the way. It pulls a fragment and uses it alone, with the rest of the page absent.
That single fact produces every writing rule that follows. A paragraph that opens by referring back to something said above is unusable. A benefit that only makes sense after the section heading is unusable. A claim resting on an adjective — leading, robust, world-class — carries nothing a model can load into an answer, and it is identical to the adjective your competitor used.
What travels well is a block that stands on its own: a question phrased the way a buyer would type it, a complete answer in the opening sentences, and a verifiable fact instead of a superlative. It has to survive being quoted with nothing around it, because that is the only way it will ever be quoted.
How a page has to be written to be quotable
Put the answer in the first forty words, before the context, before the story, before the qualification. A page that builds toward its point is written for a reader who has already decided to stay. Retrieval never reads that far. The conclusion goes at the top and the reasoning goes underneath, for the human who wants it.
Say explicitly what you do not do. Most pages describe only the fit, which forces a model to guess at the misfit and makes every provider sound alike. A page that names the case it is wrong for hands over a fact that distinguishes it, and the buyer who reads that exclusion and stays is better qualified than the one who never saw it.
Define your own terms in a form that can be lifted whole, and give the page the structured data that says what it is: an article, a question block, an organization. Headings should be the questions themselves, so that a heading and the paragraph under it form one complete unit. The unit is what gets retrieved; the page is only where it lives.
Does this replace search?
No, and treating it as a replacement is the common error. Assistants retrieve from the open web, and a page no crawler can reach or understand is not a candidate for retrieval either. Ranking work and citation work run over the same pages: the technical structure that makes a page indexable is what makes it retrievable.
The difference is what the page has to do once it is found. Programmatic coverage is about how many real questions have a page of their own — service by service, territory by territory, each one genuinely answering its own question rather than filling a template. Citation work is about whether any one of those pages survives being quoted without the rest of the site.
This site is built on that method: every service page opens with a direct answer, names what the work excludes, and phrases its questions the way a buyer types them. Nobody can guarantee what a model will say, because the models change and nobody controls the output. What can be done is write the page to be quotable and then measure, month by month, which assistants cite you and for what.