The SEO Content Brief Builder: Turn a Target Keyword Into a Complete Writer-Ready Brief
Why this prompt matters
A brief missing explicit search intent and competitor gaps forces the writer to guess at structure and depth, and guessed drafts get rejected on the first read nearly every time — triggering a full rewrite cycle that adds days to a piece and erodes trust with freelance writers who start declining rush assignments from clients whose briefs are never clear.
What we use it for
A content marketer at a project-management SaaS startup gets assigned the keyword "asana alternatives for small teams" during Monday sprint planning, with nothing but the keyword and links to three ranking competitor articles, and needs a brief a freelance writer can execute the same day without a clarifying call.
Prompt
Role: You are a senior SEO content strategist who has planned briefs for articles that reached page-one rankings in competitive B2B SaaS categories. Context: - Target keyword: [TARGET KEYWORD] - Target audience: [TARGET AUDIENCE, e.g. "ops managers at 10-50 person startups"] - Top 3-5 ranking competitor URLs or pasted article summaries: [PASTE COMPETITOR URLS OR SUMMARIES HERE] - Brand voice notes: [BRAND VOICE NOTES, e.g. "no jargon, practical, slightly opinionated"] - Word count constraint if any: [WORD COUNT TARGET, or "use your judgment based on competitor length"] Task: Produce a complete, writer-ready content brief for this keyword. The brief must include: 1. Search intent classification (informational / commercial / transactional / navigational) with a one-sentence justification 2. A recommended H2/H3 outline a writer can follow section by section 3. A competitor gap analysis: 3-5 specific subtopics or angles the ranking competitors miss or cover shallowly 4. A target word count, justified by what's actually ranking (not a generic guess) 5. 3-5 internal linking suggestions (described generically since you don't have my site map — describe what kind of page each link should point to) 6. A meta title (under 60 characters) and meta description (under 155 characters) 7. Primary keyword and 3-5 secondary/LSI keywords to weave in naturally Constraints: - Do not write the actual article body — only the brief - Do not recommend keyword stuffing or unnatural repetition - Flag if the keyword risks cannibalizing an existing likely page on the same topic - If the competitor summaries suggest the real search intent differs from what the keyword implies at face value, call that out explicitly - Keep the brief scannable — headers and bullet points, not paragraphs Output Format: ## Search Intent [classification + justification] ## Recommended Outline [H2/H3 structure] ## Competitor Gap Analysis [bulleted list] ## Target Word Count [number + justification] ## Internal Linking Suggestions [bulleted list] ## SEO Metadata - Meta Title: - Meta Description: - Primary Keyword: - Secondary Keywords: ## Cannibalization Check [flag or "no risk identified"]
Result
Example: keyword = "asana alternatives for small teams"
## Search Intent
Commercial investigation. Searchers already use or have evaluated Asana and are actively comparing switching options — this is not someone learning what project management software is. The phrase "for small teams" signals a specific filtering need (cost, simplicity) rather than enterprise feature depth.
## Recommended Outline
H2: Why Small Teams Outgrow or Reject Asana (cost per seat, feature bloat, onboarding friction)
H2: What to Look For in a Small-Team PM Tool (5 criteria, not generic "ease of use")
H2: Top 7 Alternatives, Ranked by Use Case
— H3 per tool: Best for [specific team type], pricing at 10-seat tier, one real limitation
H2: Comparison Table (price, seat minimums, free tier, standout feature)
H2: How to Migrate Your Existing Asana Boards Without Losing History
## Competitor Gap Analysis
- Both ranking competitors list tools but never mention seat-minimum pricing traps (several "cheap" tools require 5+ seats minimum)
- Neither addresses migration — a top-3 actual objection in review sites' comments
- Neither ranks tools by team type (agency vs. internal ops vs. dev team), just alphabetically or by "best overall"
- No competitor includes a comparison table — a clear structured-data opportunity for a featured snippet
## Target Word Count
1,800-2,200 words. The two ranking articles are 1,600 and 2,400 words; matching the upper range with denser, more specific content (not padding) is achievable given the gaps above.
## Internal Linking Suggestions
- Link to a project-management-software-pricing comparison page, if one exists
- Link to a "how to migrate data between SaaS tools" guide
- Link to individual tool review pages for the top 2-3 alternatives if your site has them
## SEO Metadata
Meta Title: 7 Asana Alternatives for Small Teams in 2026 (With Real Pricing)
Meta Description: Asana too expensive or bloated for your 10-person team? Compare 7 alternatives by price, seat minimums, and migration effort — no vendor fluff.
Primary Keyword: asana alternatives for small teams
Secondary Keywords: cheap project management software, asana vs [competitor], small team PM tools, migrate from asana
## Cannibalization Check
Flag: if your site already has a general "best project management software" post, this brief overlaps on tool coverage. Differentiate by keeping this one strictly filtered to small-team pricing and migration — do not let it drift into a generic "best PM tools" roundup or it will compete with your existing page in search results.
Most content briefs fail for the same reason: they hand a writer a keyword and a word count and call it done, leaving every actual strategic decision — what angle to take, what the competition is missing, whether the intent even matches the keyword's surface meaning — to be guessed at mid-draft. This prompt exists to front-load those decisions before a single sentence gets written.
Why search intent comes first, not last
Classifying intent before anything else forces a sanity check most briefs skip entirely: does the keyword actually mean what it looks like it means? A phrase like "asana alternatives" reads as pure comparison shopping, but competitor content sometimes reveals people are really asking "is Asana overkill for us" — a different question that needs a different outline. Catching that mismatch before the outline is written saves a full rewrite later.
Why the competitor gap analysis has to be specific, not generic
"Competitors don't cover this well" is not useful without naming exactly what they skip. The prompt forces 3-5 named, concrete gaps — a missing pricing detail, an unaddressed objection, a structural opportunity like a comparison table — because those are the things that actually differentiate a new article from the five that already rank. Vague competitive advantage claims don't move rankings; specific missing subtopics do.
Why the cannibalization check is a mandatory step, not an afterthought
Publishers with an established content library run a quiet risk every time they commission a new keyword-targeted piece: unknowingly creating a second page that competes with an existing one for the same search terms, splitting authority instead of building it. Making the model flag this explicitly — even when it just says "no risk identified" — builds the habit of checking before writing, not after two competing pages are already both underperforming.