The story
What a citation actually is
An AI system reads a page, and later some of what it read turns up inside an answer. We can measure the first half of that sentence exactly. We cannot see the second half at all, and neither can any other website.
Across 91 days, that first half has happened about 479 times a day.
Room 02 of 10
The two ladders
Two questions that sound the same and are not
The first ladder asks how much of our work AI systems took. The second asks how much of it came back as a person. Both are measurable on our own logs. Neither of them is the question most people mean when they say "citation", and that third question is the one nobody outside an AI company can answer.
Ladder one — what they took
In plain words
A machine belonging to a named AI company asked our server for a page, and our server sent it. We know the date, the agent, the page, the status and the byte count, because we wrote them down as it happened.
Precisely
43,596 served reads across 2 Jun 2026 to 9 Aug 2026, under the rule set out in The Numbers. Every one is a row in our own log, not an estimate and not a sample.
Ladder two — what came back
In plain words
Later, somebody arrived on the site and their browser said they had come from an AI answer surface. That is a person, and we can count them.
Precisely
771 sessions across 10 May 2026 to 9 Aug 2026 carried a referrer identifying a named AI surface. That is the only population on this instrument described as people, because it is the only one with evidence for it.
The evidence ladder
From a signpost to a token
Five stages, each requiring strictly more proof than the one before it. The last stage has issued nothing, and that is reported as plainly as the stages that have.
| Stage | What happened | Count | What proves it |
|---|---|---|---|
| 01 | The signposts we put up | 26,806 | Rows in the published anchor file. This is what we offered, not what anyone took. |
| 02 | Requests at a citation surface | 89,932 | One log row per request, whatever the outcome. |
| 03 | The material actually reached them | 43,596 | Status 200 or 206 with bytes above zero, withdrawn agent excluded. |
| 04 | Something came back carrying the trace | 23,967 | A later request carrying the trace of an earlier offer, at strong match confidence. |
| 05 | A citation token was issued | 0 | Nothing has been issued. The gate has never opened, and this counter grows only on proof. |
Sources: the anchor index, the citation table, the followback table and the mint. Freshness: Live.
Microsoft publishes, for sites it has data on, how often they are named inside AI answers. That figure is generated inside the answer engine, and no amount of server logging will reproduce it. When we say we cannot measure citations, this is precisely what we mean: we can measure the reading, and we can measure the arriving, and the naming in between belongs to somebody else's telemetry.
This instrument therefore never claims a citation count. It claims served reads, and it claims arrivals, and it keeps the two apart.
What the words mean
One word, one meaning
Ambiguity is fixed by definition, never by deletion. Four different figures were once all called "successful" on this page. Each now has a name that only it can carry.
| Term | What it means here | What it does not mean |
|---|---|---|
| Logged attempt | A request arrived at a citation surface and we wrote a row. | That anything was sent back. |
| Served read | Content left our server: 200 or 206, bytes above zero, agent in credit. | That anyone read it, or that we were named anywhere. |
| Withdrawn from credit | Served, recorded, visible, but excluded from totals and rankings. | Deleted, hidden, or never served. |
| Door knock | A recorded request at a registered machine entry point. | A citation, or a person. |
| Followback | A later request carrying the trace of an earlier offer. | A purchase, or a named citation. |
| Session referred by an AI surface | A browser arrived and its referrer named an AI answer surface. | That the AI recommended us, only that the link was followed. |
| Recorded session | A row in the session table, of any kind. | A human being. See The Humans for why. |
| Citation token | A minted, verifiable record that our material was used. | Anything issued so far. The count is zero. |
| Our own probe | Traffic we generated ourselves to verify a surface answers. | Demand. It is subtracted wherever demand is reported. |
These definitions are used identically in every room and in every JSON mirror.
The correction
What we got wrong
An instrument that cannot admit its own miscalibration cannot be trusted about anything else. Every correction we have published is listed in The Workings; the one that changed the most is here.
Corrected 8 August 2026: the tracker was writing down status codes it had guessed, not the ones the server returned. Until today the function that recorded the outcome of a request derived the status code from the shape of the URL rather than reading the real response, and that guess overrode reality. Requests that were actually refused were filed as successfully served.
This mattered because the served-read rule selects on status code. A refused request recorded as a 200 passes that filter, so every affected row was counted as a citation. 16,475 rows in the citation table are affected: they are attempts by an agent that was already being refused at the server, recorded as though we had served them. On the strength of those rows a blocked crawler ranked first by read volume on this instrument.
The tracker now records the status the server actually returned, and the guess survives only as a fallback where no real status is available. The historic rows have not been rewritten, because silently editing a log to make a past claim true is a worse fault than the one it fixes. They remain in the table, they remain visible in The Machines, and they are excluded from every total on this instrument by the withdrawn-from-credit rule. Read counts published before today are therefore overstated, and totals spanning 8 August 2026 are not comparable across it.
Corrected 7 August 2026: until today this page was a static file frozen on 19 June 2026, with live figures injected into it by pattern substitution. When a pattern stopped matching, the June number stayed on the page and looked exactly like a live one. Four such figures were found. The page is now generated from the database on every request, and the substitution layer has been removed entirely.
Corrected 7 August 2026: a single figure was previously presented as "successful" in four different places, meaning four different things. Each of those figures now has its own name, set out in the table above.
