ChatGPT Citation Experiments (2026): 45 Figures From StatWharf Test Runs
Key figures
- ChatGPT answers that cited StatWharf, September 12, 2026
- 32 of 100
- ChatGPT fan-out searches that repeated the prompt as typed
- 0 of 211
- Page vendors named in answers after ChatGPT searched for them
- 76%
- SAP prompts that cited StatWharf on each of three days
- 16 of 20
From September 8 to October 11, 2026, StatWharf sent software category prompts to AI answer engines. This page reports what those runs measured. It covers four topics. The first is how often each engine cited a StatWharf page. The second is the searches ChatGPT ran before it answered. The others are prompt wording and how stable a citation is.
Every figure comes from StatWharf’s own experiment records. No third-party citation dataset is used. Each figure states the run date, the engine and the sample size (n). Most samples are small. The figures describe what happened in these runs. They do not show what causes a citation, and they are not stable citation rates for all users.
StatWharf publishes a longer write-up of one of these runs at How ChatGPT searches for software recommendations.
Method
StatWharf ran 9 experiment runs. Each run sent fixed prompts to an answer engine through a browser. It saved the full answer and the cited links. Where the engine exposed its searches, the run saved them too. Every prompt opened a fresh conversation. No prompt asked the engine to search, to cite or to mention StatWharf.
The core prompt panel used 50 software categories that StatWharf covers. Each category had a baseline prompt, best {category}, and a year prompt, best {category} 2026. Later runs used subsets of these categories and added new wordings.
| Run | Date | Engine | Prompts |
|---|---|---|---|
| Natural-query panel, logged out | Sep 8, 2026 | ChatGPT | 108 |
| Natural-query panel | Sep 9, 2026 | Gemini | 100 |
| Natural-query panel | Sep 9, 2026 | Google AI Overview | 100 records |
| SAP recheck | Sep 9, 2026 | Google AI Overview | 8 |
| Fan-out panel | Sep 12, 2026 | ChatGPT, Gemini, Google AI Overview | 100 each |
| SAP repeat days | Sep 12 to Sep 14, 2026 | ChatGPT | 20 per day |
| Persona prompts | Sep 14 and Sep 15, 2026 | ChatGPT | 33 and 44 |
| Phrasing panel | Sep 16 and Sep 17, 2026 | ChatGPT | 55 per day |
| Perplexity check | Sep 17 and Sep 18, 2026 | Perplexity | 11 and 10 |
A run counts as a citation only with a statwharf.com link among the sources the engine showed. The “intended page” is the StatWharf page for the category in the prompt. Failed captures, bot walls and answers saved before they finished are excluded from every count. The records, scripts and per-run tables are kept in the StatWharf experiment archive, dated by run.
Limits
Runs used one location in India and one account per engine, so results reflect that setup. Several answers localized to India without being asked. Most ChatGPT runs used model routing set to auto. The September 8 run was logged out, so it is not a clean comparison with later signed-in runs. Prompts are synthetic. They are not real user search logs. Many of the cited StatWharf pages belong to one cluster of SAP governance categories, so results lean on that cluster.
Citations by engine
On September 12, 2026, the same 100 prompts ran on three engines on the same day.
| Figure | Value | Engine, date, n |
|---|---|---|
| Answers that cited StatWharf | 32 of 100 | ChatGPT, Sep 12, 2026, n = 100 |
| Citing answers where the cited page was the intended page | 30 of 32 | ChatGPT, Sep 12, 2026, n = 32 |
| Answers that cited StatWharf | 0 of 100 | Gemini, Sep 12, 2026, n = 100 |
| AI Overviews that cited StatWharf | 0 of 100 | Google AI Overview, Sep 12, 2026, n = 100 |
| Result pages with StatWharf in ordinary organic results | 8 of 100 | Google Search, Sep 12, 2026, n = 100 |
| Answers that cited StatWharf, day 1 | 6 of 11 | Perplexity, Sep 17, 2026, n = 11 |
| Answers that cited StatWharf, day 2 | 5 of 10 | Perplexity, Sep 18, 2026, n = 10 |
Source: StatWharf fan-out experiment, September 2026, n = 100 prompts per engine.
The Perplexity check is small. It used 11 prompts on day 1 and 10 on day 2, because the engine stopped accepting searches after 10. It shows that Perplexity can cite these pages. It does not give a reliable rate.
Google placed StatWharf in its ordinary results more often than in its AI Overview. Seven of the 8 organic appearances were SAP categories.
Earlier logged-out and signed-in runs
The first runs took place on September 8 and 9, 2026. ChatGPT ran logged out. Google ran in a signed-in browser with unknown personalization.
| Figure | Value | Engine, date, n |
|---|---|---|
| Baseline prompts that cited StatWharf | 5 of 50 | ChatGPT logged out, Sep 8, 2026, n = 50 |
| Year prompts that cited StatWharf | 5 of 50 | ChatGPT logged out, Sep 8, 2026, n = 50 |
| Valid answers that showed source links | 108 of 108 | ChatGPT logged out, Sep 8, 2026, n = 108 |
| Answers that showed any link | 42 of 100 | Gemini, Sep 9, 2026, n = 100 |
| Visible links that were Google product-search links | 168 of 185 | Gemini, Sep 9, 2026, n = 185 links |
| Records with a verified AI Overview | 47 of 100 | Google AI Overview, Sep 9, 2026, n = 100 |
| Captured AI Overview links that pointed to StatWharf | 0 of 294 | Google AI Overview, Sep 9, 2026, n = 294 links |
| Result pages with StatWharf in organic results | 10 of 100 | Google Search, Sep 9, 2026, n = 100 |
| SAP queries with StatWharf in organic results | 8 of 8 | Google Search, Sep 9, 2026, n = 8 |
| SAP queries with StatWharf in AI Overview sources | 0 of 8 | Google AI Overview, Sep 9, 2026, n = 8 |
The logged-out ChatGPT rate was 10 of 100 across both arms. The signed-in run three days later was 32 of 100. Three things changed between the two runs: account state, model routing and four more days of crawling. The data cannot say which one moved the rate.
Gemini answered 58 of 100 prompts with no link at all. Most of the links it did show were shopping links, not editorial sources. The Google AI Overview capture on September 9 was incomplete. Only 47 of 100 records hold a verified AI Overview, and secondary source panels were not all expanded. The zero therefore covers the captured links only.
What ChatGPT searched
ChatGPT exposed its searches in the live response stream. Gemini and Google ran their searches on the server and sent none to the browser. These figures come from the September 12 run. The fan-out study gives the full method.
| Figure | Value | Engine, date, n |
|---|---|---|
| Runs with observable fan-out searches | 100 of 100 | ChatGPT, Sep 12, 2026, n = 100 |
| Fan-out searches in total | 211 | ChatGPT, Sep 12, 2026, n = 100 prompts |
| Median searches per prompt | 2 | ChatGPT, Sep 12, 2026, n = 100 prompts |
| Most searches for one prompt | 8 | ChatGPT, Sep 12, 2026, n = 100 prompts |
| Median words per search | 11 | ChatGPT, Sep 12, 2026, n = 211 searches |
| Searches identical to the prompt | 0 of 211 | ChatGPT, Sep 12, 2026, n = 211 |
| Searches that kept the exact category phrase | 143 of 211 (68%) | ChatGPT, Sep 12, 2026, n = 211 |
| Searches that contained a year | 161 of 211 (76%) | ChatGPT, Sep 12, 2026, n = 211 |
| Searches from no-year prompts that added a year | 63 of 102 (62%) | ChatGPT, Sep 12, 2026, n = 102 |
| Category phrase share, citing runs and non-citing runs | 68% and 68% | ChatGPT, Sep 12, 2026, n = 68 and 143 searches |
Source: StatWharf fan-out experiment, September 2026, n = 211 searches from 100 prompts.
ChatGPT kept the category phrase and added vendor names and a year. Searches that led to a StatWharf citation kept the phrase at the same rate as searches that did not. The phrase is a property of how ChatGPT expands these prompts. This data does not show that it predicts a citation.
Which vendors the answer named
StatWharf checked the answers that cited a StatWharf page against the vendors listed on that page. This pass used 105 ChatGPT runs from September 12 to September 15, 2026, with 987 vendor rows in total. A vendor counts as named only with its full name in the answer text.
| Figure | Value | Engine, date, n |
|---|---|---|
| Page vendors named in the answer | 482 of 987 (49%) | ChatGPT, Sep 12 to 15, 2026, n = 987 vendor rows |
| Named rate, vendor appeared in a fan-out search | 220 of 290 (76%) | ChatGPT, Sep 12 to 15, 2026, n = 290 |
| Named rate, vendor not in any fan-out search | 262 of 697 (38%) | ChatGPT, Sep 12 to 15, 2026, n = 697 |
Vendors that ChatGPT searched for were named about twice as often. The direction is not established. ChatGPT writes its searches before it reads any page, so a vendor name in a search mostly reflects the model’s own prior knowledge. Runs within a category are not independent, so any interval on these rates is optimistic.
Prompt wording
The phrasing panel ran 11 categories in five wordings on two days. The wordings were top {category}, which {category} for a 15-person team, alternatives to {vendor} {category}, {category} for startups and {category} vs {vendor}.
| Figure | Value | Engine, date, n |
|---|---|---|
| Prompts that cited StatWharf, day 1 | 34 of 55 | ChatGPT, Sep 16, 2026, n = 55 |
| Prompts that cited StatWharf, day 2 | 41 of 55 | ChatGPT, Sep 17, 2026, n = 55 |
| Intended page cited, “top” wording | 18 of 22 | ChatGPT, Sep 16 and 17, 2026, n = 22 |
| Intended page cited, “15-person team” wording | 17 of 22 | ChatGPT, Sep 16 and 17, 2026, n = 22 |
| Intended page cited, “alternatives to” wording | 13 of 22 | ChatGPT, Sep 16 and 17, 2026, n = 22 |
| Intended page cited, “for startups” wording | 12 of 22 | ChatGPT, Sep 16 and 17, 2026, n = 22 |
| Intended page cited, “vs” wording | 12 of 22 | ChatGPT, Sep 16 and 17, 2026, n = 22 |
| Mean day-to-day swing per wording | 2 of 11 prompts | ChatGPT, Sep 16 and 17, 2026, n = 11 per wording per day |
Source: StatWharf phrasing experiment, September 2026, n = 22 runs per wording.
The gaps between wordings are not reliable. Every wording rose from day 1 to day 2, by a mean of 2 prompts out of 11. The largest gap between wordings was 27 percentage points. A power check found that 33 prompts per wording detect only a gap of about 32 points. A third day was therefore not run.
The persona runs asked the same category prompts with a short description of the user in front. These samples are also small.
| Figure | Value | Engine, date, n |
|---|---|---|
| Intended page cited, plain prompt | 19 of 22 | ChatGPT, Sep 14 and 15, 2026, n = 22 |
| Intended page cited, startup marketer prefix | 13 of 22 | ChatGPT, Sep 14 and 15, 2026, n = 22 |
| Intended page cited, mid-market CMO prefix | 12 of 22 | ChatGPT, Sep 14 and 15, 2026, n = 22 |
| Intended page cited, neutral prefix of the same length | 6 of 11 | ChatGPT, Sep 15, 2026, n = 11 |
A neutral prefix with no persona lost about as many citations as the persona prefixes. Prompt length, or any extra context before the category phrase, explains much of the drop. The persona alone does not.
How stable a citation is
The same prompt does not always give the same result. Two measures show the size of this noise.
| Figure | Value | Engine, date, n |
|---|---|---|
| SAP prompts that cited StatWharf, each of three days | 16 of 20 | ChatGPT, Sep 12 to 14, 2026, n = 20 per day |
| Repeated prompt groups whose citation outcome changed between runs | 73 of 319 | ChatGPT, Sep 12 to Oct 11, 2026, n = 920 runs |
| Runs per arm needed to detect a 20-point lift between two sets of 3 pages | About 90 | ChatGPT, computed Sep 23, 2026, from 585 runs |
The SAP panel held at 16 of 20 on all three days. Across all repeated prompts, about 1 group in 4 flipped between cited and not cited at least once. A test of a page change therefore needs far more runs than a single day of a small panel provides.
FAQ
How often did ChatGPT cite StatWharf?
In the September 12, 2026 run, ChatGPT cited StatWharf in 32 of 100 answers. In 30 of those 32, the cited page was the page for the category in the prompt. A logged-out run on September 8 cited StatWharf in 10 of 100 answers.
Did Gemini or Google AI Overview cite StatWharf?
No. Gemini cited StatWharf in 0 of 100 answers on September 9 and again on September 12. Google AI Overview cited it in 0 of 100 on September 12. Google did show StatWharf in ordinary organic results on 8 of those 100 result pages.
Does ChatGPT search the prompt exactly as typed?
No. None of the 211 searches in the September 12 run matched the prompt. ChatGPT kept the category phrase in 68% of searches and added a year in 76%. More detail is in the fan-out study.
Does prompt wording change the citation?
The results moved by wording, but day-to-day noise was about as large as the gaps. The “top” wording cited the intended page in 18 of 22 runs and the “vs” wording in 12 of 22. The sample cannot separate those gaps from noise.
Why are the samples so small?
Each run is a live browser session, and engines limit how many prompts one account can run in a day. Small samples are stated next to each figure. Read figures with fewer than about 20 runs as examples, not rates.
Questions about the method can go to editorial@statwharf.com.
Work with StatWharf
Have a product relevant to this workflow? Get in touch about product profiles and content partnerships.
Factual corrections are free: editorial@statwharf.com.