teas.co.uk
Tea and coffee, from everyday bags to speciality
Room 03 of 07 · agents and arrivals
Who read us.
Every named machine agent this instrument has recorded, what each was actually sent, and the browser sessions that arrived afterwards from AI answer surfaces.
An agent name is a user-agent claim, not a verified organisation. What protects the figures is behaviour: an agent that breaks the published rules is withdrawn from credit with its history kept visible.
12 NAMED AGENTS0 AGENTS WITHDRAWN FROM CREDIT0 AI-REFERRED SESSIONS0.6 GB SENT TO MACHINES
Section 01
Every named agent, and what each was sent.
One row per agent, every column from the same table and the same window, so the row sums are meaningful. Byte counts are the content actually shipped, not page counts. Amazonbot's row is kept in full and credited nothing.
| Agent | Attempts | Served | No content | Days seen | Anchors | Data sent (MB) | Last seen |
|---|---|---|---|---|---|---|---|
| meta-externalagent | 1,019 | 1,017 | 2 | 2 | 517 | 287.2 | 2 Oct |
| gptbot | 916 | 904 | 12 | 7 | 906 | 162.2 | 4 Oct |
| claudebot | 321 | 313 | 8 | 4 | 320 | 91.1 | 4 Oct |
| bingbot | 155 | 154 | 1 | 9 | 128 | 59.0 | 4 Oct |
| oai-searchbot | 15 | 10 | 5 | 3 | 15 | 3.5 | 1 Oct |
| chatgpt-user | 9 | 4 | 5 | 6 | 9 | 3.0 | 4 Oct |
| perplexitybot | 6 | 1 | 5 | 3 | 5 | 3.0 | 1 Oct |
| google-extended | 4 | 1 | 3 | 3 | 4 | 2.4 | 1 Oct |
| youbot | 4 | 0 | 4 | 3 | 4 | 1.2 | 1 Oct |
| mistral | 3 | 0 | 3 | 2 | 3 | 0.9 | 30 Sep |
| bytespider | 2 | 0 | 2 | 2 | 2 | 0.6 | 30 Sep |
| ccbot | 1 | 0 | 1 | 1 | 1 | 0.0 | 27 Sep |
The 12 agents together: 2,455 attempts, 2,404 served, 0.6 GB sent.Served here counts the raw rule (status + bytes); the credited study figure of 2,404 additionally removes the withdrawn agent.
Source: wp_crisps_citations grouped by agent - window: 26 Sep 2026 to 4 Oct 2026 - bytes are SUM(bytes_served) - live.
The coverage cross-check - this instrument against the raw access loguntil 7 Aug 2026 capture was gated to AI surfaces, so the raw log sees far more; both are published so the shortfall can be measured
| Agent | Recorded by this instrument | Recorded in the raw access log | Coverage |
|---|---|---|---|
| meta-externalagent | 1,019 | 93,113 | 1.1% |
| gptbot | 916 | 91,267 | 1.0% |
| amazonbot | 0 | 27,856 | 0.0% |
| claudebot | 321 | 10,164 | 3.2% |
| chatgpt-user | 9 | 8,921 | 0.1% |
| oai-searchbot | 15 | 8,848 | 0.2% |
| googleother | 0 | 4,338 | 0.0% |
| bytespider | 2 | 3,016 | 0.1% |
| perplexitybot | 6 | 2,270 | 0.3% |
| google-extended | 4 | 22 | 18.2% |
Across the frozen log: 3,432,235 requests in total, of which 250,590 were named AI crawlers, 146,034 Googlebot and 21,801 bingbot.Instrument counts are live; the log column is a frozen 7 Aug 2026 reference. A ratio above 100% means capture has outgrown that frozen day.
Section 02
The sessions that actually arrived.
From an AI answer to this shop
AI-referred sessions0
Pages viewed in them0
Product views0
Baskets started0
Checkouts started0
Completed orders0
Each step is its own evidence class, never derived from the step above. The order count is published because it is the truth.
Strong-match followbacks
7
lifetime · 7 in the last 7 days
A later request that returned to the exact anchor it was offered, at the strictest match confidence. The strongest evidence our own logs can hold that a read had anywhere to land — still not proof our name appeared in an answer.
Candidate rows examined2,455
Matched to an offer7
Matched probably0
Source: wp_crisps_sessions (26 Sep 2026 to 4 Oct 2026) and the followback table (26 Sep 2026 to 4 Oct 2026) - two tables, no shared key, never summed - live.
Section 03
Where the arrivals came from.
| Referring surface | Sessions | Pages viewed | Product pages |
|---|
AI-referred sessions only; the surface label is the recorded referrer class.
Why most recorded sessions are never called human: the session table classifies every row it has ever written as human, so that label cannot be earned from it. Of 1,821 recorded sessions, the overwhelming majority are desktop, one-page visits from scraping floods — recorded across 47 country codes and published as bot pressure, not readership. That is why this room ranks nothing by raw session count and treats only the AI-referred subset as separately evidenced.
Section 04
What was sent, and when.
The same source table across rolling and calendar windows. They overlap, so they must never be added. API reads are a subset of machine reads, not a count of completed tool operations.
Machine traffic: month, fortnight and last 24 hours
Comparison unavailable. A successful background source snapshot has not been published.
Keep reading
Where this leads next.
One study, one style, seven rooms. The legacy room addresses now land on the room that absorbed their content, and every machine mirror keeps its original path.
What they read
The doors those agents knocked on, the probe-share honesty split and what came back.
Open the record →
The mint & leaderboard
What these reads earn: the board, the classes and the run records behind them.
Open the record →
traffic/data.md
The dated machine-read windows as a markdown twin, for machines.
Open the record →