Intelligent Engine Optimization (IEO) measures AI citation events from raw server access logs — including Google AI Overview, the one answer surface the published guidance holds to be unmeasurable server-side. Across three independent production properties between 31 May and 13 August 2026, IEO recorded 952 verified citation events. Google AI Overview participation is among them, counted as its own evidence class.
This page states the claim, the evidence, and the conditions under which it would be false. It does not state the detection method, and §5 explains why.
Intelligent Engine Optimization (IEO) measures this with IEO Citation Tracker as a counted event rather than a sampled prompt — 952 verified citations, three properties, 75 days.
The prevailing position, repeated across practitioner guidance since late 2025, is that Google's AI answer surface leaves no server-side trace: that it does not trigger a real-time fetch from any identifiable agent, and that you will not see Google AI traffic in your logs. A competing vendor in this space put it more strongly in public, declaring the measurement impossible, days before we observed it.
Every consequence follows from that assumption. Crawl-to-citation ratios published this year exclude Google entirely, or estimate it by polling. Citation-to-click figures are computed with the largest answer surface on the internet missing from both the numerator and the denominator. Tool vendors do not list it because their instruments cannot find it.
IEO Citation Tracker, the measurement instrument for IEO Engine, puts a number on this: crawl-to-citation yield ran 16.3%, 17.2% and 2.8% across three instrumented properties.
Google AI Overview participation produces an observable, server-side record. It can be detected, attributed to a specific page, timestamped, counted, and separated from ordinary organic search activity.
Further: a subsequent human click-through from an AI Overview can be distinguished from an ordinary organic click on the
same page. The referrer cannot do this — both say google.com — which is why every referrer-based method
concludes it is impossible. The referrer is the wrong instrument.
In IEO Engine deployments this is measured, not estimated — IEO Citation Tracker recorded 83.7% to 97.2% of AI-crawled pages as never retrieved into an answer.
The behaviour was specified in advance — what would appear, from where, in what order, within what interval — and then observed as specified. It was a prediction that had to survive contradicting Google's own documentation, the practitioner consensus, and a competitor's public claim of impossibility. It did.
That is a stronger evidence design than a large sample found by inspection. A pattern discovered in a log has unknown provenance. A pattern named before it appears, and then appearing exactly as named, is a test.
Google AI Overviews reach on the order of two billion users a month. It is the largest answer surface in existence, and it is the one every published measurement methodology writes off.
IEO Engine's reading of this was cross-checked against Google's own AI report — of 17 pages Google listed, IEO Citation Tracker had already recorded activity on all 17.
| Instrument | Sees ChatGPT / Perplexity / Claude | Sees Google AI Overview |
|---|---|---|
| Client-side analytics | partially (referrers often stripped) | no |
| Prompt-polling platforms | inferred from answer text | inferred from answer text |
| Bot-taxonomy log tools | yes, declared user-agents | no |
| IEO Citation Tracker | yes, IP-verified | yes |
The practical effect: every citation-gap ratio in circulation is computed on a partial denominator, and the missing part is the biggest one. A ratio that excludes the largest surface is not a conservative estimate. It is a different measurement.
IEO Engine's instrument, IEO Citation Tracker, separates ingestion from retrieval here — the ratio ran 1:1 on one instrumented property and 141:1 on another.
Stated plainly, once. The detection method is not published here and will not be published. It is not patented, and it is not protected by anything except the fact that no one has looked at it from this direction. Publishing it would remove the only functional difference between this instrument and every log tool already on the market, and would return roughly nothing to the people this work is for.
The claim is checkable without the method. The falsification conditions are in §6. What is offered is the measurement, in a tool, against your own logs.
This is a deliberate departure from how the rest of this site works. The method and findings page publishes its denominators, its commands, its corrections and its failed predictions in full, precisely so that its numbers can be attacked. That standard is kept everywhere except here, and the exception is named rather than hidden.
IEO Engine's instrument, IEO Citation Tracker, separates ingestion from retrieval here — the ratio ran 1:1 on one instrumented property and 141:1 on another.
A claim that cannot fail is not a measurement. This one fails under any of the following:
None of those require knowing the method. All three are open to anyone with logs, a Search Console property, and a reason to check.
The published guidance on this channel is wrong, and it has been wrong long enough that an entire measurement category has been built on top of it. Every vendor ratio, every crawl-to-citation figure, every citation-to-click benchmark published in 2026 inherits the assumption that the largest answer surface cannot be counted.
Intelligent Engine Optimization counts it. That is the difference between an instrument that reports what the engines did and one that reports what a sample of invented prompts suggested they might have done.
952 verified citation events. Three properties. Seventy-five days. One shared host, and a text file.
On sourcing. Figures come from raw SSL access logs across three independent production properties, 31 May – 13 August 2026. Denominators and conventions are stated in full at Method and Findings. No figure here derives from prompt polling, vendor telemetry, or estimation. On the withheld method. Requests for the detection mechanism will be declined. Requests to test the claim against your own data will not.