Labs / Archive note · Updated 2026-09-26

Tools that score how AI mentions a business have a trust problem, and it isn't a secret

Buyers of tools that score how AI mentions a business keep saying the same thing: nobody trusts the numbers.

Running experimentBuilt and running, being proven.

Explore with AI

Field report

01

The complaint the market keeps repeating

We didn't go looking for a trust problem. It's the top of the pull. The highest-engagement thread we found, titled roughly “How are people actually handling AI-search visibility? Not sure these tools are worth it,” has the OP stating it plainly: the honest problem is not trusting the numbers, and not knowing what to do with them even when you do (r/SEO, 11 points, 20 comments).

A second, unrelated thread names the sharper version of the same failure: a brand gets mentioned in an AI answer, but the surrounding context is wrong (r/TechSEO). That is not a scoring complaint. That is a factual-accuracy complaint about a product whose entire job is reporting facts about a business.

Independent reviews back up the anecdote. Semrush's AI Toolkit has been called probabilistic guesswork for brands with a thin AI presence. Independent testing of Ahrefs' Brand Radar found gaps between what it reported as citations and what manual inspection of the same AI answers actually showed.

This is not a gap in the market's tooling. It's the gap this Observatory entry's own “next” step already named.

02REVIEWED

Zero of nineteen disclosed how the number was made

The sharpest single data point in the pull is a GitHub audit of 19 Chinese-market GEO (generative-engine-optimization) vendors, checked against one question: does the vendor disclose how its score is made? Zero of 19 disclosed per-prompt sample count, noise floor, confidence interval, or seat pricing.

elmo's own explainer names the three levers that make two vendors disagree on the same brand's score: which prompts get asked, how each prompt is weighted, and how a raw AI answer becomes a counted “mention.” Every one of those levers is a private methodology choice, invisible to the buyer, and none of the tools we surveyed publish theirs.

A score with no visible methodology is a guess with a decimal point.

03TESTED

What we found pointing a real audit at a real client

We ran our own check the same way the Reddit thread described the failure: not by reading the rollup number, but by reading what the AI model actually wrote. The client is a real, live home-services business, and the prompts were the ones we already track for them.

Most of what the model named checked out — real businesses, sometimes under a different public name or handle than we expected, which we confirmed by hand. One competitor named in the answer did not. It does not resolve to any verifiable, currently operating business in that service area that we could find. We are not publishing the name; the point is not to call out one business, it's that an AI answer stated a fact-shaped claim with no visible uncertainty, and the fact underneath it did not hold up to five minutes of checking.

That is the exact shape of the second Reddit complaint above, reproduced on our own audit, on a real client, this month. We did not have to go looking for a caveat to publish — the caveat found us.

The market's complaint about AI answers stating wrong things with total confidence is not theoretical. It showed up in our own audit the first time we read the raw text instead of the score.

04REVIEWED

Where the open lane actually is

Vendor tiering in this category is well established: Profound owns enterprise, Peec AI targets agencies, Otterly.ai is the cheap entry point, Scrunch AI differentiates on how AI agents read a site rather than how chat answers cite it, Rankscale claims the most AI responses per dollar for small businesses. None of the five claim a truth-check layer.

The open-source side tells the same story from a different angle. Well-starred tools exist for the observation layer — elmo, Auriti-Labs' geo-optimizer-skill, aigclink's geolook — with full diagnosis-to-strategy-to-verification workflows. elmo's own positioning line, “every metric auditable in code,” is the identical complaint the Reddit threads open with, solved the identical way we're solving it: transparency over a better-sounding score. None of the surveyed tools, open-source or commercial, check a claim against a canonical source of facts about the business being described.

The truth-check layer is not a crowded lane. Nobody surveyed — paid or open-source — claims it.

05

What this changes about what we're building

Two things follow directly from this month's research, and both are already in motion rather than proposed. First: prioritize the truth-check loop — Business Truth checked against what an AI model actually said, verdicted SUPPORTED, CONFLICT or UNKNOWN, with UNKNOWN treated as a real answer rather than a failure to hide — as the thing we lead with, over a raw mention count. The market asked for exactly this, unprompted, five separate times.

Second: the unverifiable-name finding is not a one-off to note and move past. An AI answer naming a competitor we can't verify as real is a distinct, checkable failure mode. Our audit now flags it, with the quote, the run it came from and every verification attempt recorded, and with "could not verify" treated as a real answer, not proof the name is fake.

Publish the methodology instead of a better score. Flag what can't be verified instead of repeating it.

What we asked and what we found

Every entry answers the same eight questions, in this order.

Question

What do buyers of AI-mention scoring tools say is broken, and does it match what we are building?

Why it matters

We would rather take a direction from the market's complaints than from vendor pitches. We pulled threads from Reddit, Hacker News, GitHub and the web, then pointed our own audit at a real client and read the raw AI answers ourselves instead of trusting the rollup number. One finding is uncomfortable, and we publish it anyway.

State

Running experiment Built and running, being proven.

What we built or tested

  • A research pull across six Reddit communities, Hacker News, GitHub and the open web, dated 2026-09-25.
  • A read of our own audit against one live client's tracked questions: the actual sentences an AI model wrote about them, not the overall score.
  • A new kind of finding: an AI answer that names a competitor nobody can confirm exists. It is raised only after recorded attempts to verify the name, and never labeled proven fake.
  • A first connection for Google Search Console, Analytics and the Google Business Profile, and an import of a public listing's name, address, phone and hours.

Evidence

Methodology disclosure, 19 GEO vendors audited (GitHub)
0 of 19 disclosed sample size, noise floor, confidence interval or seat pricing
Market complaint, five separate threads, Sept 2026
“the honest problem is I don't fully trust the numbers, and even when I do, I'm not sure what to actually do with them” (r/SEO) — “Our brand gets mentioned in AI answers, but the context is completely wrong” (r/TechSEO)
Competitive set surveyed
Profound, Peec AI, Otterly.ai, Scrunch AI, Rankscale, AthenaHQ, Semrush AI Toolkit, Ahrefs Brand Radar — none check whether a cited answer is actually true
Our own audit, one live home-services client, Sept 2026
One AI-named competitor in the answer could not be independently verified as a real, currently operating business in the service area

What we learned

  • The loudest complaint is not that the score is low. It is that nobody can tell whether the number means anything, said the same way by people who have never met.
  • Our own audit surfaced the same failure: an AI answer stated something with full confidence that did not survive a direct check.
  • Every well-starred open-source tool does the watching well. None of them checks a claim against a confirmed source of facts about the business. That gap is not crowded.

Limitations

  • The vendor comparisons are secondhand: independent reviews and vendor claims, not our own audit of their tools.
  • The unverifiable competitor is one flagged name on one client's audit. It shows the failure exists, not how often.
  • Reddit and GitHub engagement is a signal, not a market-size study.

What changes next

Run checks for local and service clients with a known service location, publish the measured rate on Labs, and add owner-authorized Google Business Profile sign-in as the next connection.
Failed tests are published as results. A state on this page describes today, not plans.

Sources and credits

These tools belong to the people who made them. Lehvel reviewed and, where noted, tested them. Nothing here is a Lehvel product, and no performance figure attributed to a vendor has been reproduced by us.

Next in Labs

Explore with AI

Get Upstream

One note a week: one job we took off an owner's plate, and what came of it.

My posts reach 17,000+ followers across our channels. The weekly email is called Upstream.

Weekly. Unsubscribe anytime. Privacy