Calculate a weighted visibility summary under more than one reasonable weighting scheme before using it to justify a decision. If the conclusion reverses, the report should show that sensitivity rather than presenting a single score as inevitable.
State what the weights mean
Weights can express commercial priority, equal coverage or a verified demand estimate. Those meanings are different. A planning priority does not become search demand because it appears in a spreadsheet.
NIST's experimental-design guidance recommends writing down and prioritizing objectives. For visibility reporting, declare the decision the score is intended to support before selecting weights. The calculations below are editorial examples.
Work through the arithmetic
Illustrative example: category questions have a mention rate of 20%, while branded questions have a rate of 80%. Equal group weights produce a 50% summary.
Giving category discovery an 80% weight and branded recall a 20% weight produces 32%: 0.8 × 20% + 0.2 × 80%. Nothing about the underlying answers changed. The summary changed because its objective changed.
This example is also a reason to keep discovery and branded recall visible separately. A favorable branded result can obscure an unbranded discovery problem.
Run a sensitivity review
- Freeze the valid observations used in each calculation.
- Document the primary weights and their rationale.
- Calculate an equal-weight alternative.
- Test one plausible business-priority alternative.
- Compare the action each summary would suggest.
- Inspect the component results when those actions differ.
Do not change the usable sample while testing weights. Otherwise, the difference may reflect missing data as well as weighting. Keep failed observations outside mention-rate denominators and disclose coverage.
Decide how to communicate instability
If a content priority is unchanged under all declared schemes, say the recommendation is stable across those tested assumptions. That is narrower than claiming it is objectively optimal.
If the recommended action changes, show the competing priorities and the decision the business must make. There is no statistical trick that can supply an undisclosed business objective.
Keep the primary weighting version with historical reports. A revised weighting scheme should have an annotation, bridge calculation or new series.
Read the share-of-voice calculation guide for metric units. Next, review the components behind an AI visibility observation and test whether one alternative weighting would change your proposed action.
Fact-checked: 17 October 2026. Examples are illustrative; no customer results are reported.