The result, 2026-09-20
| Engine | Asked in | Named in discovery prompts |
|---|---|---|
| Claude | August 2026 | 0 of 5 |
| ChatGPT | — | Not measured |
| Gemini | September 2026 | 0 of 9 |
| ChatGPT | September 2026 | 1 of 9 |
Correction, 11 October 2026: each row has its own date and question set
The table above stays as published and nothing was measured again. Its rows cannot be compared directly; this note separates them.
The denominators differ. The Claude row is 5 questions; the other two rows are 9, because 4 questions were added later. The table in the next section is the Claude row alone. 0 of 5, 0 of 9 and 1 of 9 cannot be added, averaged or ranked against each other. Every engine was also asked 3 brand prompts, which stay outside all of these counts.
The date in the heading is not a run date. 20 September 2026 is the day the last rows were added. The Claude row is dated 18 August 2026 and carried over unchanged. The date at the top of this page is now the date of this correction, not of a run.
The answers themselves are not published. This page reports the counts only.
Who gets named instead
This is the useful half. Across the discovery prompts, the assistant consistently names the same short list:
| Tool | Named in how many of 5 prompts |
|---|---|
| AppFollow | 5 / 5 |
| App Radar | 5 / 5 |
| Sensor Tower | 5 / 5 |
| AppTweak | 4 / 5 |
| Mobile Action | 4 / 5 |
Two things stand out. First, the list is entirely enterprise and mid-tier — the $9–39 indie tier that most solo developers actually buy from does not appear at all, in any prompt, in either language. Second, the Turkish prompts return the same names as the English ones, which suggests the answer is not localised so much as translated.
What to read alongside a name match
Asked directly — What is Storelift? — the assistant produced a confident description of a Meta measurement product for ad lift testing. That is not us. It is not anything, as far as we can tell.
A name match answers did a competitor get listed. It is not sufficient for is this my product, and this run is the proof: a bare name match scored a hit on an answer describing something else entirely.
So brand questions are excluded from the score. The alternative — counting that as recognition — would have made this page state something false about its own subject.
How to read this measurement
- An absent mention does not explain itself. This result does not show why an assistant left a name out.
- Compare only matching rows. Two rows compare only when the assistant and the question set are the same. Changing question sets do not establish a trend, and a changed answer alone does not identify its cause.
The same limits are printed inside the product, on the screen that runs this measurement for your app.
Frequently asked
Why publish a zero?
Because a visibility page that only appeared once the number turned favourable would be an advertisement, and the honest version of this measurement is the reason anyone should believe the ones we run for their app.
Does this mean AI visibility does not matter yet?
It means it is early, and that early is when the measurement is cheap. Store search still carries most installs, but the share moving to assistant answers is the reason this is measured at all — and a tool nobody names is a tool nobody installs from that surface.
How often is this rerun?
It is not rerun on a schedule. The table is one dated measurement, 18 August – 20 September 2026; a new measurement would be published with its own date, not written over this one. The date at the top of the page is the day the text last changed, not a run date.
See this for your own app
Paste your store link, add your keywords. Rank, the apps above you and demand are measured every day.
Free plan: 1 app, 25 keywords in each of 2 storefronts, 30 days of history, no card, no end date. Pro is $20/mo.
Start free →