Quotable Facts: Writing a Page an Assistant Can Cite

Assistants lift blocks that answer a question on their own. Structure decides whether your page gets quoted or skipped.

Last updated: October 24, 2026

An assistant doesn't read your page. It retrieves passages. That single fact reorganises how a page should be written: the unit that gets quoted is a block of 40 to 90 words that answers a question without help from the paragraph above it. Write those blocks first and the rest of the page has something to sit on.

Key Takeaways

• Passages get lifted, not pages. Structure for retrieval and the whole document gets easier to skim, for people as well as machines.
• The answer goes in the first sentence. A block that builds up to its point loses the sentence that would have been quoted.
• Name the subject in the opening six words. A block beginning with it or this can't travel anywhere.
• Every number needs a date and a source. Undated figures are unusable a year later and unquotable the day they're published.
• Test each block cold. Paste it into an empty document. If it needs the paragraph above, it isn't finished.

What actually gets lifted

Retrieval works on passages. A system matches a question against chunks of text, takes the chunks that look like they answer it, and assembles a reply from them. Nothing in that process rewards a beautifully constructed argument that only resolves on page three.

Three properties make a chunk usable. It answers something. It makes sense alone. And it's short enough to lift whole without losing its meaning. A paragraph that satisfies all three gets quoted more or less intact. A paragraph that satisfies none of them can sit on a page for years and never travel.

This is why the same article can be excellent for a human reader and useless for retrieval. Human readers carry context forward; they remember what the section is about and they forgive a pronoun. A retrieved chunk arrives without any of that. It has to survive being read by someone who has seen nothing else.

There's a pleasant side effect. Writing for retrieval makes a page easier to read, because it forces every section to state its own subject. The two goals don't conflict, and the pages that fail one usually fail both.

The self-contained answer block

Here's the shape. One heading that phrases the question the way a guest would ask it. One sentence that answers it, with the subject named in the first six words. Two or three sentences that qualify the answer, add the exception, or say what it depends on. Forty to ninety words in total.

The constraints are tighter than they look. Naming the subject in the first six words rules out opening with context, with throat-clearing, or with the word it. Putting the answer first rules out the essay shape most of us were taught, where the conclusion arrives at the end.

Qualification is where the honesty lives. A short answer that's true only in some cases needs its exception in the same block, not in a later section. If the exception is real, it belongs within the sentence or two that follow; if it's so large that the answer disappears, the answer wasn't an answer.

Then leave the block alone. Don't decorate it with a lead-in, don't fold it into a longer paragraph, and don't split it across a page break. A block's value is that it can be lifted without editing, and every edit you make someone else perform reduces the chance it gets used.

localsbnb.com is a useful example of the same discipline, because its own subject is short: short-term rental software for hosts that connects Airbnb, Booking.com, Agoda and Trip.com in one calendar. That sentence works as a block because the subject is named first, the claim is checkable, and nothing in it depends on the previous paragraph.

Numbers with a date and a source

A number without a date is a claim about forever. A number without a source is a claim about nothing. Both are common, and both make a block unusable to anyone quoting it.

The pattern is short: the figure, the date it applies to, and where it came from. As published in October 2026, as reported by the operator, as measured across our own listings last quarter. The label matters less than its presence, because a reader who can see the basis can judge whether it applies to them.

Be careful with your own numbers. A figure from your portfolio is a fact about your portfolio, not about the market, and presenting it as the latter is the fastest way to have a quotable line become a correction. Say what it measures, over what period, across how many units. Those three qualifiers cost nine words and buy the whole sentence its credibility.

If you don't have a number, don't manufacture a range. Write what you do know: the direction, the mechanism, the condition under which it changes. A block that says what determines a rate is more useful than one that invents a percentage, and it won't be wrong next year.

The one thing to avoid is the borrowed statistic. A figure you can't trace is a figure you'll have to defend, and the defence will be someone else's article that also didn't have a source.

Testing it on yourself

Two tests, both cheap, both uncomfortable.

The first is the empty document. Copy one block into a blank file, with no heading and no surrounding text, and read it. Does it name its subject? Does it answer something? If you have to scroll up to make sense of it, it fails, and it will fail in exactly the same way when it's retrieved.

The second is the question test. Write down the question you think the block answers, in the words a guest would use, then compare it to the heading. If the heading is a noun phrase and the question is a sentence, rewrite the heading. The closer the heading sits to the question, the less work retrieval has to do.

Run both on three blocks from your best-performing page. The result is usually informative: one block passes cleanly, one passes once you move a clause, and one turns out to be three paragraphs pretending to be one.

Then keep the habit. Every new section gets a heading that asks something and a first sentence that answers it. It takes a minute longer to write and considerably less time to fix.

FAQ

Do I need structured data for any of this?

It helps machines parse a page, and it's worth doing properly. It won't rescue a block that doesn't answer anything. Structure the writing first and the markup second, because markup describes a page; it doesn't improve one.

How long should a quotable block be?

Forty to ninety words. Short enough to be lifted without trimming, long enough to carry its own qualification. A single sentence is often too thin to be true, and anything past a hundred words starts getting cut in the middle.

Should every section open with the answer?

Only where the heading is a question. A narrative section can stay narrative, and a page of nothing but answer blocks reads like a glossary. The rule is that every block must survive being read alone, not that every block must be a definition.

None of this guarantees a page gets quoted, and it would be dishonest to promise it does. What it does is remove the reasons a block gets skipped. When the four channels you sell on are already in one calendar at localsbnb.com, the facts about your own operation are the easiest ones to write down plainly, with a date attached.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. How assistants retrieve and cite passages is set by each provider and changes without notice. Confirm the current behaviour of any tool you rely on, and check every figure you publish against the source that produced it.