Step 1: Anchor the brief to one query
Start from a single, real buyer question — "how do I do X?" or "best tool for Y?" Everything in the brief serves that query. If you can't name the query, the brief isn't ready.
Pull the query from search-console data, support tickets, or a keyword the buyer uses. Intent first, always.
Step 2: Build the outline from sub-questions
Map the H2/H3 structure to the query's sub-questions, not to your product sections. A clear outline helps both readers and an engine attribute each point. Aim for one H2 per sub-question.
A tool that proposes the outline from the query (like BriefKit) keeps this consistent across many briefs.
Step 3: Add 5–8 related questions
Include the people-also-ask set so the page covers the cluster, not just the keyword. A page that answers the siblings ("how," "vs," "best") looks complete to an engine.
Don't pad — only include questions a real buyer asks.
Step 4: List 3–5 citable sources
Name authoritative sources the draft can cite. These let an engine attribute claims and trust the page. Critical: verify each source is real, current, and says what you claim before publishing.
Suggested sources are proposals. The verification is yours.
Step 5: Write the answer hook
Draft one direct, self-contained sentence that resolves the query — the line an engine is most likely to quote. Put it at the top. If it reads fine out of context, it's a hook.
Then hand the brief to a writer. The scaffold is done; the prose is human.
Authoritative references
- Google Search Central: https://developers.google.com/search/docs
- OpenAI: https://openai.com/blog