intermediate / 45 minutes
SEO Content Brief Template With a Worked Example
Fill an SEO content brief from a query, current search results and source requirements. Keep observations separate from assumptions before handing it to a writer.
Result: A writer-ready SEO content brief with reader task, observed search results, source and claim ledger, distinct answer, section jobs and review owners.
Jump to prompt ↓6 steps to a reviewable draft
- 01
Write the query decision
Define which query and reader task the page should own, plus the proposed URL. Do not treat a keyword list as an article brief.
Result: One primary intent and a boundary against competing pages on the site.
- 02
Record what the SERP shows
Capture current result types, repeated topics, page formats and unanswered reader needs. Preserve URLs and capture dates rather than relying on memory.
Result: A SERP note that distinguishes observation from editorial judgment.
- 03
Check the evidence before outlining
List the claims the page will need, each source and its owner. Mark missing proof rather than asking the writer to fill a gap with plausible copy.
Result: A claim ledger with usable sources and open questions.
- 04
Build the brief
Fill the downloadable form first. If you use an assistant, give it only your captured observations and source ledger; inspect every proposed section before handing the brief to a writer.
Result: A brief that gives the writer a useful page to make instead of a summary of ranking pages.
Your prompt
Create an SEO content brief from the supplied research. Primary query and page purpose: {{query}} Current SERP observations with URLs and dates: {{serp_notes}} Reader task and editorial angle: {{reader_angle}} Claims, exact sources, permissions and owners: {{claim_ledger}} Existing site pages and possible internal links: {{sources_links}} Return a writer-ready brief with the page decision (create, refresh or merge), reader task, direct answer, distinct contribution, section jobs, evidence for each section, internal links, unresolved claims, review owners and freshness triggers. Label an inference as [EDITOR HYPOTHESIS] and an unsupported claim as [NEEDS SOURCE]. Do not invent search volume, ranking difficulty, competitor traffic, Google requirements or source facts.Example inputQuery: seo content brief template. SERP notes: dated links to editable templates and filled examples. Reader: editor assigning a source-grounded page. Claim ledger: template file exists; ranking outcome has no evidence.
Example outputDecision: refresh the existing workflow, not a second URL. Direct answer: link to the blank form. Distinct contribution: a claim/source/owner ledger and a completed brief. Ranking result: [NOT MEASURED]. Review owner: editor.
- 05
Check for overlap
Compare the brief with nearby site pages and the observed results. Merge the angle with an existing page if it would duplicate that page without a new reader benefit.
Result: A distinct page plan with a defensible query boundary.
- 06
Publish the writing brief
Give the writer the completed brief and source links. Name who approves claims and what must be checked before the draft is accepted.
Result: A brief a writer can use without guessing about sources, page purpose or approval.
Worked example: briefing this page
This edited brief was prepared for the page you are reading on 6 October 2026. It shows the decisions behind one assignment, not a measured ranking result. Redo the search and source checks for your own topic.
- Page decision
- Refresh the existing /workflows/content/ai-seo-content-brief/ page. Do not create a second URL for a reordered keyword.
- Primary query and reader task
- seo content brief template. An editor needs a form that tells a writer what to answer, what evidence exists and who approves the draft.
- Search observations, 6 October 2026
- The linked examples offer downloadable or copyable briefs and filled examples. That is a format observation, not evidence that either template improves rankings.
- Existing-site boundary
- The blog-outline workflow owns article structure. This page owns the earlier query, reader, source and assignment decisions.
- Distinct answer
- Give the reader an editable blank brief and a completed example with a claim/source/owner ledger.
- Claim check
- The Markdown file and dated linked examples can be checked. A claim that this method improves rankings has no outcome data and must not be published.
Sources checked: Meridian brief and example, Optiwing Markdown brief
Before handoff, the editor checks that one URL owns the task, each factual claim has a source or a [NEEDS SOURCE] label, and each section serves the reader. The writer drafts from that approved brief; the reviewer checks claims and links before publication.
What a finished draft should contain
A brief with the reader task, dated search observations, source ledger, section jobs and named review checks.
What this process cannot decide
- SERP observations change and do not guarantee a ranking outcome.
- A content brief does not replace editorial judgment or factual research.
- An assistant cannot verify a source you have not supplied or approve a claim for publication.
Questions about this workflow
Can I use the form without an AI assistant?
Yes. Fill the Markdown file directly. The prompt in the workflow is optional; it cannot supply missing research or approve a claim.
What if I cannot verify a claim yet?
Keep it in the ledger as [NEEDS SOURCE], assign an owner and remove any section that depends on it until the evidence arrives.
Should a close keyword variant get another brief and URL?
Usually not. Compare the reader task with the existing owner first. Use one brief when both phrases need the same answer; create a separate page only if the task and useful output differ.
Does the brief need a fixed word count or keyword density?
No. Give each section a job and enough sourced material to answer it. A length target may help a production schedule, but it does not substitute for the reader’s result.
