Proof
Every claim below names where it was measured. Two entries record our own mistakes, because a vendor who only shows wins is showing you a filter.
Measured 2026-07-25 — AE page_renders, SUM(_sample_interval), account 1842ebb3, window 2026-06-13..2026-07-02 (19 metered days — the meter has written nothing since; see meter_status). Ask us to re-run it in front of you.
A customer arrived through ChatGPT on day six
reclaimedwoodmillworkco.com launched and, six days later, took a phone call from someone who had asked an AI assistant for a supplier. None of our AI-visibility features were switched on at the time. That is the wedge: answer engines read real content, so they cannot be gamed — they can only be earned.
Source: tenant report, corroborated by the customer call
96.7% of your traffic is machines. You pay for the other 3.3%.
Across the network over 19 metered days (13 June – 2 July 2026): 1,900,813 renders, 1,838,216 of them robots, 62,597 of them people. Billed: $625.97. Every agency in the country charges you a flat retainer whether the visitor was a person or a crawler.
Source: AE page_renders, SUM(_sample_interval), account 1842ebb3, window 2026-06-13..2026-07-02 (19 metered days — the meter has written nothing since; see meter_status)
Blank pages still pulled 8.8% of all human traffic
Before we fixed the renderer, 93 of our flagship tenant's city pages were serving fourteen words of content. They still drew 1,675 human visits — 8.8% of that tenant's entire human traffic. The demand for local pages is not theoretical. We measured it while failing to serve it.
Source: derived: blank_city_human_hits / all tenant-22 human hits
We caught ourselves shipping a million empty URLs — and stopped it with code
An audit found our own flagship site one DNS change away from publishing 1,045,463 thin URLs to Google. We did not write a warning in a document. We wrote a gate that exits with an error and refuses the deploy. The demand filter cut it to 4,078 pages that had actually earned traffic. We would rather show you that story than pretend it never happened.
Source: tools/preflight.mjs, 13/13 pass on the current build
Our own history verifies, and you can check it
5,494 consecutive rows of production history verify under sha256(content + previous hash). Current head: 1a4940b4af689f1a…. The recipe is published. Recompute it yourself.
Source: seal row 13 (session7b-ai-drift-and-fact-gate), tools/seal.mjs --verify => {ok:13,checked:13,allValid:true}