An SEO Content Brief That Actually Ranks
Before you write the post, get a brief that names the real search intent, the questions to answer, the gaps competitors left open, and the structure that earns the ranking.
Ranking isn't about the keyword. It's about answering the question behind it better than anyone else.
A keyword is a clue to what someone actually wants to know. The brief that ranks names that intent, the questions the page must answer, and the gap the current results leave open. Store your topic and audience, and the brief aims the writing before a word is drafted.
Writing to a keyword without understanding the intent is how you produce a post that's technically optimized and answers nothing — and ranks nowhere.
The page that ranks is the one that most completely answers the question the searcher actually had.
The brief guides the writing; it doesn't replace it. A real post with a point still beats a thorough one with nothing to say.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~20 min first time · ~5 min per piece after that |
| Best for | Owner or marketing lead who publishes the company's content — B2B services and SaaS |
What this solves
Well-written posts that never rank because they answer a slightly different question than the one people are searching — and add nothing the top ten results don't already cover.
The problem
You pick a keyword, write a solid post around it, publish, and it never ranks. The post is well-written — that’s not the issue. The issue is that it answers a slightly different question than the one people are actually searching, or it covers the same ground as the ten posts already ranking without adding the thing they all missed. You optimized for the keyword and ignored the intent behind it. Without understanding what the searcher truly wants and what the current results fail to deliver, even good writing lands on page three.
The fix is doing the intent-and-gap thinking before you write, in a brief that aims the post.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe researches intent and competitors and assembles a brief — multi-step work that runs in Cowork
- Claude Projects — Your topics, your audience, and your site's angle stay the same. A Project stores them so every brief is built for your reader and your positioning
How it works
You publish content regularly, and your audience, topics, and site angle are constant. A Project stores them so every brief is built for your reader and your positioning instead of generic SEO advice.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “SEO Briefs” or “Content” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
audience.mdandpositioning.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
audience.md
Who you’re writing for and what they already know — so the brief targets the right depth and the questions that matter to them, not a generic reader.
Example: “Operations leaders evaluating AI tools. They know the buzzwords, distrust hype, and want to know what’s real and what it takes to implement. They search practical, comparison, and ‘how do I actually’ queries.”
positioning.md
Your angle and what you can say that competitors can’t — so the brief points at the gap you’re uniquely able to fill.
Example: “We’re the governance-first, non-technical-team angle. Most content on our topics is written for developers. Our gap is always: what does this mean for a business operator who isn’t going to write code.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before you brief a writer or start drafting:
- The intent is specific. “People want to learn about X” is not intent. “People searching this are comparing two approaches and want to know which fits a non-technical team” is. If the stated intent is vague, the post will be too. Push for the precise want.
- The gap is real and yours to fill. The brief should name something the current results genuinely don’t cover that you’re positioned to. If the “gap” is something everyone already addresses, there’s no reason your post outranks theirs. Ask for the angle only you can take.
- The structure answers the question, not stuffs the keyword. A good structure follows the searcher’s actual questions in order. If it reads like keyword placements with headings, it’ll rank like one. Confirm the H2s map to real questions.
Before you write: does the angle match something true about your product or experience? The gap only matters if you can credibly fill it. Your knowledge of what you can actually claim keeps the brief from promising an angle you can’t deliver.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“Target keyword: [keyword]. Using `audience.md` and `positioning.md`, build a content brief: the real search intent behind this query, the questions the page must answer to satisfy it, what the top-ranking pages cover and the gap they leave open, the angle we can take that they can't, and a recommended structure with H2s. Flag where you're inferring vs. confident.”
“Draft the intro that opens with our angle, not a generic definition.”
A content brief with five labeled parts: the real search intent behind the keyword, the questions the page must answer, what the top-ranking pages cover and the gap they leave, the angle you can take that they can't, and a recommended H2 structure. Inferences are flagged separately from confident claims. If the intent reads as 'people want to learn about X' or the H2s are keyword placements instead of real questions, it missed — push back.
- It doesn't pull live search data. Volume, difficulty, and what currently ranks are estimates unless you paste them in or connect an SEO tool (see Extra Credit).
- It doesn't write the post. The brief aims the writing — the point of view and the proof still have to come from you.
- It can't guarantee a ranking. A sharper brief raises the odds; domain authority, links, and time still do what they do.
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
audience.mdorpositioning.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The intent comes back as “people want to learn about X” — the keyword alone wasn’t enough to work with. Paste the current top results and ask what want they share, or add what you know about the searcher: “assume they’re comparing approaches for a non-technical team.” Vague intent in, vague post out.
- The “gap” is something every ranking page already covers — your
positioning.mdisn’t giving Claude an angle competitors can’t take. Name what only you can claim — your audience, your method, your proof — and ask for the gap only that lets you fill. And if no real gap exists, that’s a finding too: pick a different keyword.
Extra credit
Small additions that pay back the next time you run it.
- SEO tool connector — if you use a keyword or analytics tool, connect it so Claude grounds search volume and competition in real data rather than estimates. See the Connectors guide.
- Cluster, don’t one-off — ask Claude to map a cluster of related briefs around a topic so your posts support each other instead of competing.
- Track what ranks — a live artifact pulling your analytics can show which briefs turned into ranking pages, so the next brief learns from results.
“You don't rank by mentioning the keyword more. You rank by answering the question better.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Intent beats keywords. The recipe’s whole value is forcing the intent-and-gap thinking that ranking actually rewards, before the writing starts. Optimizing for a keyword is easy and doesn’t work; answering the real question completely is harder and does.
Positioning is what makes a gap fillable. Stored positioning lets Claude find the angle you can take that competitors can’t — which is the only durable reason a new page outranks established ones. Without it, you’re writing the eleventh version of the same post.
The brief aims; you still write. A brief makes the writing land on target, but a post still needs a point of view. The recipe handles the research and structure so your effort goes into saying something worth ranking — not into figuring out what to say.
Who this is for
Owner or marketing lead who publishes the company's content in B2B services and SaaS (2–50 employees).
The pain: Solid posts landing on page three because intent and gaps were never examined
The outcome: Every post starts from a brief that names the intent, the gap, and the structure to fill it
Published June 19, 2026 · 0 views