How to write answers people (and search) can quote.

What “quotable” actually means

A quote is a passage taken out of its page. Whoever takes it, a reader pasting a line into a message, a search feature building a summary, a colleague copying into a report, loses everything around it: the heading, the earlier paragraphs, the tone. What survives is the sentence or two itself.

So the test for any answer is simple. Cover the rest of the page and read the answer alone. Does it name what it is about? Does it give the fact? Could a stranger act on it correctly?

Everything below is a way of passing that test. None of it is a trick; it is the same advice a good editor would give for any short piece of writing.

Start from the question as it is asked

Collect questions where customers use their own words: support emails, chat transcripts, the questions staff answer at the counter, the phrases typed into your own site search. Keep the wording. “Do you deliver to Wales?” beats “Delivery information” every time.

Write one question per entry and end it with a question mark. If a question contains “and”, it is usually two questions. Split it, and each half gets a clean answer.

Leave out questions nobody asks. “Why choose us?” exists to carry a sales line, and it reads like one. A reader who wants to compare you will ask something more specific, so answer that.

Make the first sentence the answer

Lead with the answer, then give the reason. “Yes, we deliver to Wales, usually within three working days” is complete. “Thanks for asking, delivery is something we take seriously” is not an answer at all.

For a yes or no question, begin with Yes or No, then the fact that makes it true or the condition that limits it. For how long, how much and where, begin with the number or the place.

Before. “It depends on a range of factors, but we try to be as quick as we can.”

After. “Delivery takes two to three working days within the country and five to ten abroad. Orders placed before 2 pm ship the same day.”

The second version carries the same business, with the facts moved to the front.

Let the sentence stand alone

Name the subject again instead of pointing back at the question. “It takes three days” only works under the right heading. “Delivery takes three working days” works anywhere. Replace an opening “this”, “they” or “it” with the noun, and cut “as above” and “see below”.

Add the unit and the scope. 30 days, not “about a month”. “Within the country”, not “locally”. $20, not “a small fee”. A number that is quoted without its unit or its limit gets repeated wrongly, and then it is your name on the mistake.

Keep the length in range

Very short answers say too little: “Yes.” is not a quote, it is a nod. Very long ones bury the fact. A workable range is from eight words to about a hundred and twenty: one to three sentences that answer the question, plus the single condition or next step the reader needs.

Treat those numbers as a prompt to look again, not a verdict. A return policy with three real conditions may need the words. But if you are past a hundred and twenty, ask whether the answer is really a page.

When the full answer is longer, put the short version in the FAQ and link to the page with the detail. The short version is what gets quoted; the link is for the reader who wants the rest.

Specifics beat adjectives

“Fast”, “affordable” and “high quality” cannot be checked, so they cannot be quoted usefully. Replace each with the number, the name, the date or the condition behind it. If there is nothing behind it, the claim probably does not belong in the answer.

Before. “Our repairs are quick and affordable.”

After. “Most screen repairs take under an hour and cost from $60, quoted before we start.”

Use your real figures when you rewrite. An invented number is worse than a vague sentence.

Say what it depends on

Some answers really do depend. Then say on what. “The price depends on the size of the room: up to 15 square metres is $90, and larger rooms add $6 per extra square metre” hands the reader the rule instead of a shrug.

Date anything that changes: prices, opening hours, rules. A quoted answer lives on after the page changes, and a date tells the reader how old it is. Update the answer when the fact changes, and the date only then.

Mark it up so the page and the markup agree

Once the words are right, present them plainly: a heading, then one expandable item per question. Each question stays visible, and each answer is real text in the page, not an image and not something loaded after a click. The browser’s own details and summary elements do this, work with a keyboard and need no script.

Then add FAQPage markup that repeats exactly the questions and answers a visitor can see. Markup that describes something the page does not show breaks the rules for structured data, and a mismatched pair is the usual cause. Generating the block and the markup from the same list removes that risk.

Expandable FAQ boxes no longer appear in search results for most sites, so add the markup because it states the structure of the page accurately, not for a visual reward.

Where to put it, and how many

Put each block on the page where its questions are relevant: delivery questions on the delivery page, not copied onto every page. One identical block repeated across a site dilutes all of them. Three to ten questions on a page is plenty; if you have fifty, you have several pages.

Keep the answers in the page’s HTML when it loads. Content behind a login, or in a tab that needs a script to fetch it, is content that readers and crawlers may never see.

One question, start to finish

Take a question as it arrives, in a customer’s email: “hi, just wondering if you do evenings, my work finishes at 6 and i cant get there before then??”

Step 1, the question. Strip the greeting and the backstory and keep the need: “Are you open in the evening?” One question, one mark, the words a stranger would type.

Step 2, the draft answer. “We do our best to be flexible for our customers, so please get in touch and we will see what we can do.” It is polite, and it answers nothing.

Step 3, the fix. Find the fact and put it first: “Yes, we are open until 8 pm on Tuesdays and Thursdays. On other days the last appointment is at 5 pm.” The days, the hour and the exception are all in the sentence.

Step 4, the check. Cover the page. Is it clear that this is about opening hours? Name the subject if not: “Yes, the shop is open until 8 pm on Tuesdays and Thursdays. On other days the last appointment is at 5 pm.” That is twenty-two words, well inside the range, so move on to the next question.

Keep it current

Review a block whenever the fact it states changes, and at least twice a year. Add questions from the messages you receive, and retire the ones nobody asks. A short, accurate block beats a long, stale one.

A last pass before you publish

Read each answer once more with these five questions.

1. Cover everything but the answer. Does it still make sense?
2. Does the first sentence give the answer?
3. Are the numbers, units, places and dates in the sentence?
4. Is it between about eight and a hundred and twenty words?
5. Does the markup contain exactly what a visitor can see?

To apply these checks as you type, paste your questions into the FAQ block builder. It flags the short, long, repeated and hedged answers, then gives you the block and the markup to copy.