Educational use only. This tool structures a writing brief using frameworks from the Three Streams GEO Methodology. It does not guarantee AI citation, publication quality, or regulatory compliance, and it is not legal advice. The claims register is a workflow aid: every claim needs its own substantiation record and, in a regulated category, review by qualified staff before publication. Nothing is saved. This tool stores nothing on your device or anywhere else, so a reload loses the brief. Export before you leave.
1. Sentinel Query Set Builder 2. GEO Content Planner 3. Content Brief Builder 4. Writer drafts 5. QA Scorecard
What this tool does, and where it sits

A content plan decides what to publish and which queries each piece has to win. A writing brief tells the writer exactly what that piece must contain, and why. This tool turns one planned piece into that brief: an outline, a drafted Answer Capsule, evidence with substantiation records, entity rules, an internal linking plan, and a schema handoff to the Technical stream.

It produces two briefs from one set of inputs. The Content and Business brief goes to the writer. The Technical brief goes to whoever builds the page, and carries the entity and schema handoff the methodology's Comprehensive Handoff Matrix specifies, plus rendering, performance and crawler-access requirements.

Length is set by completeness, never by a word target (Guiding Principles §2.4). Answer the question fully; that is the length.

What to carry over from the GEO Content Planner

There is deliberately no import. The Planner is a teaching tool and so is this one; a machine handoff between them would turn the pair into a production system. Copying eight fields by hand takes a minute and keeps you reading what you decided.

From the Planner's review, for the piece you are briefing:

  1. Headline → Working title, on this tab
  2. Content type → Content type, on this tab. The type names match exactly.
  3. Summary and angle → Summary, on this tab
  4. Page status, new or improve → Page status, on this tab
  5. Entity to reference, long and short form, plus the Schema.org type → Primary entity, on the Queries & entities tab
  6. Hub page URL → Parent hub, on this tab
  7. Reader stage → Reader journey stage, on the Reader tab
  8. Target queries → Queries this piece must answer, on the Queries & entities tab

The Planner also carries anything its headline scanner flagged and left unresolved. Those belong in the claims register here, where they get classified and routed.

Piece identity

What the piece is, what it is called, and where it sits.

The type decides the structure, the schemas the Technical brief will specify, and which techniques matter most. The first three groups use the same names and keys as the GEO Content Planner, so a planned piece maps straight across. The fourth group covers pages the Planner does not produce.

Product and service content is the long-form layer where citation earning happens: statistics, expert quotes, self-contained sections, outbound sources. Brand and editorial pieces build the Organization or a named Person as an entity and carry no product schema at all. Brief-Builder-only types cover conversion and service pages that are not query-driven, so the Planner never produces them.

Length follows completeness, not a word count. Comparison pages reward real HTML table density; technology explainers reward DefinedTerm and dual nomenclature; how-tos reward HowTo schema and numbered steps.

Source: Three Streams GEO Methodology — Foundations, Content Architecture Principles; §2.4 Guiding Principles on length.
Product, service or topic · from the Planner
Brand & editorial · from the Planner
Custom · from the Planner
Brief Builder only · the Planner does not produce these
Brand and editorial pieces carry no product schema. The entity being reinforced is the Organization, or a named Person, not a product. Press and award pieces must name the awarding body, the award and the year, and link the source. Founder and team pieces need real named people with verifiable credentials. Self-reported figures must be attributed to your organisation in-text.
Comparison pages reward table density. Plan the tables here rather than leaving the writer to invent them: a criteria table, a head-to-head, and one that resolves by use case or audience. Tables must be real HTML in the page source, never images, or the structure is invisible to crawlers that cannot execute JavaScript.
The question-and-answer wrapper alone earns nothing. Pair every question with a verifiable specification, statistic or sourced citation. A question-formatted heading answered with reassurance underperforms a plain heading answered with evidence.
Custom pieces have no standard structure. The outline falls back to a generic shape and the schema handoff defaults to Article. Set the entity types by hand, and describe the shape explicitly in the summary below — there is no type convention for the writer to lean on.
How the body is structured, independent of the content type. Any type above can be written as a numbered informational list; the type still decides purpose, schemas and techniques.
Informational listicles only. Numbered format suits things-to-know, mistakes-to-avoid, signs, checks and steps: each entry becomes its own self-contained section, and ItemList schema is added to the Technical brief automatically. It is not the format for a ranked competitive best-of list on your own page: every ranked entry naming a competitor is a comparative claim needing head-to-head substantiation, and an organisation ranking itself first on its own site is not read as neutral. Best-of citation share is earned through placement in third-party roundups, which is Business Stream work, not owned content.
The H1 of the finished page, exactly as it should publish. Headlines are written and scored in the GEO Content Planner; bring the one you settled on there.
The angle decided in the Planner. It carries into the brief so the writer knows the intent behind the outline, not just its shape.
Whether the writer is building a new page or upgrading a live one. An upgrade needs the existing URL and a note on what changes; a refresh that only moves the date stamp is not a refresh.
Attribution changes the piece's authority weight. Match the model to the stakes: safety, health, financial or efficacy claims need a real expert byline; general editorial can use expert review.
The hub page this piece supports. Used in the internal linking plan, and in the Technical brief's canonical checks.

Reader & context

Who the reader is, where they are in the journey, and what real situation brings them here.

The job the reader hires this content to do. Most real jobs stack a functional task with an emotional or social payoff.

Customers do not buy products, they hire them to do a job. A functional job is a practical task; an emotional job is a feeling; a social job is how the outcome is perceived by others. Retrieval works on semantic meaning, so content that addresses the feeling and the situation gets retrieved for queries that never state them outright.

Source: Christensen et al. (2016), Competing Against Luck, Harvard Business School. Application to GEO mapping is logical inference, not GEO-research-validated.
When I , I want to , so I can
A specific audience plus explicit exclusions. Telling the writer who the piece is not for is what prevents the generic, everyone-flavoured prose that retrieval skips over.
Where the reader sits. The GEO Content Planner infers this from the pillar mix of the queries you claimed; bring that answer here, or override it.

The opening is the strongest citation zone: 44.2 percent of AI citations came from the first 30 percent of content in a 1.2 million answer analysis. But if the content type mismatches the reader's stage, the piece is skipped regardless of how good the opening is. GEO's leverage sits upstream, in research and comparison; at the point of purchase the reader is already convinced and the job is a frictionless path, not more persuasion.

  • Awareness — educational content, foundations, problem explanation. Inferred from Category and Problem queries.
  • Consideration — comparison guides, expert reviews, feature breakdowns. Inferred from Solution and Competitive queries.
  • Decision — authority signals, proof, evidence. Inferred from Product queries.
Source: Three Streams GEO Methodology, Foundations (JTBD content mapping); Growth Memo (Feb 2026), correlational; Liu et al., "Lost in the Middle" (TACL 2024).
The real-life situations that make someone think about your category at all. A single piece can address several.

Category Entry Points are the situations that trigger category consideration. The 7W framework organises them into seven dimensions: Why, When, Where, With whom, With what, While, and How you feel. A CEP-anchored piece describes the situation before introducing the solution, which matches how real queries are phrased — situation first, product second — so the piece becomes findable through situational queries and not only product ones. Skip this for foundational explainers.

Source: Romaniuk, J. (2018), Building Distinctive Brand Assets, Ehrenberg-Bass Institute. Application to GEO is logical inference.

Queries & entities

Which queries this piece must answer, which entities it establishes, and how it connects to the rest of the architecture.

One per line, in the words a real person would use. Bring the queries you claimed onto this piece in the GEO Content Planner. These are retrieval targets, not a section list: one section can answer several, and some may need only a sentence.

AI systems often cite a single section rather than a whole page. A page with six self-contained sections, each answering a real query, gives six chances to be cited rather than one. These are the sentinel queries you track to measure citation lift. A page can target one query or several — clustering saves pages, it does not raise citation odds.

Source: Three Streams GEO Methodology — Foundations (JTBD and CEP as sentinel query foundations; Measurement Principles); Liu et al. (TACL 2024) on self-contained extraction.
Queries added: 0
The product, service, technology or topic this content is really about. Enforces entity-first writing in the brief, and becomes the anchor of the Technical brief's schema handoff.

AI systems use named-entity recognition to decide what a page is about, then map how entities relate. Vague references — "our product", "this tool", "it" — are invisible to that layer, and an unnamed entity cannot be cited or connected. The pattern: first mention uses the full name plus its category; later mentions use a shorter but still specific form; never pronoun-only.

Every major section must re-establish its primary entity in full, because sections are extracted independently of each other.

Source: Dunietz & Gillick (2014), "A New Entity Salience Task with Millions of Training Examples", Google Research, EACL 2014. Three Streams GEO Methodology, Foundations §6.2 (Entity-First Writing).
The Schema.org type that best matches the subject. This drives the structured-data handoff in the Technical brief.
A piece is about more than one thing. Name each one explicitly and type it for schema. This is both an instruction to the writer and the entity-architecture handoff the Technical stream needs.

Name all the kinds that appear, not only your own brand: the product or service; any technology or method it uses; a component, material or ingredient; an attribute or segment the piece addresses; each competitor named in a comparison; and every named expert with their credentials. Add a row per entity below and pick its role; the Schema.org type is suggested from the role and stays editable.

Entity and naming decisions are made in Content; the JSON-LD implementation belongs to Technical. Keep your legal entities distinct if you have more than one — a parent organisation, an operating company and a consumer brand are three entities, not one.

Source: Three Streams GEO Methodology — Foundations §6.2; Coordination Framework, Comprehensive Handoff Matrix (Content → Technical).
Beyond the parent hub: which sibling pieces this should reference. Internal links scope the page and declare relationships AI can follow.

Evidence & compliance

Every claim, its primary record, its classification and its review route — decided at brief stage, before a writer drafts a word.

Compliance requirements vary by industry and market. Setting these surfaces the concerns and claim boundaries for your vertical, and the regulators for your jurisdiction, instead of generic advice.
For each claim, name the record it traces to and set the two axes. The tool returns the risk level and the review route it implies.

Why evidence is decided at brief stage. Statistics, expert quotations and credible source citations each lifted AI visibility by up to 40 percent in the Princeton study, with source citations reaching up to 115 percent for a page ranked fifth — but only if the evidence is real. And a published claim never decays: an AI restates it with full confidence in month eighteen, stripped of your hedges. The rule is that every number traces to a primary record — the test report, dashboard export, spec sheet or published study it came from, not an article that repeated it. If you cannot name the record, do not publish the number.

The universal requirements, which apply in every industry and market: claim substantiation, endorsement and testimonial disclosure, and AI-generated content disclosure. Under substantiation doctrine the evidence must exist before the claim is published, the test conditions must match the claim's conditions, best-case figures must disclose what is typical, and "up to X" still needs data showing X is achievable — "up to" is not a loophole.

Classification decides the route. Claims are classified by category and by substantiation status. The two together produce a risk level, and the risk level names who has to review it before it ships.

Record on fileNeeds verificationNo record
Sources: Aggarwal et al. (KDD 2024), "GEO: Generative Engine Optimization", arXiv:2311.09735. Three Streams GEO Methodology, Appendix F: F.2 Universal Compliance Requirements, F.8.3 Claim Type Classification, F.8.5 Review Workflow by Claim Type. The risk grid itself is this tool's construction — see the provenance note at the foot of the page. Workflow guidance, not legal advice.
Whether content was made with AI is a material fact. AI-assisted drafting with human review is permitted. AI-generated visuals, voice or synthetic people require a clear up-front label. AI-generated reviews and fabricated before-and-after imagery are prohibited outright.
Named person, credential, institution, and a specific mechanism-based claim. "Experts say" is not quotable evidence. If a quote makes a performance claim about your own offering — including from your own staff — it is also your claim: register it above so it gets classified.
Category, research or market figures from outside sources, each with its attribution. Your own performance numbers do not go here — they go in the claims register, because they need classifying. A third-party figure needs a real, checkable source, not a classification.
Outbound references the piece will cite. Aim for three to five authoritative references per thousand words, and at least one Tier 1 or Tier 2 source for anything touching science, safety, health or money.
Which real HTML tables the piece will carry and what their columns are — a structural decision of the same rank as the headings. The writer fills the cells. Any cell value that is a claim must trace to the register above.
Draft a 40 to 60 word self-contained answer to the piece's core question. The checks update as you type. It travels into the brief as a reference and an extractability check, not as a mandated opening paragraph: if the piece cannot be answered this compactly with a real number and a named entity, the argument is not yet sharp enough.

An Answer Capsule is a 40 to 60 word, self-contained answer placed directly under the title or a heading, with no links inside the block. It names the entity, states the core claim, and carries one verifiable number. In a roughly two million session audit, 72.4 percent of cited blog posts contained one — the single most common trait of cited content — and over 90 percent of cited capsules were link-free.

It is the executable form of the answer-first principle: 44.2 percent of AI citations came from the first 30 percent of content, and the start of a long context is the model's highest-attention zone. Put citations in the supporting text below the capsule, not inside it. Evidence tier: correlational.

Sources: Search Engine Land session audit (Nov 2025); Indig / Growth Memo (Feb 2026); Liu et al., "Lost in the Middle" (TACL 2024). Specification: Three Streams GEO Methodology, Foundations §6.3.
Word count: 0 (target 40–60)
·40 to 60 words
·Entity named within the first five words
·Carries at least one verifiable number
The fifth requirement cannot be machine-checked: the capsule has to stand alone if an AI extracts it with no surrounding context. Read it back cold and ask whether it still answers the question.

Generate & export

Check the brief's strength and its release gate, then export in the format the writer or the developer needs.

Brief strength 0/100 Early draft
    Four forces decide whether a reader actually switches. Each one you fill becomes a named writing instruction in the brief. They are advisory: they do not change the score and do not gate the brief. Leave any blank to omit it.

    Every switch is governed by two forces pushing forward — the push of current frustration and the pull of the new solution — and two holding back: the anxiety of switching and the habit of the status quo. The unaddressed anxieties are exactly what comparison-stage readers ask AI about.

    Source: Moesta, B. (2020), Demand-Side Sales 101. Application to GEO brief quality is logical inference.
    Push
    What makes the reader unhappy with their current state?
    Pull
    What does the solution offer that resolves the push?
    Anxiety
    What fear might stop them switching?
    Habit
    Why might they stay with what they have?
    Release gate

    The hard requirements. The brief will not generate until every applicable item clears. The strength score above is advisory; this checklist is what actually blocks.

      Writing Brief
      The instruction document handed over before drafting. Every strategic and compliance decision is made; the prose is what remains.

      Content Brief Builder — part of the Three Streams GEO Methodology, Content Stream. Downstream of the GEO Content Planner; content types and their names are shared between the two tools.

      Writing techniques: Princeton (Aggarwal et al., KDD 2024), UC Berkeley GEO-16 (2025), Liu et al. "Lost in the Middle" (TACL 2024), SAGEO Arena (Yonsei, 2026), Search Engine Land (Nov 2025), Growth Memo (Feb 2026), Vercel crawler analysis. Compliance: FTC Act §5 substantiation doctrine, FTC Endorsement Guides (16 CFR Part 255), Consumer Reviews and Testimonials Rule (16 CFR Part 465), and the Methodology's Appendix F. Jobs-to-Be-Done: Christensen. Forces of Progress: Moesta. Category Entry Points: Ehrenberg-Bass (Romaniuk).

      Educational use only — not legal advice. This tool does not guarantee AI citation, quality or regulatory compliance. Verify every claim against its primary record and route anything the register marks for review to the people who own that decision. Per Guiding Principles §2.4, no arbitrary word counts — length is set by the completeness needed to answer the question fully. Nothing is saved: export before you close the page.