Write a useful page-content brief
Give a writer the reader task, source facts, limits and approval criteria for one page. Includes a completed fictional service-page brief.
A content brief is an assignment for one page. It tells the writer who the page serves, what decision it should support and which facts they may use. A website project brief covers the wider build; this document covers the words and information needed for a particular destination.
The most useful brief makes unsupported claims and unanswered questions visible before drafting begins.
State the page's job in one sentence
Try this structure: “Help this reader make this decision using this information.” For a service page, that might be: “Help a householder decide whether a wooden dining chair is suitable for workshop assessment, using the accepted scope, exclusions and preparation steps.”
That is more actionable than “write an engaging page about quality furniture repair”. It also gives the reviewer a way to judge the draft without relying entirely on taste.
Build a small evidence pack
Keep facts separate from instructions about tone. Give each fact an identifiable source, such as a current specification sheet, an approved service list or an interview note confirmed by the person responsible for delivery.
| Brief material | What to include | What to avoid |
|---|---|---|
| Offer facts | Current scope, process, limits and practical arrangements | An old page treated as automatically accurate |
| Audience questions | Questions from actual enquiries, with assumptions labelled | A fictional customer quotation presented as research |
| Proof | Owned examples, relevant records or claims someone can substantiate | Awards, reviews or results without evidence |
| Images | Available files, purpose and permission status | A request to “find something online” with no rights check |
| Unknown details | A question, decision owner and effect on the page | Filling a gap with a plausible-sounding promise |
You can prepare a good first draft with unresolved details, but do not publish a factual claim until its basis is clear.
A completed fictional service-page brief
Teaching scenario: Alder & Grain is an invented workshop. Every business fact below is supplied for this example, not verified information about a real provider.
| Field | Completed brief |
|---|---|
| Page | Furniture repairs |
| Purpose | Help a householder judge whether an item fits the workshop's scope and prepare for assessment |
| Reader | Someone with a wooden dining chair or small wooden table who can bring it to the workshop by arrangement |
| Primary task | Decide whether to enquire about assessment |
| Questions to answer | What repairs are considered? What is excluded? Can photographs establish the final price? What happens before work starts? What should I send? |
| Approved scope | Wooden dining-chair joint repairs and minor wooden-table repairs |
| Exclusions | Upholstery, home visits and national collection |
| Process | Initial photo review; booked inspection where appropriate; written scope and quote; customer approval; repair; arranged collection |
| Important limit | Photographs help with initial review but do not establish a final repair scope or guaranteed price |
| Evidence pack | Fictional owner-approved service list F1 and process note F2; no testimonials, awards or outcome statistics supplied |
| Tone | Calm, direct and practical; explain workshop terms when they are necessary |
| Next action | Prepare an overall photograph, a close-up of the problem and a short description, then use the business's confirmed contact route |
| Constraints | No fixed turnaround, price, sustainability claim, safety promise or guarantee without separate evidence |
| Reviewer | The workshop owner checks scope and operational facts; the editor checks structure and wording |
| Acceptance | The draft states scope and exclusions, explains approval before work, identifies preparation information and contains no unsupported claims |
For a real commission, replace the fictional evidence references with actual source material. Include the confirmed contact route and operating arrangements before the page goes live.
Give useful tone instructions
| Weak instruction | More useful direction |
|---|---|
| “Make it premium” | Explain what the assessment includes and show genuine material or process detail |
| “Make it friendly” | Address the reader directly and explain what happens next without unexplained trade language |
| “Make us sound established” | Use only the verified history supplied; do not imply a founding date or client list |
| “Write for SEO” | Answer the specified task, use the service's ordinary name and keep the page distinct from related pages |
| “Make it long enough” | Cover the agreed questions fully and remove material that does not help answer them |
Google explicitly says it has no preferred word count. Choose length from the information needed, not a supposed search threshold.
Agree how the draft will be reviewed
Separate factual review from editorial review. First check whether the offer, process and limitations are correct. Then decide whether the wording and order make them understandable. Ask one person to consolidate conflicting feedback so the writer receives a clear decision.
Where someone requests a stronger claim, ask for the evidence that would support it. A request to change “we assess wooden chairs” to “we restore every chair to perfect condition” changes the promise, not just the tone.
Hand over enough context to finish the page
Supply the page's intended address, its parent page, the surrounding navigation and relevant next steps. A writer can then explain an item once in the right place and link to detail elsewhere. W3C's writing guidance supports clear headings and meaningful links; the actual page decisions remain specific to the project.
Use the editable content brief to prepare the assignment. The service-page guide turns the fictional brief above into copy, and the editing guide shows how to review the result.
The source notes
Sources and further reading
- Google Search Central: Creating helpful, reliable, people-first content Checked 4 November 2026
- W3C: Writing for Web Accessibility Checked 4 November 2026