Content Brief Template Filled In With a Real Example

A content brief filled in with a real example is a one-page plan for a single post in which every field — topic, keyword, intent, audience, outline, links, assets, and review checks — is completed for an actual article, so that a writer can follow it without guessing and a reader can copy the pattern for their own posts.

TL;DR / Key Takeaways

• A brief answers every question a writer would otherwise have to guess at: what, for whom, why, and how.
• The example below fills every field for one real post: "best pour-over coffee maker for small kitchens."
• A good brief is specific: it names the keyword, the intent, the outline, the links, and the assets.
• A brief is not the article. It is the plan the article is checked against.
• Review the finished draft against the brief before publishing, field by field.

What Is a Content Brief?

A content brief is a written plan for one piece of content. It records the decisions that shape the article — topic, keyword, audience, angle, structure, links, and success checks — before any drafting begins. Its purpose is practical: it stops a writer from drifting off-topic, stops an editor from re-litigating decisions mid-draft, and gives a reviewer something concrete to check the finished piece against.

A brief template is the blank version: headings and empty fields. A filled-in brief is the template completed for a real post. The difference matters, because blank templates hide the hard part. Anyone can write "target keyword" in a box. The skill is choosing the keyword, and a filled example shows how that choice is made and what a good answer looks like.

This article does both jobs. It explains each field, then fills every field for one example post, so you can copy the pattern rather than just admire the template.

The Example Post, Chosen First

The example post is: "Best Pour-Over Coffee Maker for Small Kitchens." It was chosen deliberately, because it is narrow enough to be one post and real enough to have genuine questions behind it.

Why this topic works as an example: the audience is clear (people with small kitchens who like pour-over coffee), the buying question is real (which brewer fits a small counter and a small budget), and the post has a natural structure (what to look for, then a comparison, then a recommendation logic, not a single "buy this" command). It is also a topic where a thin post would be obvious: a reader who owns a small kitchen needs dimensions, capacity, and storage notes, not just brand names.

Before filling the brief, three decisions were made and recorded, because every later field depends on them:

• Audience: renters and apartment dwellers with limited counter space who already drink pour-over coffee or want to start.
• Angle: help the reader choose by kitchen constraints first and brand second, so the post stays useful even as models change.
• Goal: the reader finishes knowing which size and style fits their kitchen and what to check before buying, and the blog earns a genuinely helpful page that other coffee posts can link to.

The Filled-In Brief, Field by Field

1. Working title

Best Pour-Over Coffee Maker for Small Kitchens: How to Choose One That Actually Fits

The title contains the target phrase naturally and adds the reader's real worry — fitting it in the kitchen. Titles should describe the page honestly; Google's guidance on title links makes the same point in its own way, advising that titles be descriptive and specific rather than vague or stuffed with keywords. See Google's title link guidance at https://developers.google.com/search/docs/appearance/title-link.

2. Target keyword and secondary phrases

• Primary keyword: best pour-over coffee maker for small kitchens
• Secondary phrases: small pour-over coffee maker, pour-over brewer for apartment kitchen, compact coffee dripper, pour-over coffee maker size and capacity
• Rule recorded in the brief: use the primary keyword in the title, the first paragraph, and one heading, and nowhere else by force. Secondary phrases appear only where they fit naturally.

This is a long-tail keyword: a longer, specific phrase with a clear question behind it. Long-tail phrases suit small blogs because they match a specific reader need instead of competing head-on for a broad term like "coffee maker."

3. Search intent

Intent: commercial investigation. The reader is comparing options before buying, not looking for a definition and not ready to check out this second. That means the post must compare, explain trade-offs, and give decision criteria — not merely describe pour-over coffee, and not merely push one product.

Matching search intent is the brief's most important job. A post that answers the wrong intent fails even if it is well written: a definition post disappoints a buyer, and a sales post disappoints a learner.

4. Audience and what they already know

• Who: adults in apartments or small homes, limited counter and cupboard space, brewing one to two cups at a time.
• What they know: they know what pour-over coffee is, or have at least heard of it. They do not need a history of coffee.
• What they worry about: counter footprint, where to store the brewer, whether it needs special filters, and whether a small brewer still makes good coffee.
• What they do not need: espresso machine comparisons, commercial equipment, or cafe-scale brewing.

5. Angle and promise

Angle: kitchen-first choosing. Size, storage, and capacity come before brand.

Promise to the reader: by the end, you will know what size brewer fits your kitchen, which style suits one or two cups, and the three measurements to check before you buy.

A promise like this is testable: after drafting, you can ask whether the post actually delivers it. If it does not, the draft is unfinished, not the brief.

6. Outline

The outline is the brief's backbone. Each heading is a question the reader asks, in the order they ask it:

• H1: Best Pour-Over Coffee Maker for Small Kitchens: How to Choose One That Actually Fits
• H2: What makes a pour-over maker "small-kitchen friendly"?
• H2: The 3 measurements to check before you buy (footprint, height under cupboards, capacity)
• H2: Pour-over styles compared: dripper, carafe set, and single-cup brewer
• H2: What about filters, grinders, and kettles?
• H2: How to choose: a decision path for one cup, two cups, and guests
• H2: Common mistakes when buying a small pour-over brewer
• H2: FAQ (do small brewers make weaker coffee? can I store it in a cupboard? do I need special filters?)

Note what the outline does not contain: no brand-by-brand mega-list, no history section, and no generic coffee advice. Everything serves the kitchen-first angle.

7. Internal links (planned before drafting)

• Glossary terms that fit this post's content: long-tail keyword, search intent, meta description, and title tag — the site's own reference pages for the SEO concepts this brief demonstrates.
• Existing Rankenza articles to link from the finished post: Pillar Pages and Topic Clusters Explained (where this post would sit in a coffee-niche cluster) and How to Choose Blog Topics Customers Actually Search (how a topic like this one gets chosen).
• Tool page: SEO keyword generator for checking related phrases during planning.

Planning links in the brief, rather than sprinkling them in afterwards, is what makes internal linking deliberate instead of accidental. Each link has a reason a reader would follow it.

8. External sources to cite

• Google Search Central, SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide — for the general principle that content should be written for readers and structured with clear headings.
• Google's title link guidance: https://developers.google.com/search/docs/appearance/title-link — for title-writing practice.
• Manufacturer specification pages for any brewer mentioned, checked at drafting time, for dimensions and capacity figures. No dimension is stated from memory; if a specification cannot be verified on the manufacturer's page, it does not go in the post.

This rule — verify or omit — is what keeps a filled brief honest. A brief that invents specifications hands the writer a lie to publish.

9. Assets needed

• One photo of a pour-over brewer on a small counter, showing scale, with descriptive alt text written in the brief itself: "compact pour-over coffee dripper on a small apartment kitchen counter next to a mug."
• One simple comparison table (style, footprint, capacity, filter type) — the table is specified in the brief so the writer builds it rather than writing around it.
• No stock photo of a cafe, no generic coffee-bean image that tells the reader nothing about size.

10. Meta description

Draft meta description: "Looking for a pour-over coffee maker that fits a small kitchen? Compare sizes, capacities, and styles, and learn the three measurements to check before you buy."

A meta description is the short summary that may appear under a page in search results. Writing it in the brief forces the writer to state the post's value in one sentence — a useful test of whether the post has a clear value at all.

11. Word count and depth target

Target: 2,000–2,500 words. Enough to cover the comparison and the decision path properly, not so long that a buyer must wade through filler. Depth is judged by whether every outline question is answered, not by hitting a number.

12. Call to action

One call to action, at the end: a link to the blog's broader coffee-brewing guide for readers who want technique next, not a hard sales push. The brief records this so the draft does not accumulate three competing calls to action.

13. Review checklist (used after drafting)

• Does the introduction state the kitchen-first promise?
• Does every H2 answer a question from the outline?
• Is every dimension or capacity figure sourced from a manufacturer page?
• Do all planned internal links exist and point to the right pages?
• Does the meta description match the finished post?
• Would a reader with a small kitchen know what to buy — or what to measure — after reading?

Blank Template vs Filled Brief

The table shows why filled examples teach more than blank templates: the blank version tells you what to decide, while the filled version shows what a good decision looks like.

Common Mistakes in Content Briefs

Leaving intent blank. A brief without intent produces a post that answers a question nobody asked. If you cannot state the intent in one phrase — learn, compare, buy, do — the topic is not ready to brief.

Listing keywords instead of choosing one. Ten target keywords is not a strategy; it is indecision. One primary keyword, a few natural secondary phrases, and a rule against forcing them in.

Writing the outline as topics, not questions. "Filters" is a topic. "Do I need special filters?" is a question a reader asks. Outlines built from questions stay reader-shaped; outlines built from topics drift into filler.

Adding links after drafting. Links planned in the brief serve the reader's journey. Links added afterwards tend to serve a quota, and readers can tell the difference.

Skipping the review checklist. A brief without a review step is a plan nobody checks. The checklist is what turns the brief from a document into a standard.

How to Copy This Pattern for Your Own Post

Work through the same fields in the same order: choose the post, name the audience and angle, pick one primary keyword, state the intent in one phrase, write the outline as reader questions, plan links and assets before drafting, write the meta description as a one-sentence value test, and finish with a review checklist. If any field feels hard to fill, that is useful information: the topic probably needs narrowing, or the audience needs defining, before writing starts.

Start from your own site's existing material where you can. A brief for a post inside a cluster should name its pillar — for example, the pillar and cluster guide explains how a post like this one fits a larger set — and a brief for a standalone post should still name the two or three existing posts it will link to, so the new post joins the site instead of floating beside it.

How This Looks on Rankenza

The manual way to brief a post is a blank document and a series of guesses: guess the keyword, guess the intent, guess what the top results cover, and discover halfway through drafting that two sections overlap. Rankenza's way replaces the guessing with research. For each post, it studies what the top ten results for the topic actually cover, filters that material by the intent behind the keyword, and builds the outline from the questions readers actually ask. A human reviews the draft before anything is published, so the brief's decisions — angle, links from your own sitemap, and review checks — stay under your control. Your first article is free, then $3.60 per article or $89 for 50, and the brief pattern above is the same pattern a Rankenza draft follows: one keyword, one intent, one outline of reader questions, and internal links to pages that exist, such as the content brief glossary page and the metadata generator tool for drafting titles and descriptions.

Sources

• Google Search Central, SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide
• Google Search Central, title link guidance: https://developers.google.com/search/docs/appearance/title-link
• Google Search Central documentation hub: https://developers.google.com/search
• Rankenza, Pillar Pages and Topic Clusters Explained: /pillar-pages-and-topic-clusters-explained/
• Rankenza, How to Choose Blog Topics Customers Actually Search: /how-to-choose-blog-topics-customers-actually-search/

FAQ

How long should a content brief be?

Long enough to answer every question a writer would otherwise guess at, and no longer. For a standard blog post, one to two pages is usually right. If the brief is longer than the draft will be, it is over-planned; if it fits in three lines, it is under-planned.

Should the writer or the editor write the brief?

Whoever owns the topic decision should write it, and the writer should be able to challenge it before drafting. A brief written by someone who never meets the writer tends to be ignored; a brief the writer helped shape tends to be followed.

Can one brief cover a series of posts?

No — one brief per post. A series needs a cluster plan above the briefs, with one brief for each post inside it. Sharing a brief across posts is how posts end up duplicating each other.

What if the draft discovers the brief was wrong?

Update the brief, then update the draft. The brief is a plan, not a contract. What matters is that the change is recorded and the review checklist is re-run, so the finished post is still checked against a plan that matches it.