A practical guide to SEO content briefs that writers actually use

A bad content brief is a short email that says "write about X." A mediocre brief is a twelve-page document the writer skims and forgets. A good brief sits in between: it gives the writer exactly the context they need to make good decisions, and nothing they'll ignore.

Why most briefs fail

The most common failure is dumping keyword research into the brief and calling it strategy. A list of keywords is not an article; it tells the writer what to mention, not what to say. The writer either force-fits the keywords and produces something robotic, or ignores them and produces something the SEO team rejects.

The second failure is vagueness about the reader. "Anyone interested in X" is not an audience. A writer who doesn't know who they're writing for will write for no one.

The minimum viable brief

A brief that gets used has seven parts. Anything beyond these is optional, and usually noise.

1. A working title. It doesn't have to survive editing, but it sets the angle and the promise.
2. The target audience, stated as a specific person. "First-time managers running a small team" beats "managers."
3. Search intent in one line. What is the reader actually trying to accomplish when they search for this?
4. A structure. The H2 sections, in order. This is where the thinking happens — the writer should not have to invent it.
5. Questions to answer. The specific things the article must resolve, beyond the H2s.
6. The primary keyword and where it belongs: title, first 100 words, and one H2. No more instruction than that.
7. Writer notes. Length, tone, what to avoid, and where to link internally.

Match the structure to the intent

The format should follow the search intent, not the other way around. A keyword with informational intent gets a guide or a how-to. A keyword with commercial intent — "best X for Y" — gets a comparison or a list with clear recommendations. Writing a how-to for a commercial keyword produces content that ranks nowhere because it answers a question no one asked.

Say what not to do

The most underrated line in a brief is a constraint. "Don't write a history of the topic." "Don't pad to hit a word count." "Don't invent statistics." These save more revision time than any amount of positive instruction, because they remove the writer's guesswork about your unspoken rules.

Review the brief like you'll review the draft

Before you send a brief, read it once and ask: if I were the writer, what would I still have to ask? Every unanswered question is a future revision or a future Slack message. Close those gaps now, and the draft comes back closer to final the first time.