Skip to content
🎁 CURATED IN TUNBRIDGE WELLS 🚚 Free UK delivery on orders over £35 📮 Royal Mail Tracked, same-day dispatch before 2pm Monday to Friday 💳 Gift cards from £10, sent by email or printable 📦 Tea of the Month Club, curator-picked box every month 🏢 B2B accounts: bulk pricing, invoices, multi-pack ★ 100 reward points welcome bonus when you sign up

The evidence

Every claim, with the working shown

Day by day, the returns that carried a trace, the images taken, and the traffic we refused. Where the capture behind a figure is incomplete, the figure is published as a floor and labelled as one.

Across 91 days that is about 479 served reads a day.

Room 05 of 10

23,967 strong followbacks
4,785 distinct images taken

Day by day

The last fortnight, one row a day

Nothing smoothed and nothing rolled up. Each row is one calendar day of citation-surface activity, counted from the same table under the same rule as every other figure on this instrument.

Citation-surface activity, one row per calendar day
DayAttemptsServedDistinct agentsDistinct anchors
Sun 9 Aug 20261641498135
Sat 8 Aug 20261,6791,60310958
Fri 7 Aug 20266596179512
Thu 6 Aug 20263222917261
Wed 5 Aug 20265915569520
Tue 4 Aug 20262,7202,68491,935
Mon 3 Aug 20261,3201,28710915
Sun 2 Aug 20261,6831,574111,205
Sat 1 Aug 20261,8631,753171,148
Fri 31 Jul 20262,0551,962111,277
Thu 30 Jul 20261,8951,835101,020
Wed 29 Jul 20261,06599210837
Tue 28 Jul 20261,1551,1199774
Mon 27 Jul 20261,8181,549111,271
Sun 26 Jul 20261,00294410644
This table sums to 18,915

Source: the citation table. Window: the last fourteen days to 9 Aug 2026. Rule: served means status 200 or 206 with bytes above zero, withdrawn agent excluded. Freshness: Live. Today is a partial day and is shown as such.

Followback proof

When something came back

A followback is a later request that still carries the trace of an earlier offer. It is the strongest evidence available on our own logs that a read led anywhere, and it is still not evidence that we were named in an answer.

The followback ladder — rows recorded, and how confidently each was matched
Stage2 Aug to 9 AugLifetimeWhat it means
Rows recorded13,210106,507Every candidate examined, matched or not.
Matched to an offer2,84924,597A trace tied the later request to an earlier offer at some confidence.
Matched strongly2,73023,967The strictest match confidence. This is the only followback figure quoted elsewhere.
Matched probably936Consistent with a match but not conclusive. Never counted as proof.
Matched weakly110594A partial signal only. Published for completeness and used for nothing.
Unmatched10,36181,910No offer could be tied to the request. The largest group, and shown as such.
These rows use different windows and do not sum — the first two rows are totals of the rows beneath them, not additional entries. Strong, probable, weak and unmatched sum to rows recorded: 106,507 lifetime.

Source: the followback table. Windows: the last seven days to 9 Aug 2026, and the lifetime of the table. Freshness: Live.

The image library

The pictures they took

Two tables on this site record byte counts and only one of them records images. Image figures come from the asset-knock table, whose rows are image files. The door-knock table records the bytes of whole pages, and adding the two together would produce a much larger image figure that is simply false.

Why the two byte columns are never summed. The asset-knock table records image files: its paths end in .jpg and .webp, and the recorded byte count is the image itself. The door-knock table records the weight of a whole HTML route. Of its 176,602 byte-bearing product rows, 4 are image URLs. Summing the two columns would attribute the weight of every page to pictures and multiply the image figure many times over, so the larger number is not published as an image total anywhere on this instrument.

Image capture is intermittent, so every figure in this section is a floor rather than a count. The asset-knock table spans 63 days but holds rows on only 13 of them. There is a gap between 20 June and 1 August 2026 during which nothing was recorded at all. Figures below therefore understate what was taken, by an amount we cannot quantify.

6,699Image requests by named agentsA floor. Capture ran on 13 days only.Asset-knock table · 8 Jun 2026 to 9 Aug 2026 · Requests whose agent class is a named AI or search crawler · Live
282.9Megabytes of images sent (MB)Corrected 7 August 2026: megabyte figures on the previous page were baked into a static file on 19 June and had stopped updating.Asset-knock table, recorded byte counts · 8 Jun 2026 to 9 Aug 2026 · Bytes sent on requests answered 200 or 206, named AI and search crawlers only · Live
4,785Distinct images takenAsset-knock table · 8 Jun 2026 to 9 Aug 2026 · Distinct normalised image paths, named AI and search crawlers only · Live
10,117.9Megabytes taken by unidentified crawlers (MB)Shown separately and never folded into the AI figures, because we cannot say who took it.Asset-knock table · 8 Jun 2026 to 9 Aug 2026 · Requests whose agent could not be resolved to a named AI or search crawler · Live
Images taken, by named agent
AgentRequestsData sent (MB)Distinct imagesDays captured
gptbot2,31371.72,3126
claudebot1,885175.71,82212
googlebot97756.691813
bingbot48747.529213
meta-externalagent46014.02667
oai-searchbot2953.829511
perplexitybot22016.81996
googleother470.9444
duckduckbot70.355
applebot40.143
bingpreview30.031
duckassistbot10.011
This table sums to 6,699

Source: the asset-knock table. Window: 8 Jun 2026 to 9 Aug 2026. Freshness: Live, and incomplete — see the warning above.

Every day on which image capture recorded anything at all
DayRequestsData sent (MB)
Sun 9 Aug 202650322.8
Sat 8 Aug 20261,84577.3
Fri 7 Aug 202641622.0
Thu 6 Aug 20261,442124.0
Sat 1 Aug 202650.1
Sun 28 Jun 202610.1
Sat 20 Jun 20262,753176.8
Fri 19 Jun 20261,768713.0
Thu 18 Jun 202642618.0
Wed 17 Jun 2026145166.0
Tue 16 Jun 20265637161.2
Mon 15 Jun 202640317.6
Sun 14 Jun 20263119.0
Sat 13 Jun 202674727.6
Fri 12 Jun 202662522.9
Thu 11 Jun 202646615.6
Wed 10 Jun 202661220.5
Tue 9 Jun 20262,5551007.7
Mon 8 Jun 2026251903.3
This table sums to 15,837

Source: the asset-knock table, all agent classes. This table is published in full precisely because the gaps in it are the point: the days missing between 20 June and 1 August 2026 recorded nothing.

Denied

What we did not serve

Requests that got something other than content. A refusal is as much a fact about this site as a delivery, and an instrument that only published its successes would not be an instrument.

Every outcome recorded at a citation surface
StatusWhat that meansRequests
200Content sent69,103
noneNo status recorded16,161
404No matching route4,553
301Moved permanently54
400Bad request49
302Found, redirected18
401Authentication required5
500Server error4
405Method not allowed3
403Refused2
This table sums to 89,952 of 89,932 · every logged attempt has exactly one outcome

Source: the citation table. Window: 2 Jun 2026 to 9 Aug 2026. Freshness: Live. The "no status recorded" row is 16,161 requests we logged but whose response we did not capture; they are excluded from served reads rather than assumed either way.

Every outcome recorded at a machine entry point
StatusWhat that meansRequests
200Content sent565,716
301Moved permanently127,874
404No matching route52,729
403Refused20,215
429Rate limited2,476
400Bad request1,989
302Found, redirected1,397
500Server error663
304Other377
401Authentication required327
503Other75
405Method not allowed16
This table sums to 773,854 of 773,448 · every door knock has exactly one outcome

Source: the door-knock table. Window: 10 May 2026 to 9 Aug 2026. Freshness: Live. Door knocks were recorded only against AI surfaces until 7 August 2026, so figures spanning that date are not comparable across it.