Case Study Template
Formal issuance and production certificate status are shown on Rank and Status. Document version badges do not indicate issuance status.
Context
Entity, market, period, discovery surfaces and business objective.
Baseline
Query/prompt set, engines/models, collection dates, search visibility, generative mentions/citations, authority and integrity indicators.
Intervention
What changed, where, when and why. Separate SEO, GEO, entity, distribution, technical and integrity actions.
Measurement
Use the same sampling protocol where possible. Record model/engine versions and uncertainty.
Results
Report absolute and relative changes. Avoid claiming causation unless the design supports it.
Integrity review
Were any inaccurate claims, suspicious sources or unintended effects introduced?
Public evaluation protocol
If the case is published as a VGO public evaluation, pre-register the intent scenario and keep raw evidence as specified in EVALUATION-PROTOCOL.md. Report the denominator. Do not publish only the best screenshot.
Lessons
What appears transferable, what remains uncertain, and what should be tested next.
GEO 2.0 scenario record (when applicable)
- Customer decision scenario: audience, need, market, language and decision stage.
- Verified brand facts: supporting evidence, source version, owner and review date.
- Baseline: keep mention, accuracy, citation support and recommendation relevance separate.
- Priority and action: rationale, responsibility, authorization and exact change record.
- Verification: comparable sampling, denominator, failures, contrary evidence and outcome limits.
- Maintenance: remaining gaps, drift checks, asset history and the next review.
Use GEO 2.0 only for the generative scenario; preserve the broader VGO context.
