O Construtor de Briefings de Conteúdo SEO: Transforme uma Palavra-Chave em um Briefing Completo Pronto para o Redator
Porque é que este prompt importa
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.
Para que o usamos
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"]
Resultado
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.
A maioria dos briefings de conteúdo falha pelo mesmo motivo: entregam ao redator uma palavra-chave e uma contagem de palavras e consideram o trabalho concluído, deixando cada decisão estratégica real — qual ângulo adotar, o que a concorrência está deixando passar, se a intenção realmente corresponde ao significado superficial da palavra-chave — para ser adivinhada no meio do rascunho. Este prompt existe para antecipar essas decisões antes que uma única frase seja escrita.
Por que a intenção de busca vem primeiro, não por último
Classificar a intenção antes de tudo força uma verificação de bom senso que a maioria dos briefings ignora completamente: a palavra-chave realmente significa o que parece significar à primeira vista?
Por que a análise de lacunas dos concorrentes precisa ser específica, não genérica
"Os concorrentes não cobrem bem isso" não é útil sem nomear exatamente o que eles deixam de lado. O prompt exige 3 a 5 lacunas concretas e nomeadas — um detalhe de preço ausente, uma objeção não tratada, uma oportunidade estrutural como uma tabela comparativa.
Por que a verificação de canibalização é uma etapa obrigatória, não uma reflexão tardia
Editores com uma biblioteca de conteúdo estabelecida correm um risco silencioso toda vez que encomendam uma nova peça direcionada a uma palavra-chave: criar sem querer uma segunda página que compete com uma já existente pelos mesmos termos de busca.