# ChatGPT's research depth doubled: What it means for brands

On August 8, 2026 ChatGPT doubled the pages it consults per answer. Regulators gained, affiliate media lost, and 85.9% of brands gained own-site citations.

**Published:** August 19, 2026
**Author:** Ivan Slobodin

---

Across 5,000+ tracked brands, the pages ChatGPT shows it consulted went from **11.6 to 22.5 per answer**, and it began aiming `site:` searches at named domains. It happened overnight. Regulators gained most of the reading, consumer affiliate media lost on every measure, and **85.9% of brands are now cited from their own site more often than two weeks ago**.

<figure className="not-prose my-10 border border-stone-200 rounded-xl bg-white p-6">
  <p className="text-sm font-semibold text-stone-900 mb-1">Domain-targeted searches inside the fan-out</p>
  <p className="text-xs text-stone-500 leading-relaxed mb-4">Share of ChatGPT's internal sub-queries that use a site: operator to restrict results to one named domain. Flat for months, then a step change that has held for ten days.</p>
  <div className="overflow-x-auto">
<svg viewBox="0 0 1000 330" role="img" aria-label="Line chart showing the share of ChatGPT's internal sub-queries that use a site: operator. Flat near 0.2% from July 28 through August 7, then stepping to 15 to 20% on August 8 and holding through August 17." className="w-full h-auto min-w-[700px]"> <line stroke="#e7e5e4" strokeWidth="1" x1="60" y1="280" x2="960" y2="280" /> <line stroke="#e7e5e4" strokeWidth="1" x1="60" y1="225" x2="960" y2="225" /> <line stroke="#e7e5e4" strokeWidth="1" x1="60" y1="171" x2="960" y2="171" /> <line stroke="#e7e5e4" strokeWidth="1" x1="60" y1="116" x2="960" y2="116" /> <line stroke="#e7e5e4" strokeWidth="1" x1="60" y1="62" x2="960" y2="62" /> <text fontSize="11" fill="#78716c" x="40" y="284" textAnchor="end">0%</text> <text fontSize="11" fill="#78716c" x="40" y="229" textAnchor="end">5%</text> <text fontSize="11" fill="#78716c" x="40" y="175" textAnchor="end">10%</text> <text fontSize="11" fill="#78716c" x="40" y="120" textAnchor="end">15%</text> <text fontSize="11" fill="#78716c" x="40" y="66" textAnchor="end">20%</text> <line x1="544" y1="46" x2="544" y2="288" stroke="#a8a29e" strokeWidth="1.5" strokeDasharray="4 4" /> <text fontSize="11.5" x="552" y="44" fill="#a8a29e">Aug 8</text> <polyline fill="none" stroke="#c15f3c" strokeWidth="2" strokeLinejoin="round" strokeLinecap="round" points="60,279.5 104,279.6 148,279.5 192,279.3 236,279.3 280,279.1 324,279.2 368,279.3 412,279.0 456,278.7 500,278.6 544,162.5 588,71.2 632,76.4 676,63.2 720,92.8 764,73.8 808,98.9 852,103.9 896,85.2 940,118.5" /> <circle cx="500" cy="278.6" r="4.5" fill="#ffffff" stroke="#c15f3c" strokeWidth="2" /> <circle cx="676" cy="63.2" r="5" fill="#c15f3c" stroke="#ffffff" strokeWidth="2" /> <text fontSize="11.5" fill="#57534e" x="676" y="50" textAnchor="middle">19.9%</text> <text fontSize="11.5" fill="#57534e" x="480" y="268" textAnchor="end">0.13%</text> <text fontSize="11" fill="#78716c" x="60" y="304" textAnchor="middle">Jul 28</text> <text fontSize="11" fill="#78716c" x="324" y="304" textAnchor="middle">Aug 2</text> <text fontSize="11" fill="#78716c" x="544" y="304" textAnchor="middle">Aug 8</text> <text fontSize="11" fill="#78716c" x="764" y="304" textAnchor="middle">Aug 13</text> <text fontSize="11" fill="#78716c" x="940" y="304" textAnchor="middle">Aug 17</text> <text fontSize="12" fill="#57534e" x="60" y="325">Unbranded prompts · sub-queries the model generated itself</text> </svg>
  </div>
  <p className="mt-4 text-xs text-stone-500 leading-relaxed">Unbranded prompts, counting only sub-queries the model generated itself.</p>
</figure>

## Five numbers that define the August 8 change

| Measure | Before | After | Change |
| --- | ---: | ---: | ---: |
| Pages shown as consulted, per answer *(paired, same prompts)* | 11.58 | 22.54 | 1.95× |
| Answers running multi-query research | 2.0% | 57.2% | 28× |
| `site:` share of fan-out sub-queries | 0.2% | 18% | ~90× |
| Inline citations per answer | 0.49 | 0.82 | 1.68× |
| Brand mention rate *(share of voice)* | 40.5% | 37.6% | −2.9 points |

## Did ChatGPT do more research, or just disclose more of it?

**Why this question matters.** Fan-out and source lists come from the product's research disclosure panel. If OpenAI simply started *showing* more of a process it had always run, the source-side results would reproduce with zero change in behavior.

**What we can rule out, and what we can't.** Two scrapers agreeing rules out one vendor's bug, but both read the same surface. The non-browsing API route is only ~2% of our ChatGPT volume, with the rest coming from provider scraping, so it amounts to a footnote, and it never spoke to the disclosure question anyway.

**Why answer length can't settle it.** On 287,157 identical prompts, ChatGPT answers did grow, but the *median* prompt gained only +5.1%, with 56.8% coming out longer. That's barely above a coin flip.

**Every other engine moved the same way.** Same paired basis, same window: AI Overviews +4.7% median, Gemini +6.9%, Copilot flat at −1.5%, Perplexity −34.5%. Three engines moving together points at something shared across all of them: prompt population, our own extraction, or a shift on the vendor side.

Set the disclosure question aside for a moment, because the rest of this holds whichever way it resolves.

**Depth changed. Length within each depth didn't.** A three-sub-query answer looks much the same in July as in August. There are simply 40× more of them. The small rise in the mean comes from that shift in composition.

| Fan-out depth | Share of answers before | Share after | Median length before | Median length after |
| --- | ---: | ---: | ---: | ---: |
| 1 sub-query | 98.0% | 42.8% | 2,355 | 2,340 |
| 2–3 | 1.9% | 44.3% | 2,472 | 2,538 |
| 4–7 | 0.04% | 9.9% | 3,111 | 3,306 |
| 8+ | &lt;0.01% | 3.0% | n=1 | 4,580 |

**The trail changed shape as well as size.** 43% of answers still show a single sub-query, exactly as before, while the rest moved into multi-step. Whether that reflects new routing or newly visible routing is the open question above. Either way, it's what we and everyone we track now observe.

**It doesn't hit every prompt equally.** Sorted by intent, the effect concentrates on comparison and consideration queries:

| Prompt intent | Sources before | Sources after | Ratio |
| --- | ---: | ---: | ---: |
| Commercial ("best X", "X vs Y") | 11.60 | 24.64 | 2.12× |
| Informational | 11.73 | 20.51 | 1.75× |
| Transactional | 11.01 | 17.58 | 1.60× |

**Why 478 brands barely moved.** They run 39.9% branded prompts against 12.2% for the rest, and skew informational. This isn't a collection artifact: same scraper, same route, same baseline depth. They simply own prompt sets that the change barely touches.

### What would settle this, and why we can't run it yet

**The test that would settle it.** A structural diff of raw captures either side of 00:30 UTC on Aug 8: did the source and sub-query list move to a different element, or did an existing element start filling up?

**Why we can't run it.** Raw HTML captures aren't retained in the analysis dataset, and the search-query records carry no provenance field. Answering it means going back to the raw captures while they're still inside their retention window.

**What holds either way.** Every citation-side result stands, because inline citations come from the answer body. So does the timing of the break, which lands inside a running collection window rather than at its edge, and so cannot be our own run changing.

**What depends on the answer.** Pages read per answer, the `site:` share, and the read-side category mix. If the pre-period only ever disclosed one sub-query, those denominators are weak. That's why the headline reads "0.2% → 18%" and not a single dramatic multiple.

## ChatGPT reads more institutions, but cites more vendors

Every figure below is a share ratio that has already been normalized against pool growth, so 1.00× means a category held exactly the share it had before. Above 1.00× it gained ground, below it lost ground, and that holds even where the raw count rose. The pool grew 1.82× for reading and 1.68× for citing, and the normalization has already removed both, so compare these numbers against 1.00× and never divide by pool growth again.

<figure className="not-prose my-10 border border-stone-200 rounded-xl bg-white p-6">
  <p className="text-sm font-semibold text-stone-900 mb-1">Read share versus cited share, by source category</p>
  <p className="text-xs text-stone-500 leading-relaxed mb-4">Share ratios, 1.00× = held its share. The two bars diverge sharply for brand-owned pages and for social, because a site can gain in one and lose in the other.</p>
  <div className="flex flex-wrap gap-4 mb-4"><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#c15f3c"}} />Read share</span><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#8a3e21"}} />Cited share</span></div>
  <div className="overflow-x-auto">
<svg viewBox="0 0 1000 400" role="img" aria-label="Grouped bar chart of read share versus cited share across nine source categories. Brand-owned pages gain most in citations at 1.80 times, while editorial falls to 0.40 and review platforms to 0.31." className="w-full h-auto min-w-[700px]"> <line stroke="#e7e5e4" strokeWidth="1" x1="490" y1="44" x2="490" y2="368" /> <line stroke="#e7e5e4" strokeWidth="1" x1="790" y1="44" x2="790" y2="368" /> <line stroke="#e7e5e4" strokeWidth="1" x1="940" y1="44" x2="940" y2="368" /> <line stroke="#a8a29e" strokeWidth="1.5" x1="640" y1="40" x2="640" y2="372" /> <line stroke="#e7e5e4" strokeWidth="1" x1="340" y1="40" x2="340" y2="372" /> <text fontSize="11" fill="#78716c" x="340" y="34" textAnchor="middle">0</text> <text fontSize="11" fill="#78716c" x="490" y="34" textAnchor="middle">0.5×</text> <text fontSize="11" fill="#78716c" x="640" y="34" textAnchor="middle">1.0×</text> <text fontSize="11" fill="#78716c" x="790" y="34" textAnchor="middle">1.5×</text> <text fontSize="11" fill="#78716c" x="940" y="34" textAnchor="middle">2.0×</text> <text fontSize="11" fill="#78716c" x="326" y="68" textAnchor="end">Brand-owned</text> <rect x="340" y="56" width="285" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="68" width="540" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="633" y="65" fill="#a64e2a">0.95</text> <text fontSize="11" x="888" y="77" fill="#6f311a">1.80</text> <text fontSize="11" fill="#78716c" x="326" y="102" textAnchor="end">Institutional</text> <rect x="340" y="90" width="462" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="102" width="405" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="810" y="99" fill="#a64e2a">1.54</text> <text fontSize="11" x="753" y="111" fill="#6f311a">1.35</text> <text fontSize="11" fill="#78716c" x="326" y="136" textAnchor="end">Competitor pages</text> <rect x="340" y="124" width="342" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="136" width="327" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="690" y="133" fill="#a64e2a">1.14</text> <text fontSize="11" x="675" y="145" fill="#6f311a">1.09</text> <text fontSize="11" fill="#78716c" x="326" y="170" textAnchor="end">Third-party</text> <rect x="340" y="158" width="282" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="170" width="306" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="630" y="167" fill="#a64e2a">0.94</text> <text fontSize="11" x="654" y="179" fill="#6f311a">1.02</text> <text fontSize="11" fill="#78716c" x="326" y="204" textAnchor="end">Other</text> <rect x="340" y="192" width="225" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="204" width="246" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="573" y="201" fill="#a64e2a">0.75</text> <text fontSize="11" x="594" y="213" fill="#6f311a">0.82</text> <text fontSize="11" fill="#78716c" x="326" y="238" textAnchor="end">Social</text> <rect x="340" y="226" width="378" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="238" width="174" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="726" y="235" fill="#a64e2a">1.26</text> <text fontSize="11" x="522" y="247" fill="#6f311a">0.58</text> <text fontSize="11" fill="#78716c" x="326" y="272" textAnchor="end">Editorial</text> <rect x="340" y="260" width="192" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="272" width="120" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="540" y="269" fill="#a64e2a">0.64</text> <text fontSize="11" x="468" y="281" fill="#6f311a">0.40</text> <text fontSize="11" fill="#78716c" x="326" y="306" textAnchor="end">Review platforms</text> <rect x="340" y="294" width="219" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="306" width="93" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="567" y="303" fill="#a64e2a">0.73</text> <text fontSize="11" x="441" y="315" fill="#6f311a">0.31</text> <text fontSize="11" fill="#78716c" x="326" y="340" textAnchor="end">Forums</text> <rect x="340" y="328" width="243" height="10" rx="4" fill="#c15f3c" /> <rect x="340" y="340" width="63" height="10" rx="4" fill="#8a3e21" /> <text fontSize="11" x="591" y="337" fill="#a64e2a">0.81</text> <text fontSize="11" x="411" y="349" fill="#6f311a">0.21</text> <text fontSize="12" fill="#57534e" x="340" y="390">Fixed cohort · Aug 1–7 vs Aug 9–13 · share ratios, neutral = 1.00×</text> </svg>
  </div>
  <p className="mt-4 text-xs text-stone-500 leading-relaxed">The commercially important divergence: brand-owned pages barely gained reading share (0.95×) but gained citation share by 80% (1.80×). Editorial, review platforms and forums lost in both, and lost roughly twice as hard in citations as in reading.</p>
</figure>

<figure className="not-prose my-10 border border-stone-200 rounded-xl bg-white p-6">
  <p className="text-sm font-semibold text-stone-900 mb-1">Share change by individual site</p>
  <p className="text-xs text-stone-500 leading-relaxed mb-4">Share ratios, already normalized, so 1× is neutral. Log scale, meaning each step doubles or halves. Brand counts are shown so you can see no single brand&apos;s data sits behind a bar.</p>
  <div className="overflow-x-auto">
<svg viewBox="0 0 1000 640" role="img" aria-label="Diverging bar chart of share change by individual site on a log scale. US and EU regulators gain three to five times share, while techradar.com, legalclarity.org and forbes.com lose half or more." className="w-full h-auto min-w-[700px]"> <line stroke="#e7e5e4" strokeWidth="1" x1="364" y1="44" x2="364" y2="612" /> <line stroke="#e7e5e4" strokeWidth="1" x1="492" y1="44" x2="492" y2="612" /> <line stroke="#e7e5e4" strokeWidth="1" x1="748" y1="44" x2="748" y2="612" /> <line stroke="#e7e5e4" strokeWidth="1" x1="876" y1="44" x2="876" y2="612" /> <line stroke="#a8a29e" strokeWidth="1.5" x1="620" y1="40" x2="620" y2="616" /> <text fontSize="11" fill="#78716c" x="364" y="34" textAnchor="middle">0.25×</text> <text fontSize="11" fill="#78716c" x="492" y="34" textAnchor="middle">0.5×</text> <text fontSize="11" fill="#78716c" x="620" y="34" textAnchor="middle">1×</text> <text fontSize="11" fill="#78716c" x="748" y="34" textAnchor="middle">2×</text> <text fontSize="11" fill="#78716c" x="876" y="34" textAnchor="middle">4×</text> <text fontSize="11" fill="#78716c" x="290" y="64" textAnchor="end">fda.gov · 390 proj</text> <rect x="620" y="52" width="314.1" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="942" y="64" fill="#a64e2a">5.5×</text> <text fontSize="11" fill="#78716c" x="290" y="88" textAnchor="end">nist.gov · 409</text> <rect x="620" y="76" width="297.6" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="925" y="88" fill="#a64e2a">5.0×</text> <text fontSize="11" fill="#78716c" x="290" y="112" textAnchor="end">consumerfinance.gov · 205</text> <rect x="620" y="100" width="283.0" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="911" y="112" fill="#a64e2a">4.6×</text> <text fontSize="11" fill="#78716c" x="290" y="136" textAnchor="end">sec.gov · 541</text> <rect x="620" y="124" width="268.9" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="897" y="136" fill="#a64e2a">4.3×</text> <text fontSize="11" fill="#78716c" x="290" y="160" textAnchor="end">ftc.gov · 402</text> <rect x="620" y="148" width="265.5" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="893" y="160" fill="#a64e2a">4.2×</text> <text fontSize="11" fill="#78716c" x="290" y="184" textAnchor="end">justia.com · 664</text> <rect x="620" y="172" width="258.7" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="886" y="184" fill="#a64e2a">4.1×</text> <text fontSize="11" fill="#78716c" x="290" y="208" textAnchor="end">europa.eu · 656</text> <rect x="620" y="196" width="256.9" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="884" y="208" fill="#a64e2a">4.0×</text> <text fontSize="11" fill="#78716c" x="290" y="232" textAnchor="end">irs.gov · 264</text> <rect x="620" y="220" width="235.0" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="863" y="232" fill="#a64e2a">3.6×</text> <text fontSize="11" fill="#78716c" x="290" y="256" textAnchor="end">nhs.uk · 556</text> <rect x="620" y="244" width="148.1" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="776" y="256" fill="#a64e2a">2.2×</text> <text fontSize="11" fill="#78716c" x="290" y="280" textAnchor="end">gov.uk · 940</text> <rect x="620" y="268" width="84.5" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="712" y="280" fill="#a64e2a">1.6×</text> <text fontSize="11" fill="#78716c" x="290" y="304" textAnchor="end">nih.gov · 1,302</text> <rect x="620" y="292" width="36.7" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="664" y="304" fill="#a64e2a">1.2×</text> <text fontSize="11" fill="#78716c" x="290" y="328" textAnchor="end">linkedin.com · 2,106</text> <rect x="620" y="316" width="22.5" height="12" rx="4" fill="#c15f3c" /> <text fontSize="11" x="650" y="328" fill="#a64e2a">1.1×</text> <text fontSize="11" fill="#78716c" x="290" y="352" textAnchor="end">trustpilot.com · 1,579</text> <rect x="604.6" y="340" width="15.4" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="596" y="352" textAnchor="end" fill="#78716c">0.92×</text> <text fontSize="11" fill="#78716c" x="290" y="376" textAnchor="end">clutch.co · 698</text> <rect x="596.4" y="364" width="23.6" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="588" y="376" textAnchor="end" fill="#78716c">0.88×</text> <text fontSize="11" fill="#78716c" x="290" y="400" textAnchor="end">reddit.com · 2,561</text> <rect x="576.5" y="388" width="43.5" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="568" y="400" textAnchor="end" fill="#78716c">0.79×</text> <text fontSize="11" fill="#78716c" x="290" y="424" textAnchor="end">g2.com · 936</text> <rect x="571.8" y="412" width="48.2" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="563" y="424" textAnchor="end" fill="#78716c">0.77×</text> <text fontSize="11" fill="#78716c" x="290" y="448" textAnchor="end">sciencedirect.com · 1,433</text> <rect x="548.8" y="436" width="71.2" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="540" y="448" textAnchor="end" fill="#78716c">0.68×</text> <text fontSize="11" fill="#78716c" x="290" y="472" textAnchor="end">tripadvisor.com · 524</text> <rect x="534.6" y="460" width="85.4" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="526" y="472" textAnchor="end" fill="#78716c">0.63×</text> <text fontSize="11" fill="#78716c" x="290" y="496" textAnchor="end">wikipedia.org · 1,913</text> <rect x="512.9" y="484" width="107.1" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="504" y="496" textAnchor="end" fill="#78716c">0.56×</text> <text fontSize="11" fill="#78716c" x="290" y="520" textAnchor="end">service.gov.uk · 852</text> <rect x="488.3" y="508" width="131.7" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="480" y="520" textAnchor="end" fill="#78716c">0.49×</text> <text fontSize="11" fill="#78716c" x="290" y="544" textAnchor="end">forbes.com · 1,474</text> <rect x="480.6" y="532" width="139.4" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="472" y="544" textAnchor="end" fill="#78716c">0.47×</text> <text fontSize="11" fill="#78716c" x="290" y="568" textAnchor="end">legalclarity.org · 1,180</text> <rect x="459.7" y="556" width="160.3" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="451" y="568" textAnchor="end" fill="#78716c">0.42×</text> <text fontSize="11" fill="#78716c" x="290" y="592" textAnchor="end">techradar.com · 953</text> <rect x="378.2" y="580" width="241.8" height="12" rx="4" fill="#a8a29e" /> <text fontSize="11" x="370" y="592" textAnchor="end" fill="#78716c">0.27×</text> <text fontSize="12" fill="#57534e" x="290" y="630">Fixed cohort · Aug 1–7 vs Aug 9–13 · 150+ brands and 30,000+ reads per site</text> </svg>
  </div>
  <p className="mt-4 text-xs text-stone-500 leading-relaxed">Every site here is computed on one method: fixed brand cohort, same two windows, share-normalized. Sites with larger declines exist (healthline.com at 0.22×, ~28,000 reads across 501 brands) but fall below the volume floor and are excluded rather than shown unqualified.</p>
</figure>

### Where ChatGPT aims its domain-targeted searches

**The named targets are review and reputation platforms.** ChatGPT interrogates them by name: reddit.com (1,657 brands), trustpilot.com (1,166), gov.uk (650), bbb.org (340), g2.com (295), clutch.co (219).

**But the biggest single target is the brand's own domain.** 12.2% of all `site:` queries point there, 113,122 of 927,875 over nine days, rising to 14.6% on a looser subdomain match.

**Both things are true at once.** Platforms rank individually because they're shared across thousands of brands; own-domain targets fragment across thousands of distinct domains and never chart.

## Does ChatGPT know the brands already, or find them first?

**Why the order of the queries matters.** If ChatGPT issues `site:yourbrand.com` queries, maybe the brand set is decided in advance from what the model already believes and the searching is just confirmation. If so, retrievability matters far less than being baked into the weights.

**What the sequence actually shows.** Across 175,098 answers containing a `site:` query, the dominant shape is one broad query first, then named-domain drilling.

<div className="my-10">

</div>

**The usual path is discover, then verify.** See who's in the field, then interrogate those domains by name. Good news for retrievability: the brands being checked largely surfaced in a search first.

**The 8.9% that skips discovery.** ~15,500 answers whose *first* action is querying a named brand's domain with zero prior retrieval. Those names can't have come from results, because there were none. A "knows first" mode exists. It just isn't the main one.

### What the query sequence cannot tell us

For the other 91%, we can't tell where the drilled domain came from: the first query's results, or the model's priors. There's no sub-query-to-source link in the data, so the two are indistinguishable. That's the question that decides AEO strategy, and we can't close it with what we collect today. Whether being remembered or being retrievable determines who gets checked stays open, so we claim no more than the sequence shows.

## More brands get cited, and the leader takes a bigger share

Two things happened at once. They sound contradictory until you look at the denominator. Across 930 brands with enough citations to rank in both windows:

| Per brand, competitor pages cited inline | Before | After | Change |
| --- | ---: | ---: | ---: |
| Distinct brands cited | 28.66 | 35.05 | +22% |
| Total citations | 73.6 | 137.0 | +86% |
| Top brand's share of them | 19.3% | 21.7% | +12% |
| Concentration (HHI) | 0.102 | 0.117 | +15% |

The pie nearly doubled and about six more brands got a slice of each tracked brand's answers, but the leader's slice grew faster than the field widened. The door opened wider, and whoever was already in front gained more.

### Citation rank churn is real, and far smaller than it first looks

**Our first cut looked spectacular.** Only 2 of the top 5 cited brands survived, and 72% of brands had a new number one.

**Almost all of it is an artifact of small lists.** These are low-count lists with many near-ties, so the top five churns on its own. Comparing two windows that both sit before the change shows the baseline.

<figure className="not-prose my-10 border border-stone-200 rounded-xl bg-white p-6">
  <p className="text-sm font-semibold text-stone-900 mb-1">Leaderboard churn against a null baseline</p>
  <p className="text-xs text-stone-500 leading-relaxed mb-4">Higher bars mean more stability. The null compares two pre-change windows (Aug 1–3 vs Aug 5–7); the test compares across the change (Aug 5–7 vs Aug 9–11). Equal window lengths, same 347 brands throughout.</p>
  <div className="flex flex-wrap gap-4 mb-4"><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#d6d3d1"}} />Null (both windows pre-change)</span><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#c15f3c"}} />Test (across Aug 8)</span></div>
  <div className="overflow-x-auto">
<svg viewBox="0 0 1000 190" role="img" aria-label="Grouped bar chart comparing leaderboard stability. Top-five retention falls from 43.1% in the null baseline to 31.4% across the change, and same-brand-at-number-one falls from 37.5% to 22.8%." className="w-full h-auto min-w-[700px]"> <line stroke="#e7e5e4" strokeWidth="1" x1="420" y1="40" x2="420" y2="160" /> <line stroke="#e7e5e4" strokeWidth="1" x1="540" y1="40" x2="540" y2="160" /> <line stroke="#e7e5e4" strokeWidth="1" x1="660" y1="40" x2="660" y2="160" /> <line stroke="#e7e5e4" strokeWidth="1" x1="780" y1="40" x2="780" y2="160" /> <line stroke="#e7e5e4" strokeWidth="1" x1="900" y1="40" x2="900" y2="160" /> <line stroke="#a8a29e" strokeWidth="1.5" x1="300" y1="40" x2="300" y2="160" /> <text fontSize="11" fill="#78716c" x="300" y="32" textAnchor="middle">0</text> <text fontSize="11" fill="#78716c" x="540" y="32" textAnchor="middle">20%</text> <text fontSize="11" fill="#78716c" x="780" y="32" textAnchor="middle">40%</text> <text fontSize="11" fill="#78716c" x="286" y="70" textAnchor="end">Top-5 brands retained</text> <rect x="300" y="58" width="517.2" height="10" rx="4" fill="#d6d3d1" /> <rect x="300" y="70" width="376.8" height="10" rx="4" fill="#c15f3c" /> <text fontSize="11" x="825" y="67" fill="#57534e">43.1%</text> <text fontSize="11" x="685" y="79" fill="#a64e2a">31.4%</text> <text fontSize="11" fill="#78716c" x="286" y="120" textAnchor="end">Same brand at number one</text> <rect x="300" y="108" width="450" height="10" rx="4" fill="#d6d3d1" /> <rect x="300" y="120" width="273.6" height="10" rx="4" fill="#c15f3c" /> <text fontSize="11" x="758" y="117" fill="#57534e">37.5%</text> <text fontSize="11" x="582" y="129" fill="#a64e2a">22.8%</text> <text fontSize="12" fill="#57534e" x="300" y="178">Stability of the top of the citation leaderboard between adjacent windows</text> </svg>
  </div>
  <p className="mt-4 text-xs text-stone-500 leading-relaxed">Even with nothing changing, 57% of the top five turns over between adjacent windows and the leader changes 62% of the time. The change adds roughly 12 points of churn: directionally real, modest, and invisible without the baseline.</p>
</figure>

### Own-domain citations rose for 85.9% of brands

The aggregate figure, brand-owned pages gaining 80% citation share, could have been a handful of brands dragging a mean. It isn't. Across 1,665 brands with 100 or more answers in both windows:

<div className="my-10">

</div>

## Reddit fell off a cliff in ChatGPT answers on August 14

**A separate discontinuity, six days later.** Reddit went from 12.6% of ChatGPT answers to 1.7% in ~48 hours and has stayed at the floor. Total sources per answer held at 18.5, so it isn't a general contraction.

**Reddit alone, out of every comparable source.** Every other UGC and review platform is flat or up over the same days. LinkedIn +54%, Facebook +125%, YouTube +58%, with Trustpilot, G2, Wikipedia and TripAdvisor unchanged. A "downweight UGC" policy would have hit all of them.

**ChatGPT kept asking; Reddit stopped answering.** Requests mentioning Reddit fell 25%; Reddit pages actually read fell 87%. Yield per request fell to about a sixth of what it was. That asymmetry is an access cutoff, not a ranking change.

<figure className="not-prose my-10 border border-stone-200 rounded-xl bg-white p-6">
  <p className="text-sm font-semibold text-stone-900 mb-1">ChatGPT kept asking for Reddit. Reddit stopped arriving.</p>
  <p className="text-xs text-stone-500 leading-relaxed mb-4">Both series indexed to August 8 = 100 so they share one scale.</p>
  <div className="flex flex-wrap gap-4 mb-4"><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#c15f3c"}} />Reddit requests in fan-out</span><span className="inline-flex items-center gap-2 text-xs text-stone-500"><span className="inline-block w-4 h-[3px] rounded-sm" style={{background:"#a8a29e"}} />Reddit pages actually read</span></div>
  <div className="overflow-x-auto">
<svg viewBox="0 0 1000 310" role="img" aria-label="Line chart indexed to August 8 equals 100. Reddit requests in the fan-out stay near 75 while Reddit pages actually read fall to 13." className="w-full h-auto min-w-[700px]"> <line stroke="#e7e5e4" strokeWidth="1" x1="80" y1="260" x2="960" y2="260" /> <line stroke="#e7e5e4" strokeWidth="1" x1="80" y1="205" x2="960" y2="205" /> <line stroke="#e7e5e4" strokeWidth="1" x1="80" y1="150" x2="960" y2="150" /> <line stroke="#e7e5e4" strokeWidth="1" x1="80" y1="95" x2="960" y2="95" /> <text fontSize="11" fill="#78716c" x="62" y="264" textAnchor="end">0</text> <text fontSize="11" fill="#78716c" x="62" y="209" textAnchor="end">40</text> <text fontSize="11" fill="#78716c" x="62" y="154" textAnchor="end">80</text> <text fontSize="11" fill="#78716c" x="62" y="99" textAnchor="end">120</text> <polyline fill="none" stroke="#c15f3c" strokeWidth="2" strokeLinejoin="round" strokeLinecap="round" points="80,122.5 171,122.9 262,131.0 353,147.8 444,146.4 536,138.9 627,157.0 718,143.8 809,157.0 900,157.0" /> <polyline fill="none" stroke="#a8a29e" strokeWidth="2" strokeLinejoin="round" strokeLinecap="round" points="80,122.5 171,78.9 262,52.8 353,110.4 444,175.3 536,166.1 627,210.9 718,240.6 809,242.0 900,241.6" /> <circle cx="900" cy="157.0" r="5" fill="#c15f3c" stroke="#ffffff" strokeWidth="2" /> <circle cx="900" cy="241.6" r="5" fill="#a8a29e" stroke="#ffffff" strokeWidth="2" /> <text fontSize="11.5" x="912" y="152" fill="#a64e2a">75</text> <text fontSize="11.5" x="912" y="246" fill="#78716c">13</text> <text fontSize="11" fill="#78716c" x="80" y="286" textAnchor="middle">Aug 8</text> <text fontSize="11" fill="#78716c" x="353" y="286" textAnchor="middle">Aug 11</text> <text fontSize="11" fill="#78716c" x="627" y="286" textAnchor="middle">Aug 14</text> <text fontSize="11" fill="#78716c" x="900" y="286" textAnchor="middle">Aug 17</text> <text fontSize="12" fill="#57534e" x="80" y="305">Indexed, Aug 8 = 100 · fixed brand cohort</text> </svg>
  </div>
  <p className="mt-4 text-xs text-stone-500 leading-relaxed">Requests −25%, yield −87%. Reddit is still the domain ChatGPT names most often in its own searches, and it now returns almost nothing.</p>
</figure>

### One caveat to keep attached to the Reddit finding

**Magnitude varies by collection provider.** On Aug 15 one saw Reddit in 2.18% of answers and another in 5.49%, having agreed within a few points before Aug 14. arXiv shows a similar shape on the same days.

**Direction and timing agree everywhere.** Treat 12.6% → 1.7% as our best estimate and expect the exact figure to move, and don't build a claim about any named commercial arrangement on top of it.

## What the August 8 change means for brands

## Method: how we measured this

- **Population.** All ChatGPT responses across 5,000+ tracked brands, August 1–17, 2026, ~300k responses/day. Comparison windows are Aug 1–7 versus Aug 9–13, skipping the Aug 8 transition day and ending before the Aug 14 Reddit event.
- **Fixed cohort.** Site and category figures use only brands with responses on all 17 days (~131k responses/day). The raw daily brand count swings substantially from one day to the next, so without this, changes in which brands ran would masquerade as model behavior.
- **Paired prompt test.** The headline 11.58 → 22.54 comes from 266,182 prompt strings that ran in both windows with three or more responses each, so it's immune to prompt-mix drift. Median paired ratio 1.64×; 81.6% of individual prompts increased; 56% rose by half or more. The effect runs across the whole population.
- **Share ratios are pre-normalized.** Every ratio in the category tables and both charts already divides by pool growth (1.82× read, 1.68× cited), so 1.00× is neutral. Only ever compare them against 1.00×.
- **Chrome excluded.** About a quarter of raw citation rows are interface assets: a favicon service, image CDNs, product photos, map-widget legal links. All excluded. Including them inflates every per-answer figure, and it did on our first pass.
- **Sources versus citations.** Reported separately throughout, because they move differently and the distinction reverses which category wins.
- **Null baselines on anything ranked.** Leaderboard churn is quoted only against a same-length pre-change comparison, because the top of these lists turns over heavily by itself. Without that control the raw figure reads as a 72% reshuffle when the true effect is about 12 points. We'll hold any future rank claim in this series to the same standard.
- **Paired-brand floors applied symmetrically.** Concentration and variety figures use only brands clearing the volume floor in both windows. Applying the floor per window instead admitted 1,481 brands after against 1,004 before and reversed the variety result, because the later period clears a citation floor more easily by construction.
- **Cross-engine control on answer length.** Paired-prompt length change over the same window: ChatGPT +5.1% median, AI Overviews +4.7%, Gemini +6.9%, Copilot −1.5%, Perplexity −34.5%. ChatGPT is not distinctive, so answer length is not used as evidence of a ChatGPT-specific change. AI Mode's headline +43% was a single 12,048-character day and is excluded as noise.
- **Answer body versus research panel.** Inline citations are extracted from the response text, while source lists come from the research disclosure panel. Findings are labeled by which one they rest on, because only the first is immune to the disclosure question.
- **Robustness.** The depth increase reproduces on two independent collection providers with separate infrastructure (1.9× and 1.45×). Provider identity is not otherwise a reported dimension. The API/gateway route is ~2% of ChatGPT volume and is not used as a control.

---

[Back to Blog](https://www.searchable.com/blog) | [Searchable Homepage](https://www.searchable.com)
