AI SEO Content Brief Generator With n8n And Claude

Content briefs are one of the most time-consuming deliverables in SEO — and also one of the most inconsistent. When created manually, their quality depends entirely on how much time the strategist has. A rushed brief gets one paragraph of vague direction. A thorough brief takes 45–60 minutes per keyword: pulling SERP data, reading competitor articles, identifying topic gaps, and structuring an outline. For teams managing 10+ keywords per week, that’s an entire day of work before a word is written.

This workflow compresses that 45-minute manual process into about 90 seconds per keyword, with quality that rivals a thorough human-written brief. The key is combining real Ahrefs SERP data with Claude 3.5 Sonnet’s analytical capability. Unlike prompt-only approaches that ask the AI to imagine what ranks, this workflow feeds Claude actual ranking URLs, domain ratings, traffic estimates, and word counts — then asks it to draw conclusions from evidence, not assumption.

The Intermediate difficulty rating reflects the Ahrefs API setup and the custom data transformation required in the Code node, not the conceptual complexity. If your team already uses Ahrefs and has basic n8n experience, plan for 35–45 minutes of setup. The $0.04-per-brief cost comes from Claude 3.5 Sonnet API usage (~1,500 input tokens + ~800 output tokens at Sonnet pricing).

Prerequisites

1. An n8n instance (Cloud or self-hosted; n8n Cloud Starter plan recommended for reliable scheduling)
2. An Anthropic API key with Claude 3.5 Sonnet access (usage-based; ~$2–4/month for 50 briefs/week)
3. An Ahrefs account with API access (available on Ahrefs Advanced or Enterprise plans; the SERP Overview endpoint is required)
4. A Notion database for keywords with properties: Keyword (text), Monthly Volume (number), KD Score (number), Brief Status (select: “Needs Brief” / “Brief Ready”), Brief Page (relation or URL)
5. A Slack workspace with a #content-team channel (or similar) and an incoming webhook or Slack bot token
6. Basic familiarity with n8n’s Code node (JavaScript) — needed to reshape the Ahrefs API response into Claude’s prompt format

Setup Guide

1. Import the blueprint — Download and import the workflow JSON into n8n via the Import from File option.
2. Configure Notion credentials — Authenticate the Notion node with your integration token. Select your keywords database. The filter should read: Brief Status = Needs Brief.
3. Set up Ahrefs API — In the HTTP Request node labeled “Fetch SERP Data”, add your Ahrefs API token as a Header Auth credential (Authorization: Bearer YOUR_TOKEN). The endpoint used is https://api.ahrefs.com/v3/serp-overview with query parameters keyword, country (default: us), and limit=10.
4. Add Anthropic credentials — In the HTTP Request node labeled “Claude Brief Generator”, add your Anthropic API key as a Header Auth credential (x-api-key). The model is set to claude-3-5-sonnet-20241022.
5. Review the Code node — The Code node transforms the Ahrefs response array into the [SERP_DATA] string injected into the prompt. Inspect the default transformation logic and adjust if Ahrefs changes its response schema.
6. Connect Slack — Add your Slack credential (Bot Token preferred over Incoming Webhook for richer message formatting). Update the channel name in the Slack node from #content-team to your actual channel.
7. Update Notion write node — Configure the “Create Brief Page” Notion node to write to the same or a linked database. Map the content field from the Claude response to the Notion page body using the Text block type.
8. Set the trigger — Default is a manual trigger. Change to a weekly Schedule Trigger (e.g., Monday 8 AM) if you want fully automatic processing of accumulated keywords.
9. Test with a single keyword — Add one row to Notion with a real keyword and status “Needs Brief”. Run manually and inspect each node’s output before enabling the schedule.

Who This Is NOT For

• Teams without Ahrefs API access — the workflow degrades significantly without real SERP data; a DataForSEO or SemRush API adaptation is possible but requires custom node configuration not included in the blueprint
• Local SEO teams targeting city-specific or hyper-local keywords where Ahrefs SERP data may not reflect true local pack results
• Teams producing content at fewer than 5 briefs per month — at that volume, manual briefing is faster than the setup investment
• E-commerce teams needing product page briefs — the prompt and outline structure is optimized for editorial/blog content; product SEO requires different signals (schema, reviews, pricing data)