Turn fanout questions into a usable content brief
A content brief states the decision a page should support and the evidence still needed. Take reviewed questions from your fanout, assign them to a reader task and give the editor a concrete outline rather than an unreviewed keyword list.
Use it for an existing page or a justified new URL. Edit the Markdown files in a text editor or adapt them to your editorial workflow. The example remains a fictional research assignment.
Start with a clearly labelled query listUse an existing export or run a short topic. Keep native observations and modelled ideas separate.Open the toolStart with the reader and their decision
Write the assignment in one sentence: the owner of a five-person SEO team should be able to choose a suitable software plan using verified features, permissions and total seat cost. That sentence defines the page more clearly than ten similar keywords.
In the completed example, selection and cost stay in one fictional buying guide. CSV-import questions lead to a separate operation. The brief specifies that link without copying an entire import tutorial into the buying guide. The SQL question is excluded.
The seven-question mapping comes from the clustering example.
Market and language deliberately stay open in the example until the real price and demand checks are planned. Replace those fields for your assignment. Similar English and German wording does not establish equal demand or identical price conditions.
Download the blank template and worked example. Their structure covers the reader decision, question/evidence register, outline, exclusions and acceptance. This is an assignment, not a finished researched article or proof that a product has been tested.
Connect every planned section to its evidence
For each question, the evidence register records its origin, required proof and remaining limit. The selection cluster requires actual feature and permission checks. The cost cluster requires current official prices, included users and conditions for additional seats.
Those checks have not been performed in the teaching example, so it contains no prices, tested winner or customer results. The assignment is still concrete: the reviewer knows what must be obtained. An empty metric is more honest and useful than a plausible number without a source.
The outline follows that decision: selection task and open information first, supported criteria next, usable plan cost after that, and the separate import link last. A best-tools title needs actual criteria and tests before publication.
Do not demand a word count for each fanout question. Some questions can be answered together in a table; others need an independent tutorial. Remove sections that contribute nothing to the reader's decision. Keep important limits visible in the article rather than only in an internal note.
What belongs in the assignment
From the fictional example; checks have not yet been performed.
| Section | Required work | Before publication |
|---|---|---|
| Feature comparison | Test permissions and workflow | Record check date and outcome |
| Five-user cost | Check price and seat conditions | Name market, currency and open conditions |
| CSV import | Link the separate task | The destination must exist and work |
Hand over the brief with clear acceptance criteria
Name a person responsible for missing evidence and another for editorial review. Acceptance means the reader can make the decision using traceable information. A checklist that only ticks keyword included does not test that task.
Record the demand check with its range and filters, or label it not checked. State which existing URL will change and which published internal destinations support the next step. A draft may contain open questions; the finished page must not turn them into facts.
For the demand check, use the fanout-to-Search-Console mapping.
After publication, add release and recrawl dates plus appropriate query/page cohorts. Until comparable follow-up data exists, impact remains unmeasured. If several pages changed together, a later click increase cannot be attributed to this brief alone.
Sources used
These sources support the functions and limits described here. They do not prove claims beyond that scope.
- Original query-clustering, content-brief and GSC-mapping worksheetsOpen source
Blank worksheets and completed teaching examples. Seven illustrative questions and fictional website paths support the walkthrough only. No real provider output, client result, GSC measurement or keyword volume is published in these files.
- Optimizing for generative AI features on Google SearchOpen source
Normal SEO foundations remain relevant; pages made primarily for fan-out variations are not the accepted content model.