SEO Content Brief Template vs. Article Outline Template: What Goes in Each

By ContentBrief.io Editorial Team ·

Teams that keep a brief template and an outline template tend to end up with two documents that slowly turn into the same document. The outline template picks up a “target keyword” line because someone found it handy once. Then a line for the audience. A few months later the brief template has grown its own list of H2s, the writer receives two sets of headings that disagree, and they have to guess which one the editor actually meant.

Each fact should live in one place.

The pages that rank for this comparison (Semrush's guide to content outlines, Zapier's brief template, Ryan Robinson's downloadable doc) agree on the definitions, and they are right: the brief carries strategy, the outline carries structure, and a brief often contains an outline. All three spend most of their length on the brief side or on how to arrange headings. None of them gives the outline template a way to point back at the brief. That missing link is where outline reviews go soft, in our view, and the fix is a single column. Every heading in the outline names the brief field it exists to deliver.

What belongs in the SEO brief template

The brief template holds decisions that have to be made before anyone drafts, by the person who owns the strategy. We cover the reasoning field by field in what makes a good content brief, so this is the short list, in rough order of how much damage each one does when it is blank.

  • The angle. One sentence on what this page will do that the current first page of results does not. If this field is empty, nothing else on the list can save the article.
  • Primary keyword, plus the dominant result format on page one and the date somebody looked.
  • The reader and the search behind it.
  • Questions the page must answer, written out as the reader would type them.
  • Must-includes and must-avoids, with links. The approved customer quote. The competitor nobody names.
  • Competitor URLs studied, dated.
  • Internal links the page should carry, and a target length given as a range rather than a single number.
  • Success criteria, which most templates skip.

Notice what is missing. Headings. If a section is non-negotiable, like the pricing table on a comparison page, it goes under must-includes as a requirement. The editor states what the page has to contain and leaves the heading text to whoever builds the structure.

What belongs in the outline template

Much less. The outline template is the writer's return document, sent back before drafting, and our case for letting the writer draft it is in content brief vs. outline. At the top it has a working title and the angle restated in the writer's own words. Then one block per section: the draft heading, a line or two on what that section has to establish, a rough length, and a cell labelled Serves.

No keyword field, no audience field. Those already exist in the brief, and copying them into the outline is exactly how the two documents start drifting apart. The restated angle is the one deliberate duplicate, because the restatement is a test: if the writer's version of the angle reads like a different article, you have found the problem before anyone wrote 1,500 words of it.

The Serves column

Each section in the outline has to name what it delivers from the brief, and only a few values are allowed. “Angle” for the sections that carry the page's argument. “Must-include: pricing table.” “Question: how long should a brief be?” copied word for word from the brief's question list. And “Setup,” for an opening or a definition the reader needs before the rest makes sense, which we cap at two sections per outline because setup has a way of multiplying.

Reviewing then becomes a check that runs in both directions. Any section with an empty Serves cell gets cut, or the writer argues for it in a comment (sometimes they win, and that tells you the brief was missing something). Any brief field that no section serves is a gap, and you can see it without reading a single talking point. A missing must-include shows up as a row nobody wrote, rather than as an editor's vague sense that something is off.

This page was outlined the same way. The introduction is marked Setup, and the one-sentence section further down serves a question from our own brief that none of the three ranking pages asked: what changes when one person does both jobs?

The review step itself, who signs off and when, lives in the brief approval workflow. The Serves column just makes the outline checkpoint in that workflow take five minutes instead of a read-through and a feeling.

Rules for keeping the two templates apart

A field that appears in both templates gets deleted from the outline template. H2 text that has crept into the brief template turns back into must-includes. And when a writer keeps adding the same section to every outline and marking it Setup, that section probably belongs in the brief as a standing requirement (or in your style guide), so stop making each writer reinvent it.

Version the templates together. When someone adds a field to the brief (say, a line for the product screenshot the page needs), the list of allowed Serves values changes with it, and an outline template that still references last quarter's brief fields will quietly stop matching anything.

When one template is enough

If the person who writes the brief also writes the article, drop the outline template and add a Serves column to the outline field inside the brief.

Where a generator fits

We build a brief generator, so here is how ours fits these two templates, and where it stops. Run a keyword through ContentBrief.io and the brief comes back with an outline of five to eight H2s, each with talking points, plus a separate list of six to ten questions readers want answered, an analysis of each competing page it read, internal linking suggestions, and a target word count set about ten percent above the competitors' average.

That output does not fill a Serves column. Its question list is the closest thing to one, and mapping each generated question to a generated section is a decent first pass: the questions no section answers are your gaps, and the sections no question needs are your candidates for cutting. The angle is not generated, and it should not be. Write it yourself, put it at the top of the brief, and let the writer restate it on the outline. If you are building the brief template from scratch, start from our content brief template and strip out any headings it tempts you to keep.