InfiniteRanks resources

Case-study evidence: how to document an AI search outcome

A case study should let a reader distinguish the work shipped, the observations collected and the claims the data can support. This library does not invent customer outcomes.

InfiniteRanks editorial team

Document the baseline

Record the brand, permission to publish, market, language, prompt cohort, collection methods, model versions and dates. Include expected checks, eligible answers, citation-complete answers and failures. A percentage without starting counts can make a tiny change appear dramatic.

Show the intervention

Save the affected page URL, prior version, approved edits, publication date and review owner. Explain why the change was useful for the reader. Identify other events in the same window such as a product launch, campaign, redirect or model update. A timeline helps readers assess alternative explanations.

State the outcome conservatively

Compare the unchanged cohort and show raw counts as well as rates. Separate mentions, owned-site citations, referral sessions and conversions. Explain sample limits and any missing data. Do not call an observed before-and-after difference causal unless the design supports that conclusion.

Use the worked examples responsibly

The linked examples demonstrate calculations and editorial reasoning with explicitly fictional numbers. They are teaching material, not testimonials or claimed customer results. A publishable customer story needs permission and original evidence before it can replace an illustrative example.

Sources and further reading

Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.

Be part of the conversation.

Explore a model response with your own provider key.