What this workflow should accomplish
Category Definition gives teams defining the market language an audit should test a controlled input for AI visibility measurement instead of relying on ad hoc prompts or screenshots.
The result is a bounded measurement for a defined question set and collection period. It does not establish a universal ranking, guarantee future inclusion, or prove why a model produced an answer.
Why a generic visibility score is insufficient
a vague or internally invented category produces weak buyer questions and irrelevant competitors.
Keep the full evidence trail so a reviewer can distinguish absence, mention, recommendation, citation, and description accuracy.
teams defining the market language an audit should test
Use this playbook when the result will change a content, positioning, measurement, reporting, or go-to-market decision. Assign an owner before collection begins and agree on what evidence would justify action.
Start with a decision-shaped question
“What category would a buyer name when looking for this outcome without knowing our brand?”
Evidence to retain
customer language, product pages, competitor framing, analyst or directory terms, and exclusions.
Interpretation boundary
testing the wrong category can make a strong product look invisible.
Move from scope to a reviewable retest
- 01
Define the decision and audience
Define the decision and audience: teams defining the market language an audit should test.
- 02
Build a controlled question set. Start with
Build a controlled question set. Start with: “What category would a buyer name when looking for this outcome without knowing our brand?”
- 03
Retain customer language, product pages, competitor framing, analyst or directory terms, and exclusions.
Retain customer language, product pages, competitor framing, analyst or directory terms, and exclusions.
- 04
Review the main failure mode
Review the main failure mode: testing the wrong category can make a strong product look invisible.
- 05
Turn the finding into a test
Turn the finding into a test: document the primary category, adjacent categories, disallowed labels, and evidence for each.
audited questions mapped to an approved category
Publish the numerator, denominator, eligible question set, providers, collection dates, and exclusions beside the result. A score without its measurement contract is difficult to compare or audit.
Turn the observation into a test
document the primary category, adjacent categories, disallowed labels, and evidence for each.
Record the observation, hypothesis, planned change, owner, expected mechanism, and retest condition separately. This keeps the report honest when evidence is incomplete.
Questions to resolve before acting
What should Category Definition measurement include?
At minimum, keep customer language, product pages, competitor framing, analyst or directory terms, and exclusions. The result should remain traceable to the exact question and collection conditions.
What is the main interpretation risk?
testing the wrong category can make a strong product look invisible. Treat observed answers as bounded evidence, not proof of a universal ranking or a hidden model cause.
Which metric should the team review first?
Start with audited questions mapped to an approved category. Keep its numerator, denominator, eligible question set, and collection period visible beside the result.