The content brief is the critical document that sits between keyword research and actual article writing. A good brief takes 3-4 hours to create—even for experienced SEO professionals. It requires synthesizing keyword data, competitor analysis, search intent classification, and existing on-page performance into a single structured document that writers can execute against.
Claude Cowork eliminates the manual synthesis work. Upload your keyword data, SERP results, and any existing content metrics, and Cowork generates a complete, publication-ready brief in 5-10 minutes. This article walks through the exact process: what data you need, how to configure Cowork's Content Brief skill, what a complete brief looks like, and how to iterate and refine outputs based on your writer's feedback.
Teams using this workflow report saving 2.5 hours per brief, which compounds across dozens of articles per quarter. For context on how content briefs fit into your broader Cowork SEO strategy, see Claude Cowork for SEO Specialists: The Complete Playbook. For brand managers producing campaign-level creative briefs rather than SEO content briefs, the methodology differs—see our dedicated guide to Claude Cowork for campaign briefs, which covers messaging hierarchies, creative territory development, and agency-ready brief output.
What a Complete Content Brief Contains
Before automating brief generation, you need to understand what a complete brief includes. Underspecified briefs fail—writers struggle to know what to write, leading to drafts that miss the mark and require heavy rewrites. Over-specified briefs waste time—you're writing the article twice.
A strong content brief includes:
- Target keyword and LSI keywords: Primary keyword, 2-3 secondary keywords, 4-5 related terms writers should naturally incorporate
- Search intent classification: Transactional, informational, commercial investigation, navigational—this determines content structure and CTA placement
- Headline recommendations: 3-4 title options tested against competitor headlines for clarity and keyword inclusion
- Meta description template: 150-160 character version optimized for click-through
- Target reader persona: Who are we writing for? Level of expertise? Job role? Decision-making authority?
- Content structure/outline: Section-by-section outline with H2, H3 headers and bullet points describing what each section should cover
- Content depth benchmark: Average word count, number of sections, expected list items—based on what competitors publish
- SERP feature opportunities: Are competitors capturing featured snippets? Image carousels? Video? What format should we target?
- Competitor analysis summary: What are the top 3 ranking competitors covering? What's missing or weak in their coverage that we can outrank them with?
- Internal linking recommendations: 3-5 other pages on our site that should link to this new article (pillar pages, related content, etc.)
A brief at this level of detail provides writers with clear direction without being overly prescriptive. They know the target structure, the content gaps they need to fill, and how this fits into your site's broader architecture.
What Data You Need Before Starting
Core Data Inputs
Cowork's Content Brief skill requires these inputs to generate a quality brief:
- Target keyword(s) — Your primary keyword plus any secondary keywords (usually 1-3 keywords per brief)
- SERP data for that keyword — Top 10 ranking URLs, page titles, meta descriptions, current SERP features. Export from SEMrush or Ahrefs.
- Search volume and difficulty metrics — Estimated monthly searches and keyword difficulty score
- Your content inventory — List of existing pages on your site that are relevant to this topic (for internal linking recommendations)
Optional But Recommended Data
- Page content from top 3 competitors (what sections do they have? How long is each section?)
- Current rank position for this keyword (if you're updating an existing page)
- User intent data from GA4 or search analytics (what are searchers actually clicking on in the SERP?)
- Your content calendar (what topics are already scheduled?)
Step-by-Step Brief Generation Process
Step 1: Prepare Your Keyword Research Data
Start with your keyword research. In SEMrush or Ahrefs, run a keyword cluster analysis to identify your target keyword plus related search terms. Export as CSV with these columns:
- Keyword
- Search Volume
- Difficulty
- Intent
- Current Rank (if updating existing content)
For a new article, you'll typically focus on one primary keyword, though Cowork can handle 2-3 related keywords if you're writing a comprehensive guide.
Step 2: Export SERP Data
Export the top 10 ranking results for your target keyword. In SEMrush:
- Keyword Research → Organic Search
- Enter your target keyword
- Scroll to SERP Results section
- Click the export icon and select CSV
- Ensure export includes: URL, title, meta description, traffic, position
You now have a structured view of what's currently ranking and how your competitors are optimizing titles and meta descriptions.
Step 3: Gather Competitor Content Outline
For each of the top 3 competitors, visit their ranking page and document their content structure. You can do this manually (copy their outline) or use a tool like Screaming Frog to extract heading structure. Create a simple CSV or text file noting:
- Competitor domain
- URL rank position
- Page title
- Main sections (H2 headings)
- Estimated content length
This data helps Cowork identify content gaps—topics competitors cover that you're missing, or sections where competitors are weak.
Step 4: Create Your Content Inventory List
Create a simple CSV of your existing content that's related to this topic. This enables Cowork to generate internal linking recommendations. Include:
- Page URL
- Page title
- Word count
- Primary topic/keyword
Step 5: Configure Cowork Content Brief Skill
In your Cowork workspace:
- Create a new Skill or use the existing "Content Brief" skill template
- Set the skill type to "Text Processing"
- Upload your keyword CSV, SERP data CSV, and competitor outline document
- Add your content inventory as an additional input
- Use the prompt template below to configure the skill's instructions
Step 6: Execute Brief Generation
Once configured, execute the skill. Cowork will process your input data and generate a complete brief, typically in 2-5 minutes depending on data volume.
Step 7: Review and Iterate
Review the generated brief. If sections are missing, structural elements need adjustment, or you want different headline options, edit the prompt template and re-run. Most briefs require 1-2 iterations to match your team's preferences.
Sample Brief Structure Output
Here's what a generated brief looks like (formatted for a hypothetical keyword about "API rate limiting"):
TARGET KEYWORD: API rate limiting
SECONDARY KEYWORDS: rate limits, request throttling, API gateway
SEARCH VOLUME: 4,200/month
KEYWORD DIFFICULTY: 28/100
HEADLINE OPTIONS:
1. "API Rate Limiting: Best Practices and Implementation Guide"
2. "How to Implement Rate Limiting: A Developer's Guide"
3. "API Rate Limiting Strategies for Production Systems"
META DESCRIPTION (155 char):
"Learn how to implement API rate limiting in your backend. Complete guide covering algorithms, best practices, tools, and code examples for production systems."
TARGET READER PERSONA:
Backend engineers and API developers building production systems. 3-5 years of experience. Need practical, code-forward explanations with working examples.
CONTENT STRUCTURE:
H2: What is API Rate Limiting? (300 words)
- Definition and why it matters
- Impact on system stability and user experience
- Real-world scenarios where rate limiting prevented outages
H2: Common Rate Limiting Algorithms (800 words)
H3: Token Bucket Algorithm
H3: Sliding Window Counter
H3: Leaky Bucket Algorithm
H3: Fixed Window Counter
- Pros/cons of each
- Performance implications
- When to use which algorithm
H2: Implementation Approaches (600 words)
H3: Server-Side Rate Limiting
H3: API Gateway Rate Limiting
H3: Client-Side Rate Limiting
- Code examples (Python, Node.js, Java)
- Configuration patterns
- Monitoring and alerting
H2: Rate Limiting Best Practices (400 words)
- Graceful degradation
- User communication strategies
- Handling bursty traffic
- Testing your rate limits
H2: Tools and Libraries (300 words)
- Redis-based solutions
- API gateway options (Kong, AWS API Gateway, Cloudflare)
- Framework-specific libraries
- Monitoring solutions
FEATURED SNIPPET OPPORTUNITY:
Competitors rank for snippet, format: Definition. Current snippet is generic. Recommendation: Create a concise, 2-sentence definition of API rate limiting in an opening callout box, immediately after the H1.
INTERNAL LINKING RECOMMENDATIONS:
Link to: "API Throttling vs Rate Limiting" (differentiation)
Link to: "Backend Performance Monitoring" (monitoring/observability)
Link to: "Building Scalable APIs" (pillar page on API architecture)
CONTENT DEPTH BENCHMARK:
Average competitor word count: 2,400-3,000 words
Number of sections: 5-7 main sections
Code examples: 3-5 working code snippets
Estimated read time: 8-10 minutes
COMPETITIVE ANALYSIS SUMMARY:
- All top 3 competitors cover the core algorithms (standard content)
- Competitor A has weak implementation section (opportunity to outrank with detailed code examples)
- Competitor B missing discussion of API gateway solutions (coverage gap we can fill)
- Competitor C has outdated rate limiting library recommendations
- EDGE: Deep code examples + modern tool recommendations = opportunity for top 3
This level of structure takes a human 3-4 hours to assemble. Cowork produces it in 5 minutes.
The Three Prompt Templates You'll Use
Template 1: Core Brief Generation
Use this when starting from raw keyword data and SERP results:
Generate a detailed content brief for this keyword. The brief is for internal writer handoff—it should be prescriptive enough to guide the writer but not overly rigid.
INPUT DATA:
- Target keyword(s): [keyword]
- Search volume: [volume]
- Keyword difficulty: [difficulty]
- Top ranking competitors: [list URLs]
ANALYSIS REQUIRED:
1. Classify search intent: Is this informational, commercial, or transactional?
2. Analyze competitor content: What are the top 3 competitors covering? What's missing?
3. Identify content gaps: What topics do competitors undercover or miss entirely?
4. Recommend content structure: What H2 and H3 sections should we create?
OUTPUT FORMAT (exactly as specified):
- Target keyword and LSI terms
- 3-4 headline options
- Meta description (155 characters)
- Target reader persona
- Detailed outline (H2s with descriptions, H3 options below each)
- Word count benchmark from competitor analysis
- Featured snippet opportunity (if applicable)
- Internal linking recommendations (3-5 internal pages)
- Competitive edge statement: "How we'll outrank current top 3"
Make the outline specific. For each section, include 1-2 sentence description of what the writer should cover. Include any statistics, examples, or proof points they should include.
Template 2: Refining Based on Competitor Content
Use this after you've reviewed competitor pages and want more granular structure:
Refine this content brief based on detailed competitor content analysis.
COMPETITOR 1 STRUCTURE: [paste competitor 1 outline]
COMPETITOR 2 STRUCTURE: [paste competitor 2 outline]
COMPETITOR 3 STRUCTURE: [paste competitor 3 outline]
CURRENT BRIEF: [paste the brief generated in Template 1]
REFINEMENT INSTRUCTIONS:
1. Identify sections that appear in ALL top 3 competitors (these are table-stakes—must include)
2. Identify sections unique to one competitor (consider if we should include or skip)
3. Find obvious content gaps: topics competitors miss that we can uniquely cover
4. Recommend merged/combined sections where competitors cover similar topics with different names
5. Update the outline to: Include all table-stakes sections + our unique angle sections + strategic gaps
Output the REFINED outline only (don't repeat previous analysis). Include section order and estimated word allocation per section.
Template 3: Iterating with Writer Feedback
Use this when your writer provides feedback on the brief structure:
Update the content brief based on writer feedback.
ORIGINAL BRIEF: [paste current brief]
WRITER FEEDBACK: [paste specific feedback, e.g., "Section on implementation is too vague", "No mention of x framework"]
REVISION INSTRUCTIONS:
1. Expand or clarify sections the writer flagged
2. Add missing topics they mentioned (with estimated word count and placement in the outline)
3. Maintain overall structure but tighten descriptions
4. Add any specific examples or resources they requested
5. Keep the brief actionable and specific (not vague)
Output: REVISED BRIEF OUTLINE (sections marked as [NEW] if added, [EXPANDED] if updated)
How to Save 2.5 Hours Per Brief
The time savings come from automating the synthesis work, not the creative work:
- Competitive analysis: Manual reading of top 10 ranking pages takes 45-60 minutes. Cowork's analysis takes 2 minutes.
- Outline generation: Synthesizing competitor structures into a unique outline takes 60-90 minutes. Cowork does this in 2-3 minutes.
- Headline testing: Coming up with 3-4 headline variations and checking them against competitor headlines takes 20-30 minutes. Cowork generates these immediately.
- Internal linking research: Reviewing your content inventory and identifying 3-5 linking opportunities takes 15-20 minutes. Cowork recommends these in 1 minute.
Total manual time saved per brief: 2.5-3 hours. For teams writing 20 articles per quarter, this is 50+ hours saved—more than one person's entire output.
Quality Control: When to Reject a Generated Brief
Cowork's outputs are usually strong, but not perfect. Reject or heavily revise a brief if:
- Search intent classification is wrong: You know your audience. If Cowork classified this as "informational" but you know it's "commercial," fix it and re-run.
- Outline misses critical sections: If a section that matters to your audience is missing, add it manually or use Template 2 to refine.
- Word count benchmark seems off: Cross-check against your analytics. If Cowork says 2,000 words but top competitors are 5,000+, investigate before giving writers the lower target.
- Internal linking recommendations don't align with your site architecture: Cowork makes its best guess, but you know your site. Adjust the linking recommendations to match your silo structure.
These are exceptions. In most cases (70-80% of briefs), generated output is immediately usable with minimal tweaks.
Connecting Content Briefs to Your Broader Workflow
The content brief is just one piece of your content operations. For a complete view of how Cowork integrates into SEO agency operations at scale, see How SEO Agencies Use Claude Cowork to Scale Content Operations. For guidance on other SEO workflows (on-page optimization, technical audits, link prospecting), see 8 Claude Cowork Workflows for SEO Teams That Actually Move Rankings.
Frequently Asked Questions
What if I'm writing about a brand-new topic with no ranking competitors?
Use the core Template 1 but adapt the prompt: instead of analyzing competitor structure, tell Cowork your target audience and the specific problem you're solving. Cowork can generate an outline based on best practices for that topic/audience, even without competitor reference. You may want to do additional research to fill gaps that competitor analysis would normally reveal.
Can Cowork generate briefs for multiple content types (blog posts, whitepapers, product guides)?
Yes. Adapt the prompt to specify the content type. A whitepaper brief will look different from a blog post brief (more sections, deeper research, different CTA structure). Let Cowork know the content type and target outcome in the prompt.
Should I share Cowork's generated brief with writers as-is, or should I review it first?
Always review before handing off. Spending 15 minutes reviewing/adjusting a brief prevents writers from spending 2 hours on a draft that misses the mark. The review should focus on: intent classification, structure, internal linking logic, and word count targets. Once you've reviewed 5-10 generated briefs, you'll develop a sense of what usually needs adjustment in your industry/domain.
How often should I regenerate briefs for evergreen content I'm updating?
Regenerate briefs when you're doing a major refresh (6+ months since last update) or when your keyword target has shifted. For minor updates, the old brief is usually sufficient. Use Cowork's brief generation quarterly to check if search intent has changed for your highest-value keywords.
Can I use Cowork briefs to brief out work to freelance writers or agencies?
Absolutely. In fact, detailed briefs improve freelancer output quality significantly. Share the complete brief (but not your internal competitive analysis comments). Detailed briefs reduce revision cycles by 30-40% because writers understand the target structure and content gaps upfront.
Ready to Automate Content Brief Generation?
Content briefs are the foundation of quality SEO writing. Automating their generation frees your SEO team to focus on strategy and distribution instead of spending days synthesizing competitor data.
Related Articles: 8 Claude Cowork Workflows • On-Page Optimisation • Connecting to SEMrush, Ahrefs & GA4 • Scaling with Cowork at Agencies