Standing vs Ahrefs Brand Radar

Where Ahrefs Brand Radar is better

• If you already pay for Ahrefs, this is included, and the marginal cost of adding it is zero.
• An enormous pre-collected prompt corpus that we cannot match, sourced from their keyword database.
• The rest of Ahrefs. Backlinks, keywords and site audit in one place is a real advantage no pure-play has.
• They are unusually honest about instability in their own documentation.

The prompt basket

Ahrefs Brand Radar: Bundled with Ahrefs plans; custom prompts metered in checks (Lite 150/mo, Standard 300, Advanced 600, standalone 2,500).

Checks, defined by Ahrefs as one prompt execution times one LLM times one location. Those collapse quickly: 10 prompts across 4 tools and 2 locations is 80 checks per refresh.

Standing: a fixed basket built from your category, priced per domain rather than per prompt. It is the smallest basket in the category and the only fixed one, which is the trade: fewer questions, but the same questions every scan, so a change in the score is a change in the answers rather than a change in what we asked. It also means two customers in one category are directly comparable.

How many times each question is asked

Ahrefs Brand Radar: Once per prompt per engine per location per refresh for custom prompts, stated as a billing definition rather than a methodology claim. A unit denominated in single executions leaves no room for repeats. For their pre-collected corpus the run count is not published. They substitute a 90-day reporting window for replication, which is temporal smoothing rather than repeated measurement.

Standing: 5 runs per prompt per engine on paid scans, 3 on the free check, published. Roughly 300 responses per paid scan. This is the number that decides whether a score is a measurement or a single draw from a distribution.

What each publishes about uncertainty

Ahrefs Brand Radar: No error bar, confidence interval or significance threshold, but the most explicit instability admission in the category: they tell users not to obsess over individual responses since they can change from one minute to the next, and describe their metrics as directional indicators. The 90-day window is justified for stability, which is an acknowledgement that a single cycle is unstable, handled by widening the window rather than measuring the variance.

Standing: a 95% confidence band on every score, shown in the product, with alerts gated on whether a move exceeds that domain's own historical drift. An engine that fails more than half its calls reports that it did not respond rather than a measured zero. Our own weakness, stated: the band covers within-scan sampling and does not cover platform drift between scans, which is why the model version is on the report.

Where Standing is better

• We measure the variance rather than widening the window until it disappears. A 90-day average hides a change as effectively as it hides noise.
• 5 runs per prompt per engine, published, against a billing unit that is explicitly one execution.
• A confidence band in the product, and significance-gated alerts.
• We do not require an Ahrefs subscription, and the free check needs no account.

Which to pick

Other comparisons

• vs Profound
• vs Peec AI
• vs Otterly AI
• vs Semrush AI Toolkit
• vs AthenaHQ
• vs Scrunch AI
• vs Evertune