# Perplexity + Claude: Research-to-Brief SEO Workflow

> Use Perplexity for live SERP research and Claude to synthesize a battle-tested content brief your writers actually want to use.

**Platform:** Perplexity  
**Category:** seo  
**Difficulty:** Beginner  
**Tags:** perplexity, claude, seo, content, research  
**Updated:** 2026-06-08  
**Source:** https://promptfoo.tech/workflows/perplexity-seo-brief-workflow

## 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.

## How it works
1. Perplexity Pro query: SERP analysis for the target keyword with citations.
2. Second Perplexity query: PAA and related searches with source URLs.
3. You paste both outputs into a Claude Project with the brief template as its system prompt.
4. Claude returns a brief: target intent, must-cover subtopics, differentiation angles, suggested H2s, target word count.
5. 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.

## Use cases
- In-house SEO teams briefing freelancers.
- Agencies producing 20+ briefs a month.
- Founders self-writing cornerstone content who need a rigor forcing function.

## Step-by-step
### Step 1: Standardize your Perplexity queries
One for SERP intent, one for PAA/related. Save them as templates in a Notion page so team members don't reinvent.

### Step 2: Set up a Claude Project
Attach your brief template as a project file. Every brief request now inherits the format.

### Step 3: Prompt for angles, not summaries
'What are the 3 angles competitors are NOT taking on this topic?' is worth more than 'summarize the top 10 results'.

### Step 4: Demand H2s tied to intent
Every H2 should map to an intent bucket (informational, navigational, commercial). This makes editing painless.

### Step 5: Version briefs in git or Notion
Track which brief produced which article. Over 3 months you'll spot which brief patterns rank.

## Example
```
Brief snippet: 'Differentiator #2 — no competitor covers the failure modes. Include a section titled "When this workflow breaks" with 3 real examples.'
```

## FAQs
**Why not just use Perplexity for the brief?**

Perplexity is great at research, weaker at long-form structure. Claude is the reverse. Play to strengths.

**Can I automate this?**

You can — pipe Perplexity API → Claude API → Notion. But manual review of research is where you catch bad sources.

**Does this replace human editors?**

No. It replaces the blank page. Editors still make the piece great.

---
Licensed under CC-BY-4.0. Attribution: PromptFoo.tech