Brief the decision, not a keyword
A discovery call, sales objection, search query or observed AI-answer gap can start the brief. The output is a page specification with a direct answer, evidence, a practical example and a review owner. The goal is to help a buyer decide, then make the answer easy to find and cite.
Record where the question came from. A sales call is evidence of one buyer's concern, not proof of broad search demand. Search volume is a different observation. An AI answer is a sample taken under specific engine, location and session conditions.
Write the brief
- Preserve the buyer's wording and define the decision behind it. Include stage, audience and the consequence of a poor choice.
- Inspect current search results and answer-engine sources. Read the actual linked pages rather than a list of domains.
- Separate a coverage gap from an evidence gap. A missing phrase does not mean the buyer needs another thin article.
- State the page's two-line answer and the practical output it will show: a decision table, workflow, worked example or editable sheet.
- Specify what the company can support from experience, what is a reference design and what requires external evidence. Attach primary sources and dates.
- Plan the necessary sections: when to use it, inputs, decision branches, exceptions, measurement and the next useful resource.
- Build the page in crawlable HTML with a descriptive title, canonical URL, author and visible source links. Make structured data match the page.
- Review the factual claims and usefulness with a person. Publish only the approved version, then observe discovery and buyer conversations separately.
A brief that guides production
- Question
- How should we route inbound leads without creating duplicates?
- Decision
- Existing owner first; enrichment must not delay ownership
- Useful output
- Branch map and example owner receipt
- Evidence
- CRM behavior checked; reference design labeled
- Commercial connection
- GTM engineering lane, with the standard start
Avoid false shortcuts
More pages do not repair a weak answer. Rewording a creator's post is not original evidence. A transcript or internal example needs permission and sanitization before publication. If the useful insight belongs to a source, cite it rather than presenting it as your own test.
Do not promise a citation or a ranking. Google says the existing SEO requirements apply to AI features; there is no special schema that guarantees inclusion. Use a normal, accessible page with useful evidence.
What to measure
Check indexability, internal-link discovery and whether a reader can answer the decision after reading. Track query and citation observations with dates and conditions. Record visits, resource-citing calls and downstream pipeline as different measures.
Compare repeat samples using the same prompt set, but preserve changed conditions. A newly cited page is an observation, not proof that one edit caused the change. Use the source-gap workflow to choose the next piece of work and the decision register to retain what was tested.
Publication and source record
Published on GTMhub: . Last reviewed: .