Proof you can check: live case studies with disclosed sample sizes
Sep 27, 2026 · 4 min read
Published case studies are generated from measured campaign data — citations vs mentions, live vs estimated checks and the exact sample size — never hand-written marketing copy.

Marketing case studies have a trust problem: nobody can tell a measured result from a rounded-up one. So we stopped writing them by hand. Every case study on our Proof page is generated from the campaign's own tracked data.
Generated, not written
A case study is refreshed from the campaign's citation runs, GenO audits and ranking snapshots. The headline cites the measured citation rate; the metrics carry citation vs mention rates and engines present. If the numbers are weak, the case study says so — an honest 0% baseline is a better proof story than a vague win.
Sample size, always disclosed
Every published study carries its sample: checks per run, repeats this month, and how many checks were live API calls versus web-researched estimates. Fewer than three repeats in a month and the number is labeled a single scan, not a trend. The dogfood campaign on our own domain runs the full cadence so the sample is always big enough to judge.
Verify the loop, not the claim
The publish-and-verify loop records what was published and the before/after citation delta — so a case study isn't a claim about what the platform can do, it's a log of what it did. That's the standard we hold ourselves to, and the one we think buyers should demand from every GenO vendor.
Put this into practice on your own site.
Grade any URL free in about 60 seconds.





