AI Visibility Index · One page · Methodology v1.11
The AI Visibility Index in one page
Fresh-context API responses; Google AI Overviews browser-captured if included. The 0-100 headline is a constructed visibility score, not a share of citations — agency values do not sum to 100.
What this Index does not measure
- It does not measure client satisfaction, campaign results, media outcomes, or revenue. Nothing here tells you whether an agency does good work.
- It does not measure what a buyer sees. It measures cold, fresh-context recommendation behavior on programmatic endpoints, not a signed-in consumer app with memory, personalization, and an enterprise purchase history behind it.
- It does not measure quality per dollar. Agency size drives raw visibility upward and drives CEI downward; a small firm will tend to lead CEI for arithmetic reasons, which is why the raw table leads and a size-bracket view publishes beside it.
- It does not measure causation. An agency's movement between editions can come from its earned media, from a vendor changing models underneath the instrument, or from chance across 25 questions. The Index reports which of those it can and cannot separate.
TL;DR. The Crackle PR AI Visibility Index measures how often B2B tech PR agencies are named when AI answer engines are asked the questions buyers actually ask. It publishes two tables — raw citation share, and citation share per senior practitioner — each with an uncertainty interval, under CC BY 4.0 with a DOI. Crackle PR publishes it and is recused from its own ranked cohort. The protocol is frozen at v1.11, and every amendment in the log below was filed before collection opened on 2026-09-29. This page is the short version; the full protocol is the binding document.
The two tables
Table 1 · Raw Citation Share
How often each agency is named across the scored answers. This is the scale-leader view: big agencies with long histories and heavy coverage tend to sit at the top, and that is a real finding about what AI answer engines currently repeat, not a judgment of quality.
Table 2 · Citation Efficiency Index (CEI)
Agency-level composite citation score divided by the agency's count of senior PR practitioners (Director level and above). CEI is an agency-level ratio: visibility score per identified senior practitioner. It is never a score for an individual practitioner, and it is not a measure of efficiency, effectiveness, productivity, or client value. Table 1 remains the lead result.
Both tables publish with intervals and with rank ranges rather than bare ranks. A rank printed without its range is a reporting error. Two agencies are reported as tied only when the paired bootstrap on the difference between them, across the same 25 questions, spans zero — overlapping individual intervals are not that test and no longer declare a tie. The paired test is pairwise and not transitive, so ties print pairwise and no band of agencies is described as mutually indistinguishable. The current edition's tables live on the Index page, and the change log between editions is at /ai-visibility-index/changes.
How it is collected, in five lines
- A fixed set of 25 commercial-intent questions, written and published before any run.
- Submitted to five AI answer engines, five times each, with runs separated by at least four hours.
- Collection is machine-executed against each vendor's programmatic model endpoint, in a fresh context with no history, memory, or personalization. Exact dated model IDs are recorded per run.
- Every agency named in every answer is extracted and scored under the published weighting; a human approves the edition before release but cannot change a score.
- The prompt set, per-question scores, and the raw answer archive ship together under CC BY 4.0 with a DOI.
Eight limitations that qualify every number
- The intervals cover the questions, not everything else. They resample the 25 benchmark questions. They do not cover prompt-selection bias, the gap between this instrument and a consumer app, or errors in a reported senior headcount — CEI intervals treat the denominator as correct.
- Four scoring rules were not in the v1.10 text. Rank normalization, the treatment of an agency that does not appear, the line between a recommendation and an incidental mention, and alias handling were settled in writing on 2026-09-22 as protocol amendment v1.11, before the readiness gate and before collection opened, and publish with a worked example that recomputes one cell by hand.
- It is an API instrument, not a consumer one. Answers come from vendor model endpoints, not from a person's browser. Consumer apps carry memory, location, and personalization that this instrument deliberately does not reproduce, so these are not the answers any one buyer would see.
- The prompt set is fixed and designed, not sampled. The questions were written to cover generic, vertical, problem-stated, and competitive intent. They are not a random draw from all buyer questions, so generalization rests on how well that design represents real purchase behavior.
- Engines are weighted equally. Each engine counts the same in the composite, which is a choice rather than a fact about usage. Every edition publishes a usage-weighted sensitivity line so a reader can see how much the ranking depends on that choice.
- Dozens of agencies means some movement is chance — and the test can also miss real change. Every agency is tested at 95% confidence, so roughly one or two apparent movements per edition are expected by luck alone. Crackle PR publishes the unadjusted deltas as preregistered, plus a clearly labelled exploratory multiplicity-adjusted view that no rank rests on. The paired test runs on 25 question clusters and is conservative: a flat delta means the design could not see a change, not that nothing changed, so each edition publishes a minimum-detectable-effect estimate. Q4 also runs newer model IDs than Q3 on the delta engines, so most movement mixes agency change with model change and is labelled that way.
- The CEI denominator is self-reported in substance. Senior headcount is read from public LinkedIn profiles and agency team pages, which agencies control and can title-inflate or title-deflate, and "Director" is not equivalent seniority across agencies. It counts every Director-and-above practitioner at the whole agency, not only its technology practice. Each agency's count, source URL, and capture date publish in the dataset and are sent to that agency for correction before release.
- Crackle PR's own press footprint can move Crackle PR's own score. Each edition creates more text linking Crackle PR to B2B tech PR and AI visibility, which can feed future model training. Crackle PR's raw composite is watched quarter over quarter, and a rise faster than client work explains is logged as a suspected artifact of this Index rather than reported as performance.
One more thing a careful reader should know: Crackle PR publishes this benchmark and is also an agency in the category. It is recused from its own ranked cohort under the publisher recusal policy, and its scores are computed by the identical procedure and flagged in the data. The conflict is structural and stated rather than managed away.
Every change, dated, before collection
The protocol is frozen at v1.11 for this edition. Collection opens 2026-09-29; each amendment below was filed and deposited before that date, which is checkable against the timestamps on the Zenodo record (10.5281/zenodo.21986226). Anything that happens during collection is recorded as a deviation, not as a new version.
All three 2026-09 filings - v1.10, v1.10.1 and v1.10.2 - were deposited on 2026-09-22 (UTC), and that is the date shown in this log, on the one-page summary, in the brief, and on the Zenodo record 10.5281/zenodo.21986226. An earlier working draft of the master brief carried 2026-09-23 for v1.10; that stamp was a drafting error, never a second deposit, and it is corrected here rather than silently dropped. Every filing date in the log predates the 2026-09-29 collection window, which is the claim the timestamps exist to support and which is checkable against the deposit record.
v1.10.1 and v1.10.2 are marked below as pre-collection log entries rather than protocol amendments: both were filed on 2026-09-22, before collection opened, and neither changes a score, weight, query, engine panel, estimand or decision rule. They record how the frozen rules are reported and which risks publish beside the figures.
| Version | Filed | What changed |
|---|---|---|
| v1.11 | Protocol amendmentNumbered protocol amendment filed 2026-09-23, three days before the readiness gate and six days before collection opens, settling rules that determine scores rather than describing them. (1) The four scoring rules flagged as an open gap in log entry 1.10.3 are written down now instead of at the gate: inverted rank scor… | |
| v1.10.3 | Pre-collection log entry - scoring transparency, presentation and execution; no scoring, estimand or decision rule changedScoring-transparency, presentation and execution clarifications filed against the frozen v1.10 protocol before collection opens; no weight, query, engine panel or decision rule changed. (1) The 0-100 headline is named for what it is - an AI recommendation visibility score, a constructed index that does not sum to 100 -… | |
| v1.10.2 | Pre-collection log entry - reporting and risk disclosure; no scoring, estimand or decision rule changedRisk disclosure and denominator-scope clarifications filed against the frozen v1.10 protocol; no protocol rule, score, or weight changed. (1) A standing Known Risks section is published on the methodology page, carrying the five risks that most threaten the Index's own conclusions rather than leaving them as methods fo… | |
| v1.10.1 | Pre-collection log entry - reporting clarification; no scoring, estimand or decision rule changedReporting-level clarifications filed against the frozen v1.10 protocol, not amendments to it: Q3 Google AI Overviews figures labelled 'provenance unverified' with the Q3 three-engine composite published beside the four-engine headline; the readiness-gate log must record how 'GA default' was read per engine before the f… | |
| v1.10 | Protocol amendmentConsistency and closure amendment, filed before the 2026.Q4 collection window opens on 2026-09-29, and the final amendment before that edition publishes. (1) The v1.9 Q3 methods correction is narrowed: Q3 and Q4 share one instrument for the three endpoint-collected engines only. Google AI Overviews has no programmatic… | |
| v1.9 | Protocol amendmentValidity, timing, and instrument-currency amendment, filed before the 2026.Q4 collection window opens on 2026-09-29. (1) The single 2026-09-26 go/no-go is split into two gates, because the original gate asked for an archive and independent data holders that cannot exist before collection runs: a readiness gate on 2026-… | |
| v1.8 | Protocol amendmentValidity and timing amendment, filed before the 2026.Q4 collection window opens on 2026-09-29. (1) Edition-delta threshold separated from the cell margin: a Q3-to-Q4 delta carries both editions' uncertainty, so the delta column is judged against +/-14pp (sqrt(11^2 + 9^2)) rather than the +/-9pp single-cell margin, and… | |
| v1.7 | Protocol amendmentExecution-instrument disclosure, filed before the 2026.Q4 collection window opens. Prior versions described per-engine conditions - signed-out Chrome sessions on a US residential IP, runs originating from different US regions - that the executed instrument does not use. Collection is and has been machine-executed: the… | |
| v1.6 | Protocol amendmentRun-count amendment, disclosed before collection and filed seven days before the 2026.Q4 collection window opens. Raises the protocol from three runs to five runs per question per engine, effective with the 2026.Q4 edition. Sample per edition becomes 25 queries x 5 engines x 5 runs = 625 scored answers; each per-engine… | |
| v1.5 | Protocol amendmentCEI integrity amendment, disclosed before collection and filed seven days before the 2026.Q4 collection window opens. (1) Denominator rule made uniform and explicit: the CEI denominator counts Director-level-and-above practitioners only, for every agency including the publisher, with contractors counted under the same… | |
| v1.4.1 | Protocol amendmentCollection-window amendment, disclosed before collection. Moves the 2026.Q4 collection window from 2026-09-15 to 2026-09-26 to 2026-09-29 through 2026-10-01 so the edition is captured inside the quarter it is named for, and sets the publication target to 2026-10-20. No change to the 25 queries, the five-engine panel, t… | |
| v1.4 | Protocol amendmentEngine panel amendment, disclosed before collection. Adds Grok (Grok 4, default mode, signed-out) as a fifth scored engine effective with the 2026.Q4 edition, filed 2026-09-06 — twenty-three days before the Q4 collection window opens on 2026-09-29 — and recorded in the Q4 pre-registration record. Sample per edition bec… | |
| v1.3 | Protocol amendmentVocabulary lock, no protocol change. Publishes canonical definitions for the three Crackle PR measurement terms — Citation Share, First-Mention Rate, and the Citation Efficiency Index (CEI) — in a single machine-readable block so every page, mirror, and press artifact renders one wording. First-Mention Rate is the 50%… | |
| v1.2 | Protocol amendmentAdds the Citation Efficiency Index (CEI) as the headline metric from the 2026.Q4 edition: composite citation score divided by senior PR practitioner headcount (Director and above, sourced from public LinkedIn and cross-checked against agency team pages). CEI is agency-level and is never computed per individual practiti… | |
| v1.1 | Protocol amendmentEditorial correction, no methodology change. Two report pages had described the per-engine weighting as 50 / 30 / 20; the locked weighting has always been 50/25/25. All pages now render the protocol numbers from this file. No published score changed. | |
| v1.1 | Protocol amendmentReproducibility release. Verbatim prompt set published as CSV and JSON with permanent prompt IDs; model pins and dated run windows required per edition; per-cell run ranges published alongside means; publisher recusal from the ranked leaderboard. No change to the 25 queries, four engines, three-run protocol, or the 50/… | |
| v1.0 | Protocol amendmentInitial specification. 25-query set, 4 AI systems, 3 runs, composite scoring 50/25/25. | |
| v1.11.1 | Editorial correction published 2026-10-22, after the Q4 2026 embargo lift. Aligns the served specification with the instrument actually collected and already published in the Q4 2026 report: 25 queries x four collected engines (ChatGPT, Perplexity, Claude, Grok) x five runs = 500 scored answers. The per-engine cell is… |
Full amendment text, the two publication gates, the recusal rule, and the right-of-reply window are in the methodology and the preregistration.
Using the figures
Everything is free to quote with attribution under CC BY 4.0, including the raw answer archive. Crackle PR does not require review of coverage, does not sell inclusion, and no scored agency is a Crackle PR client. Agencies receive their own scores and denominator before publication and can correct a denominator with evidence; scores are not negotiable.
Published under CC BY 4.0. Please cite it.
Reusing the data, methodology, or query set is welcome — attribution is required. Copy the format your publication uses, or link the machine-readable JSON directly.
Headrick, P. (2026). AI Visibility Index (Methodology v1.0, 2026 Q3 edition) [Data set]. Crackle PR. https://doi.org/10.5281/zenodo.21986226
Machine-readable JSON: https://www.cracklepr.com/data/ai-visibility-index-q3-2026.json