ع
Learn Tracks Reference Guides Saved
playbook

Turn a topic into a brief a writer can actually execute

Hand Claude a target topic and your angle, and get back a search- and answer-engine-ready brief — intent, the real questions readers ask, an outline, the entities to cover, FAQs, metadata, and internal links — so the writer executes a plan instead of guessing.

medium ~30 min per brief
when to reach for this

Writers guess at what a page should cover, and the result ranks for nothing and answers no one. A content brief fixes that: you give Claude a target topic plus your context, and it returns a brief built for both search engines and the answer-engine era — the intent, the questions real readers ask, an outline, the entities a credible piece must cover, an FAQ block, the metadata, and the internal links. The writer executes a plan instead of improvising, and the page actually ranks and gets cited. Run it from the Claude Desktop chat — no terminal involved.

gather this first
  • The target topic or query, and the one job the page should do — rank, capture a lead, educate, or get cited by AI answers.
  • Your angle: the point of view or product truth that makes your page worth more than a generic article.
  • A few of your existing pages to link to, plus 2–3 competing pages already ranking for the topic (paste their text — Claude can't browse them live).
the workflow

  1. Pin the intent and the reader's real questions

    Open the folder with your context in Claude Desktop and ask in the chat. Start with intent, not an outline — what the searcher actually wants decides everything else about the page.

    you ask
    For the topic "[your topic/query]", what's the search intent (informational, commercial, transactional), who's asking, and the 8–10 actual questions they want answered? Group the questions logically.

    what you get back The intent, the audience, and a grouped question map — the spine of the whole brief.

    Answer-engine note: these questions become your H2s and FAQ block, which is exactly what AI answers and featured snippets quote. Getting them right is half the work.

  2. Map the must-cover entities and the competitors' gaps

    A page ranks when it's comprehensive and credible. Map what a complete piece must cover, then find where the ranking competitors are thin — that's your opening.

    you ask
    List the entities, subtopics, and terms a comprehensive, credible piece on [topic] must cover. Then, from these competing pages [paste their text], mark which of those each competitor covers well and where they're thin or missing.

    what you get back A coverage checklist plus a gap analysis — the topics you must include and the specific weaknesses you can beat.

  3. Draft the outline with your angle built in

    Now structure it — answering the question map in a logical order, weaving in your angle, and front-loading the answer so both readers and answer engines get the payoff fast.

    you ask
    Build an H2/H3 outline that answers the question map in a sensible order, works in our angle [your POV/product truth], and front-loads the direct answer near the top. Add a one-line intent for each section so the writer knows its job.

    what you get back A structured outline with per-section intents — a plan a writer can fill without guessing what each part is for.

  4. Add the SEO and AEO furniture

    The metadata and linking are what turn a good draft into a found one. Generate them from the same question map so everything stays coherent.

    you ask
    Draft the title tag (≤60 chars), the meta description (≤155 chars), an FAQ block built from the question map (for FAQ schema), 5–8 internal links from [our pages] with anchor text, and the primary plus secondary keywords.

    what you get back Title and meta, an FAQ block ready for schema, an internal-linking plan, and the keyword set — the furniture that makes the page discoverable.

  5. Assemble the brief

    Pull it into one hand-off document so the writer has a single source, not a thread to scroll.

    you ask
    Assemble everything into one brief: target query, intent, audience, the outline with section intents, the entity checklist, the FAQ block, title/meta, internal links, and a one-line "what would make this the single best result for this query."

    what you get back A complete, paste-ready content brief — the plan a writer executes.

    The writer still writes. The brief just makes sure they write the right thing — the difference between a page that ranks and one that disappears.

make it your own
  • Refresh an old page: paste an existing piece that's slipping and ask what to add, cut, and restructure to win the ranking back, instead of briefing a new one.
  • AEO-first: when the goal is getting cited by AI answers, lean the brief toward answer-first prose, a clean FAQ block, and full entity coverage — the things answer engines reward (see the answer-engine-optimization guide).
  • Brief at volume: feed a list of topics and have Claude produce one brief per row, so a quarter of content gets planned in an afternoon.
watch out for
  • A brief is not a draft — and Claude isn't reading the live SERP. It works from what you paste plus its training. Verify the competitive picture and anything time-sensitive against your real search tools.
  • Keywords and search volumes Claude states are estimates, not data. Confirm them in your keyword tool before you commit a quarter to a topic.
  • Don't keyword-stuff. Write for the reader's questions — the entity checklist is about coverage and credibility, not a list of phrases to cram in.
  • An outline is only as good as the angle. A brief that's comprehensive but says nothing only you could say still loses to a page with a real point of view.

you'll end up with A search- and answer-engine-ready content brief — intent, question map, outline with section intents, entity checklist, FAQ block, metadata, and internal links — so a writer executes a clear plan and the page actually ranks and gets cited.

Questions people ask

Does Claude pull live search results or keyword data?
No. Claude works from what you paste in (the competing pages, your existing content) plus its training — it isn't reading the live SERP. Treat keyword and search-volume figures it gives as estimates and confirm them in your real keyword tool, and verify the competitive picture against your own search before you commit.
What is AEO, and why is it baked into this brief?
AEO is answer-engine optimization — getting your content cited by AI answers and featured snippets, not just ranked in blue links. The brief builds for it by mapping the real questions readers ask (which become your H2s and FAQ block) and front-loading direct answers, since that's the structure answer engines quote. There's a dedicated answer-engine-optimization guide if you want to go deeper.
Is the brief the same as a draft?
No — the brief is the plan, the draft is the execution. The writer (human or AI-assisted) still writes the page; the brief just guarantees they cover the right intent, questions, entities, and angle so the finished piece performs. Keeping them separate is what lets one person brief and another write.
Can I use this to fix a page that's losing rankings?
Yes — that's the refresh variation. Paste the existing page and ask Claude what to add, cut, and restructure to win the ranking back, using the same intent-and-entity analysis. Refreshing a slipping page is usually a faster win than briefing a brand-new one.