SEO Content Brief (Search Intent to Editorial Plan)
This workflow creates an editorial brief that connects the reader's actual task to a clear article structure. It separates verified facts from assumptions, identifies what original contribution the article can make, and gives writers a practical plan without treating keyword repetition as a strategy.
GPT / Claude / Gemini6 variables
Prompt
Create an editorial SEO content brief for {TOPIC}.
Audience: {AUDIENCE}
Site or product context: {SITE_CONTEXT}
Reader's task: {READER_TASK}
Existing related URLs: {RELATED_URLS}
Available primary sources: {SOURCES}
Requirements:
- State the reader's problem and the page's specific promise.
- Distinguish verified facts, assumptions, and questions requiring research.
- Do not invent search volume, ranking difficulty, statistics, quotations, or source findings.
- Propose a useful outline based on reader needs, not copied competitor headings.
- Identify what original analysis, example, test, or decision aid could make the page valuable.
- Flag overlapping URLs and explain whether to update, combine, or create a page.
- Suggest relevant internal links only when the destination genuinely helps the reader.
Output:
1. Audience and intent
2. Page promise and scope exclusions
3. Proposed title and outline
4. Questions the article must answer
5. Evidence and source plan
6. Original contribution
7. Internal-link opportunities
8. Risks, unknowns, and pre-publication checklist
Topic: {TOPIC}Quick brief
Purpose
Turn a topic into a useful, evidence-led brief before drafting.
Expected output
A brief containing audience, search task, page promise, scope boundaries, proposed title and H2 outline, questions to answer, primary-source requirements, internal-link opportunities, differentiating evidence, and a pre-publication verification checklist.
Customize before copying
Replace these placeholders with your own context before you run the prompt.
{TOPIC}{AUDIENCE}{SITE_CONTEXT}{READER_TASK}{RELATED_URLS}{SOURCES}
Works well with
GPT
Claude
Gemini
Variations
Create a short brief for a product comparison with an explicit evaluation methodology.
Turn a verified support-ticket theme into a documentation brief.
Audit a proposed brief for overlap with existing pages before drafting.
What this prompt helps you do
This workflow creates an editorial brief that connects the reader's actual task to a clear article structure. It separates verified facts from assumptions, identifies what original contribution the article can make, and gives writers a practical plan without treating keyword repetition as a strategy.
When to use it
Use before writing a guide, comparison, tutorial, or explainer. It is especially useful when several pages target related topics and the team needs to avoid cannibalization, shallow coverage, and duplicated sections.
Decision context
A brief is worth creating when the topic needs research, multiple sections, or coordination between writers and reviewers. For a short announcement or a simple factual update, a lightweight outline may be enough. Search volume alone is not evidence that a page deserves to exist.
How it works
The model first defines the reader and their task, then lists the questions the page must answer, the evidence required, and the original value the article can add. It proposes a structure only after the purpose is clear. Unsupported claims and missing sources are called out rather than filled with invented details.
Best practices
Supply the intended audience, product context, primary sources, and competing pages you have actually reviewed. Ask for a source plan and verification checklist. Have an editor confirm the angle and factual claims before publication.
Common mistakes
Do not treat suggested keywords as mandatory phrases, invent search-volume data, copy competitors' headings, or publish a brief as if its assumptions were verified research. Avoid making multiple near-identical pages for tiny keyword variations.
What you should expect back
A brief containing audience, search task, page promise, scope boundaries, proposed title and H2 outline, questions to answer, primary-source requirements, internal-link opportunities, differentiating evidence, and a pre-publication verification checklist.
Limitations
A language model cannot reliably infer live search demand or verify a source it has not accessed. The brief is a planning artifact, not proof that the topic has traffic or that a page will rank.
Model notes
Works with GPT, Claude, Gemini, or another capable text model. Provide source URLs or excerpts when factual verification matters.
Real-world applications
Editorial teams use it to standardize briefs, solo publishers use it to reduce research drift, and product teams use it to plan documentation around real user problems.
How to tell if it worked
The writer can explain the page's unique purpose, every important claim has an evidence plan, the outline answers the reader's task, and the final page does not duplicate an existing URL.
Where to go next
Pair with the source-grounded research brief and content quality audit prompts in this collection.
Appears in collections
Related prompts
Source-Grounded Research Brief (Claims, Evidence, Unknowns)
Build a research trail that makes factual writing easier to verify.
Content Quality Audit (Originality, Accuracy, Reader Value)
Review a draft for usefulness and credibility before publishing.
SEO Keyword Research and Search Intent Mapper
Turn seed topics and verified keyword data into a focused content plan.
Product Review Brief (Balanced + Credible)
Write reviews that don't sound like paid ads.
Landing Page Copy Audit (Fix Confusing Text)
Improve website copy so users understand it in 5 seconds instead of leaving.
User Research Synthesis (Patterns to Insights)
Transform raw user research data into actionable insights and recommendations.