What is a content brief? Definition and what belongs in one

Most briefs in circulation are a keyword and a word count, and then everyone is surprised when the page does nothing. That is the whole problem in one sentence. A brief is not a work order; it is the set of decisions that determine whether the page can win, made by whoever has done the research and handed to whoever is doing the writing.

What a brief is for

Semrush defines one simply — "a document that gives writers instructions and guidelines for creating written content" — and Backlinko calls it "a blueprint for high-quality, engaging, and SEO-friendly content". Both are true and both undersell the mechanism.

The real function is to move the hard thinking upstream. Deciding which query a page targets, what the pages ranking for it already say, and what this page will add is research work, not writing work. Do it in the brief and the writer spends their time writing. Skip it and the writer either does the research badly under time pressure, or produces the average of the first three results — the most common shape of a page that never ranks.

Ahrefs puts the writer's side of it well: a brief should help the writer understand why they are writing something, because then "they'll have a better chance at hitting your goal".

What belongs in one

These are the fields that change the output. Anything not on this list should have to justify its place.

Field	Why it is there
The target query and its search intent	Decides everything downstream — format, depth, what counts as an answer
Who the reader is and what they already know	Sets the reading level and how much can be assumed
What the ranking pages already say	Stops the writer rediscovering it, badly, at 4pm
The angle — what this page adds	The one field that decides whether the page can outrank anything
Working title	Fixes the promise the page has to keep
Outline as intent-driven sections	Gives structure without dictating sentences
Internal links to make	Where this page sits in the site, decided by someone who can see the whole site
Sources to cite, claims to support	Prevents the confident, unsourced assertion
The next step for the reader	What the page is for, commercially
Constraints — persona, reading level, length range with a reason	The voice and the shape, stated once
Done criteria	What "finished" means, so review is not a matter of taste

Two of those carry most of the weight. The angle is the field people leave blank; without it the writer's only available strategy is to cover what everyone else covered. And the outline is the field people get wrong — Backlinko distinguishes an SEO-led outline, which specifies structure, from a writer-led one, which lists topics and leaves the shape to the writer. The failure in both cases is the same: pasting the competitor's H2s into the brief and calling it a structure.

The fields that are theatre

Word count as a target. Useful as a range with a reason attached — "the ranking pages run 1,200 to 1,800, this one needs to cover four subtopics" — and actively harmful as a number to hit, because a writer paid by a number writes to that number. Backlinko warns that SEO tools tend to overcount competitor length by including navigation and sidebars, so the figure people chase is often inflated to begin with.

Keyword density and term lists. A list of phrases to include produces text that reads like it was written to include a list of phrases. There is no density target that Google publishes or rewards.

Instructions like "add E-E-A-T" or "make it engaging". These are outcomes, not inputs. The brief's job is to name the thing that would make the page authoritative — the practitioner quote, the data set, the author with the credential — not to ask for authority in the abstract.

Everything. Ahrefs makes the sharpest point in the topic: "Spend too long writing suggested headers, recommending examples to include, and handpicking competitor articles to read, and you may as well have written the article yourself." Semrush lands in the same place, warning against briefs that are "too granular or rigid". A brief that removes every decision removes the reason to hire a writer.

Content brief, creative brief, SEO brief

A creative brief governs a campaign or an asset: the big idea, the tone, the audience, the deliverables. Semrush draws the line at the output — content briefs guide written deliverables, creative briefs guide visual ones. It is what an agency and a client agree before anyone designs anything.

An SEO brief is a content brief with the results-page research already done: the query, the intent, the competing URLs, the subtopics the ranking pages cover, the internal links. The two words usually describe the same artefact at different levels of completeness, and if the content has to rank, the SEO half is not optional.

How Structura handles this

Structura has no brief editor. There is no form to fill in, no template to send a freelancer, and no place to type an angle for post number seventeen — which is a real limitation if your team likes briefing by hand, and worth knowing before you buy.

What it does instead is assemble the brief internally, per post, from things you set once. The keyword comes from a bank grounded in real search volume for your topic space, with a ledger that stops the same topic being written twice. The competitive research is done live: it reads the pages currently ranking for that keyword, including their outlines, at the moment it drafts. The voice, expertise and reading level come from the author persona you configure. The angle and the internal links come from your campaign's positioning and objective plus the archive you have already published. The brief exists; you simply never see it as a document.

The practical consequence: your input moves from per-post to per-campaign. You set the positioning, the objective, the personas, and you approve the keywords — then you review output rather than writing specifications. Teams who want to steer individual pieces should expect to do it at the approval gate, editing the draft, rather than upstream in a brief. The features page walks through what each stage of that pipeline does.

FAQ