An SEO content brief tells a writer which reader question a page should answer, why the page is useful, what it must cover, and which evidence supports its claims. A good template separates required decisions from suggestions so the writer can improve the prose without guessing the assignment.
Use the template below for a new article or an existing-page update. It is a planning document you can copy into your own editor. It does not require you to include a statistic, quotation, table, or FAQ in every piece.
What the Brief Needs to Resolve
Start with the audience and the decision. “Write about onboarding” leaves too much unresolved. “Help a SaaS operations lead prepare the information needed before onboarding a new customer” gives the writer a reader, a task, and a boundary.
Add a primary query and a small set of supporting questions. These are research inputs, not a repetition target. A brief should explain why a supporting term belongs, rather than distribute keywords across headings mechanically.
Then identify the source of truth. Product capabilities should come from current product information; a customer quotation needs its actual wording, attribution, and permission; a numerical comparison needs compatible definitions and dates. Competitor pages can show how a topic is framed, but do not automatically establish facts about your product.
Copyable SEO Content Brief Template
| Field | What to enter |
|---|---|
| Page goal | What the reader should understand, decide, or do |
| Audience | Role, experience, situation, and relevant constraint |
| Primary query and intent | The main question and expected answer format |
| Existing page check | Current URL to improve, or reason a new page is needed |
| Supporting questions | Related questions that belong inside this answer |
| Angle | The useful example, method, or evidence this page contributes |
| Required coverage | The specific points an editor must be able to find |
| Exclusions | Adjacent topics and claims the article should not introduce |
| Outline | Ordered sections with one reader task per section |
| Facts and attribution | Product facts, supplied expertise, dates, and permitted claims |
| Source requirements | Eligible pages and which claims each source supports |
| Article elements | Quotes, stats, FAQ, comparison table, takeaways, and whether they help |
| Voice and reading level | Practical guidance with an example of the desired tone |
| Links and next step | Relevant internal destinations and the action they support |
| Editorial checks | What must be verified before the copy is approved |
Add production ownership and deadlines in your tracker. Keep the editorial brief focused enough that the writer can identify the essential decisions quickly.
A Filled SaaS Brief
This is an illustrative assignment, not a record of customer research or measured keyword demand.
Working title: A Customer Onboarding Checklist for a Small SaaS Team.
Page goal: help an operations lead prepare a clear handoff before onboarding starts.
Audience: a small SaaS team introducing a repeatable onboarding process without a dedicated operations department.
Primary question: what information and responsibilities should be confirmed before the first onboarding session?
Supporting questions: who owns each task, which information the customer supplies, how unresolved questions are tracked, and what counts as a completed handoff.
Angle: one copyable handoff table that distinguishes required inputs, owners, and the evidence that a task is complete.
Required coverage: define the handoff; identify customer and internal owners; list the information to gather; explain how to handle a missing input; show a final review checklist.
Exclusions: do not rank software, invent completion-rate statistics, promise a particular implementation time, or describe the example as a customer success story.
Source requirements: the article's practical checklist can be presented as an editorial method. Any statement about a particular software feature must be checked against that product's current documentation before inclusion. No customer quote is supplied, so a quotation is not required.
Article elements: a checklist is useful; a FAQ can address genuinely unresolved reader questions. A comparison table of software is outside this assignment. Numerical statistics are optional and should be omitted if no relevant evidence is available.
Voice: direct and practical. Explain an unfamiliar term when it first appears. Describe the reader's next decision rather than promising effortless growth.
Next step: copy the handoff table, assign owners, and discuss missing inputs before writing a separate software-evaluation brief.
Give Each Heading a Job
The outline for this brief could contain five sections: define the handoff; gather customer inputs; assign internal owners; resolve missing information; approve the checklist. Under each heading, record the decision the reader should make.
The writer can propose a clearer heading without changing the article's purpose. If a new section introduces software rankings or performance claims, it changes the assignment and should be reviewed before drafting.
Keep length guidance proportional to the question. A target length helps production planning; it does not establish a preferred word count for search engines. Add examples and detail where they improve the answer, not to fill a quota.
Review the Brief Before Requesting Prose
Ask whether a writer unfamiliar with the product could distinguish a supplied fact from an instruction, find the source for each specific claim, and recognize which elements are optional. Resolve those gaps before generation.
After drafting, check the actual article against the brief. Confirm the main answer appears early, required coverage is present, quotations are accurate, sources support the statements attached to them, and links lead to appropriate destinations. Remove unsupported claims instead of attaching a vaguely related citation.
In RoboWrite, a brief can shape a Content Kit containing the outline, supporting claims, and selected components. Element controls vary: some support Required, Optional, or Off, while citations and unsupported elements have different rules. A missing required element can need review rather than being fabricated.
For the product process rather than another blank template, read how to turn a brief into a Content Kit.
Add a Claim-to-Source Handoff
A source list becomes more useful when the writer can see which statement each source is meant to support. Add a small evidence map alongside the brief. The following entries continue the fictional SaaS onboarding assignment, rather than reporting a real product test.
| Proposed statement | Evidence required | Writer action if it is missing |
|---|---|---|
| A particular role can approve a handoff | Current process or permission record | Keep the role unnamed until the owner confirms it |
| An integration imports an existing checklist | Current product documentation for that integration | Omit the capability claim rather than infer it from a logo |
| A customer described a specific obstacle | Accurate interview note with its original context | Paraphrase only within the permitted editorial use; do not invent a quotation |
| A method reduces completion time | A relevant measurement with definitions and dates | Describe the method without the unverified performance claim |
The evidence map is a review aid, not a requirement to cite a source after every ordinary recommendation. Use it for consequential product facts, numerical claims, quotations, and statements a reviewer needs to check.
When interviews supply the initial angle, follow the interview-to-content-pillar workflow before turning every interesting phrase into a keyword assignment. When brief preparation is repeated across a knowledge base, the content brief automation workflow shows how to keep source versions and review ownership explicit.
Next Step
Copy the template and complete it for one SaaS buyer question. Then explore RoboWrite Content Kits to see how a familiar brief becomes explicit article requirements and a reviewable research plan.
Sources and Further Reading
- Google's people-first content guidance.
- RoboWrite Public API guide: Content Kits, supplied facts, article requirements, and review behavior.
