{
  "$schema": "https://promptfoo.tech/schemas/workflow-template.json",
  "name": "Perplexity + Claude: Research-to-Brief SEO Workflow",
  "slug": "perplexity-seo-brief-workflow",
  "platform": "Perplexity",
  "category": "seo",
  "difficulty": "Beginner",
  "tags": [
    "perplexity",
    "claude",
    "seo",
    "content",
    "research"
  ],
  "summary": "Use Perplexity for live SERP research and Claude to synthesize a battle-tested content brief your writers actually want to use.",
  "overview": "SEO briefs from templates are generic; briefs from live research are useful. This two-step workflow uses Perplexity to pull current SERP intent, competitor angles, and PAA questions, then Claude to synthesize a brief that includes the H2s, angles to differentiate on, and the questions you must answer.",
  "variables": {
    "ANTHROPIC_API_KEY": "sk-ant-..."
  },
  "steps": [
    {
      "order": 1,
      "name": "Standardize your Perplexity queries",
      "description": "One for SERP intent, one for PAA/related. Save them as templates in a Notion page so team members don't reinvent."
    },
    {
      "order": 2,
      "name": "Set up a Claude Project",
      "description": "Attach your brief template as a project file. Every brief request now inherits the format."
    },
    {
      "order": 3,
      "name": "Prompt for angles, not summaries",
      "description": "'What are the 3 angles competitors are NOT taking on this topic?' is worth more than 'summarize the top 10 results'."
    },
    {
      "order": 4,
      "name": "Demand H2s tied to intent",
      "description": "Every H2 should map to an intent bucket (informational, navigational, commercial). This makes editing painless."
    },
    {
      "order": 5,
      "name": "Version briefs in git or Notion",
      "description": "Track which brief produced which article. Over 3 months you'll spot which brief patterns rank."
    }
  ],
  "howItWorks": [
    "Perplexity Pro query: SERP analysis for the target keyword with citations.",
    "Second Perplexity query: PAA and related searches with source URLs.",
    "You paste both outputs into a Claude Project with the brief template as its system prompt.",
    "Claude returns a brief: target intent, must-cover subtopics, differentiation angles, suggested H2s, target word count.",
    "You paste the brief into your CMS or Notion as the writer's starting point."
  ],
  "benefits": [
    "Writers open a brief with citations, not vibes.",
    "Differentiation angles surface before writing, not in editing.",
    "Repeatable — the same two prompts work for every keyword."
  ],
  "useCases": [
    "In-house SEO teams briefing freelancers.",
    "Agencies producing 20+ briefs a month.",
    "Founders self-writing cornerstone content who need a rigor forcing function."
  ],
  "example": "Brief snippet: 'Differentiator #2 — no competitor covers the failure modes. Include a section titled \"When this workflow breaks\" with 3 real examples.'",
  "faqs": [
    {
      "q": "Why not just use Perplexity for the brief?",
      "a": "Perplexity is great at research, weaker at long-form structure. Claude is the reverse. Play to strengths."
    },
    {
      "q": "Can I automate this?",
      "a": "You can — pipe Perplexity API → Claude API → Notion. But manual review of research is where you catch bad sources."
    },
    {
      "q": "Does this replace human editors?",
      "a": "No. It replaces the blank page. Editors still make the piece great."
    }
  ],
  "source": "https://promptfoo.tech/workflows/perplexity-seo-brief-workflow",
  "updated": "2026-06-08",
  "license": "CC-BY-4.0"
}