You answered that question again. Give it a useful home.

01Start with the moment someone gets stuck

You finish a call, close the inbox, then type the same explanation again. That repetition gives you a useful place to start.

Write down the task behind the question. Is someone trying to choose a service, prepare the right files, understand a bill, or fix a problem? The answer should help them take that next step.

GOV.UK’s research guidance recommends needs based on observed problems and phrased in language a user might use. Apply that principle to your business: keep what was asked separate from your guess about why it was asked. [1]

02Keep a small answer record

Use a sheet or document you already maintain. Record only information you are permitted to use, and keep customer identities and private conversations out of the public draft.

Swipe or scroll to compare

For your first pass, collect five questions and choose one. Five is a suggested working limit for this exercise, rather than a demand threshold or a research result.

03Decide whether the question needs a page

A repeated question can reveal missing content. It can also reveal a confusing offer or a broken step. Fix the part that causes the work.

Swipe or scroll to compare

Google’s people-first guidance asks whether a reader can achieve their goal after reading. It also cautions against producing many pages mainly to attract search traffic. Use reader usefulness as the release test. [2]

04Write the answer in four calm parts

• Give the direct answer in the first short paragraph.
• Explain the conditions that would change it.
• Show one useful example, checklist or comparison.
• Finish with the next action and who to contact if it does not fit.

An illustrative question might be: “What do you need from us before the website project starts?” A useful answer would name the actual brief, assets, permissions and approver required by that business. A paragraph about being passionate about collaboration would leave the task unfinished.

Use a descriptive page title and headings. Keep the important answer in ordinary page text, then link to it from the place a customer would expect to find it. Google recommends using the words people use to look for the content in prominent places and making links crawlable. [3]

05Let AI prepare the draft

Give the model an approved brief rather than an inbox export. A short input can contain the general question, cleared facts, source links, exclusions and the action you want the reader to take.

Draft instruction to adapt: Using only this approved answer record, draft a direct answer, conditions, one example and a next step. Attach the supporting source to every factual claim. List missing information separately. Do not infer a price, policy, result, customer identity or permission. If a suitable page already exists in the supplied index, propose a revision to it.

Read the draft against the sources. Confirm business facts with their owner. Check whether the answer has become longer without becoming more useful.

06Run a small pilot for one week

Publish one approved answer. When the same relevant question arrives, offer that page alongside a short personal reply. Check whether the person still needs clarification.

• Record how often the specific question arrives, including cases where the page did not help.
• Count writing, checking, replying and maintenance time.
• Note which part people misunderstand or cannot find.
• Check any connected visits or enquiries separately from search or AI citation observations.

These are proposed checks. No trial, reader result, time saving or discovery gain is claimed here.

07Keep the answer alive

A service change, new price, revised policy or recurring misunderstanding should trigger a review. Update the original answer when the intent stays the same.

After the pilot, choose one move: keep the page, simplify it, move the answer onto a better page, or fix the underlying process. Expand the library when this small loop proves useful to your readers and maintainable for your team.