Claude AI SEO Content Brief Prompt Template: An XML-Structured Approach That Actually Works

Why Claude Brief Prompts Usually Underdeliver

Most practitioners who try Claude for SEO content briefs run into the same problem: they paste a prompt, get back a tidy-looking outline, and assume the model did the work. Then the writer follows that outline and produces something that reads like a Wikipedia summary of the topic — correct, generic, and unlikely to outrank anything.

The controlling variable is not Claude's capability. It is the prompt structure. Claude has no live search access, so without manually injected SERP data, it defaults to producing what an average-of-internet synthesis would look like for a given keyword. The outline it generates reflects what has been written about a topic historically, not what is currently ranking, what competitors are missing, or what angle would actually differentiate the piece.

The fix is structural. A Claude brief prompt that uses XML tag formatting, injects real SERP context, and covers all six required brief components produces a qualitatively different output — one that a writer can actually use as a production brief rather than a starting point for a second round of prompting.

What Makes Claude Specifically Well-Suited for Structured SEO Briefs

Claude has three structural properties that make it a strong fit for SEO brief generation — but only when the prompt is built to activate them.

• Native XML tag parsing. Anthropic's own prompting documentation confirms that XML tags help Claude parse complex prompts unambiguously by separating instructions, context, and variable inputs into distinct labeled blocks. When a prompt mixes instructions, background information, pasted SERP data, and formatting rules in a single block of text, Claude can lose track of which part is which. XML tags eliminate that ambiguity.
• 200K-token context window. Claude's extended context window means you can inject SERP summaries, competitor article outlines, internal brand style guides, and existing content samples into a single session without hitting a truncation wall. This is a structural advantage for brief quality: the more real-world context the model has, the less it has to fill gaps from training data.
• Instruction-following discipline. Claude prioritizes provided source material over its internal training data when summarizing or structuring injected documents. This reduces hallucination in brief generation — when you paste in competitor content or SERP data, Claude works from that material rather than substituting its own version of what those sources probably said.

The Six Components Every Claude Content Brief Prompt Needs

Claude will not infer missing brief components. If you do not specify search intent, it will guess. If you do not define the audience, it will write for a generic reader. If you do not provide competitor framing, the brief will not identify content gaps. Every component listed below must be explicit in the prompt.

The Copy-Paste XML Template with Annotated Fields

The template below uses the XML tag pattern that Anthropic's prompting documentation recommends for complex, multi-part prompts: role, context, task, data, and format_rules. Each block is labeled so Claude reads the prompt modularly — instructions do not bleed into context, and pasted SERP data does not get treated as part of the task definition.

Before pasting this into Claude, gather your SERP data manually: open the top 5–8 results for your target keyword, note their H2 structure and the angles they take, and paste those summaries into the <data> block. Claude has no live search access — this injection step is not optional.

<role>
You are a senior SEO content strategist. Your task is to produce a structured content brief that a writer can follow to create a page that competes for a specific keyword. Do not write the article. Write the brief only.
</role>

<context>
Brand: [Your brand name]
Target audience: [e.g., "In-house SEO managers with 2+ years of experience, familiar with keyword research and on-page optimization basics. Not developers."]
Brand voice: [e.g., "Direct, practitioner-focused, honest about tool limitations. No hype. No generic AI phrasing."]
Existing content on this topic: [Paste URL or brief summary if applicable, or write "None"]
</context>

<task>
1. Analyze the competitor content and SERP data provided in <data>.
2. Identify the primary search intent for the target keyword.
3. Identify at least two content gaps — angles, subtopics, or questions that the top-ranking pages do not adequately address.
4. Produce a complete content brief containing:
   a. Target keyword and search intent classification
   b. Recommended page title (H1)
   c. Meta description (150–160 characters)
   d. Audience and assumed knowledge level
   e. Recommended H2 and H3 structure with a one-sentence description of each section's purpose
   f. Content gaps to exploit
   g. Word count target
   h. Tone and CTA guidance
   i. Internal linking suggestions (if provided in context)
</task>

<data>
Target keyword: [Paste exact keyword phrase here]

SERP summary (top 5–8 results — paste H2 outlines, article angles, and any notable gaps you observed):
[Paste your manually gathered SERP notes here. Example:
- Result 1: "[Title]" — covers X, Y, Z. Skips [gap].
- Result 2: "[Title]" — covers A, B. Heavy on [angle], light on [angle].
- Result 3: "[Title]" — [notes]
]

Competitor excerpts or outlines (optional but recommended):
[Paste relevant sections from competitor articles here if you want Claude to analyze them directly]

Brand style guide excerpt (optional):
[Paste relevant tone, terminology, or formatting rules here if available]
</data>

<format_rules>
- Output the brief as structured sections with clear labels.
- Use bullet points for the H2/H3 outline, with each heading followed by a one-sentence purpose note.
- Do not write body copy or article prose — brief components only.
- Flag any section where competitor coverage is thin and the content gap opportunity is high.
- Word count target: [e.g., 1,400–1,800 words]
</format_rules>

Adapting the Template for Different Content Types

The base template above handles informational how-to content well by default. For other content types, two or three targeted adjustments to the <task> and <format_rules> blocks are enough to redirect the output.

Model Selection: When to Use Opus vs. Sonnet for Brief Generation

Claude's model tiers differ meaningfully in output quality and cost for this task. The right choice depends on what kind of brief you are generating and how much analytical differentiation it requires.

For most day-to-day SEO brief workflows, Sonnet is the right default. Reserve Opus for briefs where the differentiation angle is genuinely difficult to identify — where the top-ranking pages are high-quality, the keyword is competitive, and a generic brief will produce a generic article that cannot displace what is already there.

Known Failure Modes and Specific Fixes

Each failure mode below has a specific symptom and a specific fix. These are not general warnings — they are the four most common reasons a Claude brief prompt produces unusable output.

• Failure mode: No SERP data injected. Symptom: The brief outline reads like a Wikipedia table of contents — topically complete, structurally generic, no differentiation. Fix: Gather SERP data manually before prompting. Open the top 5–8 results, note their H2 structure and the angles they take, and paste those observations into the <data> block. This is the single most impactful change you can make. Claude has no live search access — without injected data, it cannot know what is currently ranking or what is missing from the SERP.
• Failure mode: Vague audience definition. Symptom: The brief recommends introductory-level explanations for concepts the target reader already knows, or assumes technical knowledge the reader does not have. Fix: Specify role, experience level, and assumed prior knowledge explicitly in the <context> block. 'Marketing professional' is not enough. 'In-house SEO manager with 3+ years of experience, comfortable with keyword research and on-page optimization, not a developer' is specific enough for Claude to calibrate depth and terminology.
• Failure mode: Missing competitor framing. Symptom: The brief does not identify content gaps or differentiation angles — it recommends covering the same topics in the same order as the pages already ranking. Fix: Add at least two competitor summaries to the <data> block, noting what each article covers and what it skips. Even rough notes ('Result 2 covers X and Y but has no section on Z') give Claude enough context to identify structural gaps.
• Failure mode: Prompt too short or free-form. Symptom: Claude produces a brief that is structurally correct but missing one or more required components — no CTA guidance, no word count, no audience note. Fix: Use the full XML template. Free-form prompts ask Claude to infer structure; the XML template tells it exactly what to produce. When a prompt mixes instructions, context, and data in a single block, Claude can lose track of which part is which — XML tags prevent this by forcing modular parsing.

What to Do After the Brief: The Human Review Layer

Claude's output is a structured draft — not a finished brief. The model can organize, synthesize, and identify patterns in the data you provide, but it cannot apply the judgment that comes from knowing your specific audience, your brand's competitive position, or the editorial context of the piece.

Treat the Claude output as roughly 90% complete. The remaining 10% requires human review on these specific tasks:

• Verify the proposed outline reflects genuine information gain. Read the H2/H3 structure Claude recommends and ask: does each section offer something the top-ranking competitors do not? If the outline is structurally differentiated but the section descriptions are vague, sharpen them before handing the brief to a writer.
• Finesse the intro angle. Claude will recommend an intro approach, but the specific hook — the concrete problem, example, or claim that makes a reader continue past the first paragraph — requires editorial judgment. Generic intro formulas ('In today's digital landscape...') are a Claude default when the prompt does not specify an angle. Override this in the brief.
• Check any statistics or claims in the brief for accuracy. If Claude's brief references specific data points or cites trends, verify them against your injected SERP data. Claude may occasionally synthesize a plausible-sounding statistic from training data rather than from the material you provided — especially if the injected data was sparse.
• Adjust tone to match actual brand voice. Even with a detailed tone specification in the <context> block, Claude's tone guidance in the brief may drift toward neutral editorial. Review the tone and CTA section of the brief against examples of your best-performing existing content and adjust as needed.

What Claude Still Cannot Do for This Task

Being direct about Claude's hard limitations for SEO brief generation is more useful than glossing over them. There are three that matter for this workflow:

• No live SERP access. Claude cannot browse the internet or retrieve current search results. Every session starts fresh with no knowledge of what is ranking today, what competitors published last month, or what search volumes look like right now. Manual SERP data injection is required every time — this is a structural constraint, not a configuration issue.
• Not suited for very high-volume repetitive brief generation at speed. The XML template approach works well for deliberate, one-at-a-time brief production. For workflows requiring dozens of briefs per day with automated SERP data ingestion, you would need an API-based pipeline with programmatic data injection — a different setup than the chat interface or basic API use this guide covers.
• Cannot verify whether a proposed angle is genuinely differentiated without supplied data. If you do not inject competitor content, Claude has no basis for identifying gaps. It will generate an outline that looks differentiated but is actually a reasonable guess at what the topic requires — not a gap analysis.