A query fanout report template for findings and next decisions
A fanout report starts with the requested decision and the data actually reviewed. It then gives evidenced findings, separate hypotheses and concrete recommendations. Missing demand or outcome measurements remain explicitly missing.
Use this after a review. The completed teaching file reports a fictional editorial assignment, not client successes or new provider runs.
Use a question you actually need to investigateStart with existing material or the appropriate tool mode. The worksheets require no additional provider run.Open the free toolStart with the decision the report should support
A team rarely needs only a long query list. It needs to decide whether to research a cost section, improve an existing page or exclude a question. State that assignment and recipient first. An editorial report needs different details from a private parser diagnosis.
Record files, versions and timestamps. Preserve the evidence classes: native API observation, modelled idea, editorial question and human search data. A selection is not a complete run. State included and excluded questions, along with sources available only at run scope.
The Markdown template places the finding, evidence class, location, supported claim and limit side by side. Each recommendation then has an owner, target and acceptance evidence. The report remains useful even when the next person cannot open the original dialog.
Download the annotated teaching report too. It reviews seven original questions and records unchecked demand. The file reports retrospectively on the exercise; a content brief is the prospective writing assignment. The documents serve different tasks.
Next, you can create the writing brief.
Separate findings, hypotheses and recommendations in one example
F01 describes the grouping of seven editorial questions. Selection and cost stay with the same fictional buying guide, import is a separate operation and SQL is excluded. The claim concerns the worksheet's grouping. It establishes neither a provider search nor human demand.
F03 records that the GSC example contains no measurements. That missing check is not converted into a zero-demand claim. F04 names the supported general statement from the source audit and distinguishes it from an individual ranking outcome.
Next, you can audit the supporting sources.
H01 suggests that a verified cost section could help a five-person team choose a plan. R01 therefore recommends a bounded research assignment with current seat conditions and a reproducible calculation. The brief should not produce an unchecked winner recommendation.
Do not transfer synthetic arithmetic from the measurement exercise into this report as observed results. The example explicitly states that the fictional website change has not been released and clicks, rankings and conversions have not been measured.
End the report with a checkable follow-up
Use concrete next steps: obtain current conditions, test an import route, approve a page change or conduct a comparable follow-up. Name an owner and acceptance evidence. An unspecified recommendation to publish more content leaves the recipient with the same unanswered question.
Before sharing, review the audience and permitted fields. Remove private input and account identifiers; check provider-material sharing rights separately. Raw queries and fragment payloads do not belong in usage analytics events. These templates require no new tracking integration.
Disclose shared ownership for connected services. ai-fanout.com, SEO Fanout and Crawl Foundry form a connected workflow, not independent confirmation of the findings. End with the baseline, next review date and open limits so the report creates a task that can actually be followed up.
Next, you can plan the follow-up measurement.
Sources used
These sources support the functions and limits described here. They do not prove claims beyond that scope.
- Original prioritization, source-audit, measurement, repetition and reporting artifactsOpen source
Twenty blank/worked-example files and the end-to-end fictional buying-guide workflow. Source-audit rows review public primary guidance and owner disclosure. Measurement arithmetic and attempt states are explicitly synthetic, not website results, client outcomes, provider responses or benchmarks. No paid requests or new retained grounding output.
- 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.