Lead with the reader and the outcome

A keyword list is research material, not an article brief. Begin the brief with the intended reader, their situation, and the decision or task the page should help them complete. Then identify the page’s role within the site.

For a hypothetical inventory application, a brief about reorder points might target a small retailer trying to avoid stockouts. The outcome is understanding what information is needed to set a reorder threshold, not simply encountering the phrase several times. The writer needs to know whether the page teaches a concept, demonstrates the product, or helps evaluate software. Without that context, even a polished draft may answer the wrong question.

Include only research that changes the article

Provide a representative query, related tasks, a concise search-result observation, and links to reliable sources. Label measured keyword figures with their settings and date if you include them. Separate factual sources from competitor pages used to understand coverage.

For the inventory example, the brief might require a clearly labeled hypothetical calculation, an explanation of assumptions, and a note about variability in supplier lead times. It should not instruct the writer to imitate the headings of the current top result. Explain the useful contribution your article can make: a transparent worksheet, an annotated example, or a product-specific walkthrough verified by someone who knows the workflow.

Specify evidence and boundaries

List claims that need verification, product capabilities that must be checked, and subjects outside the article’s scope. If the draft uses a hypothetical business, require explicit labeling. If it describes an actual customer, require permission and verified details.

The reorder-point article should distinguish a simplified teaching example from an operational recommendation for every retailer. It may explain the inputs without pretending to solve all inventory planning. Give the writer access to a reviewer for uncertain statements. A brief that makes limits explicit reduces revision cycles and prevents AI-assisted drafting from filling gaps with confident guesses. The evidence requirements are more useful than an arbitrary demand to sound authoritative.

Define what makes the draft ready

Use acceptance criteria tied to the reader: the main answer appears early, examples can be followed, terminology is explained, sources support factual claims, and the next step fits the task. Include the intended destination URL so the writer can check for overlap with existing pages.

Before publication, ask someone unfamiliar with the draft to follow the example or explain the decision back in their own words. Revise where they become confused. After publication, return observed query and reader feedback to the brief template. A good brief evolves from actual editorial problems. It should make the writer’s work clearer and the article more useful, rather than turning the keyword spreadsheet into a rigid formula for every page.

Attach one example of an acceptable explanation and one known pitfall from past drafts so the writer can apply the criteria concretely.

PUT IT TO WORK

A useful brief explains what the reader needs, what evidence the writer must use, and how the finished article will be judged.

Sources & further reading

Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.

THE WORKSPACE WE'RE BUILDING

From search signals to a useful first draft.

SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.

Join early access ↗