Last reviewed: April 25, 2026 · Format: copy-ready prompt workflow · Human-reviewed
SEO Content Brief Prompt Template for Search, AI Answers, and Human Editors
Use this copy-ready prompt to turn a target keyword, SERP notes, competitor gaps, entities, internal links, citation requirements, CTA, and schema recommendations into a practical SEO content brief a writer can actually execute.
Who this is for
Founders, marketers, editors, agencies, consultants, SaaS teams, ecommerce teams, and SEO operators who need repeatable briefs for writers or AI-assisted drafting.
Who should skip this
Skip it if you want one-click article generation, plan to publish without human review, or do not have a real page goal, search intent, and source strategy.
Best use case
Use it before drafting pillar pages, comparison pages, buying guides, product-led educational pages, and high-intent blog posts that need editorial control.
Quick SEO brief workflow
| Step | What to provide | What the AI should return |
|---|---|---|
| 1. Query and intent | Primary keyword, secondary keywords, audience, funnel stage, target country/language. | Intent classification, page type, angle, and success criteria. |
| 2. SERP observations | Top ranking URLs, headings, snippet formats, PAA questions, competitor strengths and weak spots. | Format recommendation, gap list, and “must cover / should avoid” notes. |
| 3. Entity coverage | People, tools, concepts, standards, data points, features, problems, alternatives. | Entity map, definitions, and places where citations are required. |
| 4. Brief output | Brand voice, CTA, internal links, examples, constraints, schema needs. | Writer-ready outline, section instructions, FAQs, links, sources, and QA checklist. |
Copy-ready SEO content brief prompt

You are an expert SEO strategist, content editor, and search-quality reviewer. Build a writer-ready SEO content brief using the inputs below. Do not write the full article yet. Create a brief that a human writer can use to produce a useful, accurate, differentiated page.
INPUTS
Primary keyword: {insert}
Secondary keywords: {insert}
Target audience: {who is searching and what they already know}
Search intent: {informational / commercial / transactional / local / mixed}
Funnel stage: {top / middle / bottom}
Target geography/language: {insert}
Page type: {guide / comparison / product page / landing page / tutorial / checklist}
Business goal: {lead, sale, signup, internal education, trust}
Offer or CTA: {insert}
Brand voice: {plainspoken, expert, practical, etc.}
Existing internal links to consider: {URLs + preferred anchor context}
External sources required: {official docs, studies, standards, credible publications}
SERP observations: {top-ranking pages, PAA questions, featured snippets, competitor gaps}
Competitor pages to beat: {URL + what each does well/poorly}
Entities to include: {people, tools, topics, standards, features, alternatives}
Constraints: {claims to avoid, legal/medical/financial limits, product limits}
TASK
1. Identify the dominant search intent and the page format most likely to satisfy it.
2. Summarize the user’s real problem in 40–60 words.
3. List the SERP patterns: common headings, tables, snippets, questions, and missing angles.
4. Build an entity and subtopic map with required definitions and citation points.
5. Recommend a title tag, H1, meta description, and URL slug.
6. Create a detailed H2/H3 outline. For each section, specify: purpose, key points, examples, data/source needs, and the question it answers.
7. Add a direct-answer block, comparison table plan, decision framework, common mistakes, FAQ, and related-next-reads section.
8. Map internal links by section with natural anchor text and reason for inclusion.
9. Recommend external source types and exact claims that require citations.
10. Recommend schema opportunities only if they match visible content: Article, FAQPage, HowTo, Product, ItemList, BreadcrumbList, or none.
11. Add an editorial QA checklist covering accuracy, originality, E-E-A-T, freshness, internal links, duplicate H1 risk, and unsupported claims.
12. Flag where AI should not invent facts and where a human expert must review.
OUTPUT FORMAT
- Search intent decision
- SERP gap summary
- Entity/subtopic map
- Metadata recommendations
- Writer-ready outline
- Internal-link map
- Source/citation plan
- FAQ candidates
- Schema recommendation
- Human editorial checklist
- Final “publish / revise / reject” criteriaExample input
Primary keyword: AI prompts for sales emails Secondary keywords: ChatGPT sales email prompts, cold email prompts, follow-up email prompt Audience: B2B founders and marketers who need better outbound emails Search intent: commercial-informational Page type: prompt library page Business goal: free prompt usage and Operator Pack product interest CTA: PromptGrade and AI Revenue Operator Pack SERP observations: Many ranking pages list generic prompts but lack segmentation by use case, buyer awareness, proof, objections, and follow-up logic Entities: sales emails, cold outreach, buyer persona, pain point, offer, proof, objection handling, CTA, sequence, deliverability Internal links: /ai-prompt-library/, /outreach-email-prompt/, /promptgrade/, /product/ai-revenue-operator-pack-product/
Example brief output excerpt
Recommended page angle
Create a practical sales-email prompt workflow, not a generic prompt list. The page should show how to brief the AI with buyer context, pain, proof, objection, offer, sequence stage, tone, and deliverability constraints.
Core sections
- Direct answer: define what a strong sales-email prompt must include.
- Prompt table: segment by cold email, follow-up, reactivation, upsell, webinar invite, and breakup email.
- Decision framework: when to use AI, when to write manually, and what a human must approve.
- Source plan: cite email compliance/deliverability guidance only for legal or deliverability claims.
SEO brief quality checklist

| Intent | The brief states the dominant intent, page type, audience sophistication, and action the reader should take next. |
|---|---|
| SERP analysis | The brief compares ranking formats and explains how the page will be more useful, not just longer. |
| Entity coverage | Important people, tools, concepts, standards, features, alternatives, and risks are defined or assigned to sections. |
| Internal links | Links are mapped by reader need, not dropped in as generic SEO anchors. |
| Citations | Any statistic, standard, policy, or technical claim has a source requirement. |
| Editorial safety | The brief flags unsupported claims, YMYL limits, product limitations, and human review points. |
When not to use AI for SEO briefs
Do not let AI invent SERP research, quote fake statistics, create legal or medical advice, fabricate experience, or decide product claims without evidence. Use AI to structure the brief; use human research and credible sources to validate it.
Common mistakes
- Asking for “an SEO optimized article” instead of briefing intent, SERP gaps, entities, and evidence.
- Using the same outline for every keyword regardless of query intent.
- Adding FAQ schema when the visible page does not include matching FAQ content.
- Ignoring internal-link context and linking only for keyword anchors.
- Publishing AI claims without checking the source, date, or applicability.
FAQ
Can this prompt write the article too?
It can, but the safer workflow is brief first, draft second, edit third. A strong brief gives the writer or AI model constraints before drafting starts.
Should every page include FAQ schema?
No. Use FAQ schema only when the page visibly includes useful FAQ content and the implementation is handled properly by the SEO plugin or theme layer.
How many internal links should a brief include?
Use as many as genuinely help the reader. For important pages, 6–10 contextual links is often useful, but relevance matters more than count.
Sources
Related next reads
- AI Prompt Library — browse the main workflow library.
- Offer Positioning Prompt — clarify the message before building content.
- Landing Page Copy Prompt — turn a brief into conversion copy.
- PromptGrade — score and improve the prompt before using it.