How to read your AI Visibility Score

Every audit ends with a single number out of 100. It's useful precisely because it's simple — but a score only means something once you understand what feeds into it.

Six signals, one number

The AI Visibility Score combines six weighted signals: mention rate (how often your brand appears across tested prompts), citation rate (how often the answer is backed by a source connected to you), competitor share (how much of the answer space competitors occupy instead), platform coverage (how consistently you appear across engines), source authority (how strong the domains citing you actually are), and brand consistency (whether your positioning is described the same way across answers).

None of these signals is pass/fail. A brand can have a strong mention rate but weak source authority, or excellent platform coverage but a fragmented brand description across engines. The score compresses all of that into one comparable number, but the report behind it is where the real diagnosis lives.

What the bands mean

0–39 is weak visibility: the brand is largely absent from the tested prompts. 40–59 is partial visibility: present in some contexts, missing in others that matter. 60–79 is strong but fragile: solid presence, but concentrated in a way that a competitor could disrupt. 80–100 is high visibility: consistent presence across engines, prompts, and sources.

The score is a proprietary decision-support indicator for the agreed audit scope — not an official engine metric, and not a ranking guarantee.

That distinction matters because AI-generated answers vary by model, user, context, and time. The score reflects visibility within a documented scope — a specific set of prompts, platforms, and competitors, tested on a specific date — so it stays interpretable and comparable over time, without pretending to be more precise than the underlying data allows.

That score comes from a full Growth GEO Intelligence Audit. If you have not run one yet, the free preview is a good first step — it checks your site's technical and semantic readiness before you request a deeper audit.