A semantic content brief is a one-page specification that tells a writer, human or AI, exactly what a page must cover: its one search intent, the entity and attributes, the questions in the order readers ask them, the facts to state, and where the page links. It sits between the topical map and the draft, and it is the single biggest lever on content quality.
Why a semantic brief beats a keyword brief
A traditional brief says: target keyword, word count, a few secondary keywords, competitors to beat. It tells the writer which words to use, not what the page must know. The result is pages that match each other and say nothing new.
A semantic brief starts from meaning. It defines the job the page does, the entity it is about, the attributes that make coverage complete, and the questions a reader brings, in order. Keywords still appear, but as phrasing guidance, not the plan.
What goes in a semantic content brief
| Field | What it contains |
|---|---|
| Central search intent | One sentence: the job this page does for the reader |
| Map position | Section (core or outer), parent page, sibling pages |
| Main entity | Its full canonical name and a one-line definition |
| Attributes to cover | Root attributes (must have), rare and unique attributes (differentiators) |
| Question sequence | The questions in the order a reader asks them; these become headings |
| Facts and values | Specific numbers, dates and claims to include, each with a source |
| Related entities | Entities to mention in context so the page sits in the right neighbourhood |
| Original element | What this page has that others don’t: data, example, screenshot, template, opinion |
| Internal links | Link up to the parent, sideways to 2 or 3 siblings, with suggested anchors |
| Format | Tables, steps, comparison blocks, FAQ; approximate length set by what the questions need |
| Out of scope | What this page must not cover because another page owns it |
The last field matters more than it looks. It is how briefs prevent keyword cannibalization before it starts.
A worked example
Here is a trimmed brief for a page on a coffee site:
- Central search intent: help a home barista fix sour or bitter espresso.
- Map position: outer section; parent “How to dial in espresso”; siblings “Grind size guide”, “Espresso ratio explained”.
- Main entity: espresso extraction.
- Root attributes: grind size, dose, yield, shot time, water temperature.
- Rare attributes: bean roast date, puck preparation, channeling.
- Question sequence: Why is my espresso sour? Why is it bitter? How do I tell under- from over-extraction? What should I change first? What if changing grind doesn’t help?
- Facts: typical starting ratio and shot time ranges, each sourced.
- Original element: a one-variable-at-a-time troubleshooting table from our own testing.
- Links: up to “How to dial in espresso”; across to “Grind size guide”.
- Out of scope: machine reviews, milk steaming.
Notice that the question sequence already reads like the page’s headings. That is deliberate: headings ordered the way readers ask make the page easy to follow and easy for AI systems to quote one answer at a time.
How to build a brief, step by step
- Start from the topical map node. If the page isn’t in the map, decide whether it should be before writing anything. See what a topical map is.
- Write the central search intent in one sentence and check no other page owns it.
- List attributes using the entity-attribute-value model.
- Collect questions from People Also Ask, Search Console, forums and AI prompts, then order them like a conversation.
- Map the fan-out: for AI search, list the sub-questions a prompt on this topic splits into; each should be answered somewhere. See query fan-out.
- Gather the facts with sources before drafting starts, so the writer isn’t guessing.
- Decide the original element. If you can’t name one, the page isn’t ready to be written.
- Set the links and the out-of-scope list.
Using briefs with AI writing tools
A good brief is the difference between generic AI output and a usable draft. Give the model the whole brief, plus your own notes for the original element, and ask it to follow the question sequence as headings and state each fact with its source. Then edit as the expert. Our view on where AI helps and where it doesn’t is in does Google penalize AI content?
Brief quality checklist
- Could two different writers produce substantially the same coverage from this brief?
- Does every heading answer a real question?
- Are the facts sourced?
- Is there an original element?
- Is it clear what the page must not cover?
Briefing is step two of the four-step workflow in the semantic SEO checklist (map, brief, produce, link). If you want briefs generated from a full topical map, that is one of the things SemanticOS is built to do.
Frequently asked questions
What is a semantic content brief?
A brief that specifies a page’s single search intent, main entity, attributes to cover, questions in reading order, facts with sources, internal links and what is out of scope, rather than just a list of keywords.
How is a semantic brief different from a keyword brief?
A keyword brief lists words to use. A semantic brief defines what the page must know and in what order, so the content is complete and distinct from other pages.
How long should a content brief be?
Usually one page. Long enough to define intent, attributes, questions, facts and links; short enough that a writer reads all of it.
Can I use a content brief with ChatGPT or other AI tools?
Yes. A detailed brief plus your own notes produces far better AI drafts than a keyword prompt, but the draft still needs fact-checking and expert editing.