Crawl Presence Registry Dataset

Before any AI trains on the open web, a crawler has to have kept a copy. This dataset is the standing record of what the open crawl actually holds about our company — collection by collection, capture by capture, era by era — and the robots posture, recorded as our owner’s decision, under which that crawling happens. “The corpus knows us” is a query result here, not an impression.

The standing registry of the training/research-corpora element for The Flat Rate Movers: every Common Crawl collection’s recorded answer for this domain — captures classified by URL class and content era, with the query state and method on every collection — the recorded robots posture under which crawling happens (owner decision, 2026-10-31: Option 1, open training), the signed signal-observation log that proves what the estate’s robots file said and when, and the element’s gap records P1–P6 each with its designed solution. Query it three ways: the full JSON file; ?table= on the API route; and the ?table= form of /v1/datasets for the estate inventory.

One JSON file: 129 collections · 16197 capture rows · 14822 with status 200 · current-estate captures: 0 · 17 robots agent groups (7 training, 9 retrieval) · 6 gaps (2 resolved). Generated from a live sweep of the Common Crawl index by the Flat Rate Machine — never hand-kept.

Download datasets-crawl-presence.json API: /v1/crawl-presence

What this dataset contains

NodeContents
Collections129 Common Crawl collections, each with its query state, the verbatim query method, attempts and observed crawl window
Crawl Presence (capture rows)16197 captures with URL, timestamp, status, WARC digest, computed URL class and computed content era
Presence SummaryPer collection × URL class counts and 200-counts; per-era and per-class totals — the dilution curve and the sampling mix as data
Robots PolicyThe owner’s recorded posture decision (Option 1, open training, 2026-10-31), the per-agent table, and the served-vs-source drift gate
Signal ObservationsThe signed, hash-chained log of preference signals as served — first entry: the robots.txt of 2026-10-31
Filter InspectionsEmpty by design — rows exist only from inspected WET records (first inspection: batch E5-B4)
Corpus Release ChecksNot-checked by design — rows are added only when a real downstream-release check runs
Gap Records P1–P6Every gap with its evidence, its impact and its designed solution
Mechanism PinsThe verified mechanism facts the posture decision rests on, each with its source
Registry TotalsCounts by query state, era, class and purpose — computed at generation
Scope and RulesThe vocabulary, the era/class computation rules, and the no-invention boundaries

The headline finding: a zero that is a fact

Every collection Common Crawl has published to date was crawled before our current site existed — the estate cut over on October 28, 2026, and the newest collection in the index predates it. So the current estate is present in zero collections, and everything the crawl holds about this domain — 16197 captures across 129 collections — describes predecessor sites: the WordPress site that ran until the cutover, the Wix-era site before it, and earlier forms. Each capture row carries its content era, computed from its timestamp against the cutover and its URL form, never hand-tagged; 0 rows are flagged for era review because their form contradicts their timestamp. The first collection crawled after the cutover is the current estate’s corpus debut, and this registry is the instrument standing watch for it (gap P1, resolving in batch E5-B2).

Content eraCapturesStatus 200
current-estate00
pre-cutover-wordpress1477513724
wix-era448369
earlier-predecessor974729
URL classCapturesStatus 200
page46514054
dataset-file00
llms00
graph00
index44
robots223192
taxonomy1131910572
other00

Every collection, with its recorded answer

The seed sweep of October 31, 2026 queried every collection in Common Crawl’s index for this domain, 2026 series first, under a retry discipline. A collection that returned captures is queried-clean; one whose index could not be read after all retries stands as unverifiable-index-error — a visible state, never a silent zero (gap P6). Capture windows are read from this domain’s own rows; where a domain returned no captures, no window is derivable and none is invented.

CollectionQuery stateCapturesStatus 200Window observed for this domain
CC-MAIN-2026-43queried-clean9052322026-10-11T07:49:50Z → 2026-10-18T01:24:29Z
CC-MAIN-2026-39queried-clean3622026-09-09T09:06:24Z → 2026-09-15T21:50:23Z
CC-MAIN-2026-34queried-clean1402026-08-09T18:47:59Z → 2026-08-14T06:35:46Z
CC-MAIN-2026-30queried-clean00— → —
CC-MAIN-2026-25queried-clean2102026-06-08T10:36:27Z → 2026-06-17T07:04:38Z
CC-MAIN-2026-21queried-clean1402026-05-14T09:35:33Z → 2026-05-15T07:47:55Z
CC-MAIN-2026-17queried-clean00— → —
CC-MAIN-2026-12queried-clean222026-03-07T20:25:07Z → 2026-03-09T20:28:15Z
CC-MAIN-2026-08queried-clean332026-02-13T23:16:34Z → 2026-02-18T11:09:42Z
CC-MAIN-2026-04queried-clean222026-01-17T15:17:06Z → 2026-01-22T21:39:50Z
CC-MAIN-2025-51queried-clean2612612025-12-08T09:26:48Z → 2025-12-14T12:48:15Z
CC-MAIN-2025-47queried-clean5245232025-11-08T20:56:38Z → 2025-11-09T17:13:15Z
CC-MAIN-2025-43queried-clean6796782025-10-12T07:04:19Z → 2025-10-17T08:40:58Z
CC-MAIN-2025-38queried-clean6926882025-09-06T18:46:33Z → 2025-09-15T13:44:29Z
CC-MAIN-2025-33queried-clean7567502025-08-04T02:21:35Z → 2025-08-15T06:47:26Z
CC-MAIN-2025-30queried-clean3923882025-07-10T06:35:08Z → 2025-07-15T07:51:11Z
CC-MAIN-2025-26queried-clean7637592025-06-12T14:34:18Z → 2025-06-22T16:11:43Z
CC-MAIN-2025-21queried-clean8117822025-05-14T03:57:19Z → 2025-05-24T23:28:34Z
CC-MAIN-2025-18queried-clean8468382025-04-18T05:53:47Z → 2025-04-30T18:02:55Z
CC-MAIN-2025-13queried-clean8007902025-03-23T19:40:10Z → 2025-03-28T16:49:38Z
CC-MAIN-2025-08queried-clean5555522025-02-11T17:11:36Z → 2025-02-18T05:09:24Z
CC-MAIN-2025-05queried-clean6836812025-01-13T15:40:33Z → 2025-01-21T02:54:14Z
CC-MAIN-2024-51queried-clean4204192024-12-03T04:19:49Z → 2024-12-10T15:57:52Z
CC-MAIN-2024-46queried-clean6025932024-11-03T08:45:10Z → 2024-11-11T15:16:26Z
CC-MAIN-2024-42queried-clean6806662024-10-06T12:26:52Z → 2024-10-15T10:44:34Z
CC-MAIN-2024-38queried-clean7917782024-09-09T07:20:18Z → 2024-09-19T05:38:21Z
CC-MAIN-2024-33queried-clean5675552024-08-10T06:22:36Z → 2024-08-15T06:52:34Z
CC-MAIN-2024-30queried-clean3723582024-07-13T21:25:43Z → 2024-07-21T05:08:22Z
CC-MAIN-2024-26queried-clean2031792024-06-14T17:38:49Z → 2024-06-24T14:32:25Z
CC-MAIN-2024-22queried-clean5264952024-05-23T14:28:47Z → 2024-05-27T07:40:24Z
CC-MAIN-2024-18queried-clean115311262024-04-13T08:35:03Z → 2024-04-25T12:13:02Z
CC-MAIN-2024-10queried-clean1401252024-03-04T10:17:23Z → 2024-03-04T12:56:43Z
CC-MAIN-2023-50queried-clean1261142023-12-03T06:29:34Z → 2023-12-06T08:31:43Z
CC-MAIN-2023-40queried-clean1171002023-09-27T00:36:05Z → 2023-09-27T03:01:28Z
CC-MAIN-2023-23queried-clean107962023-06-02T07:25:55Z → 2023-06-02T09:50:58Z
CC-MAIN-2023-14queried-clean68612023-03-24T08:25:11Z → 2023-03-24T11:00:44Z
CC-MAIN-2023-06queried-clean60502023-02-01T18:04:04Z → 2023-02-08T01:19:34Z
CC-MAIN-2022-49queried-clean106922022-12-03T21:24:08Z → 2022-12-05T12:29:41Z
CC-MAIN-2022-40queried-clean39312022-10-05T17:24:28Z → 2022-10-05T19:35:52Z
CC-MAIN-2022-33queried-clean41322022-08-09T12:49:49Z → 2022-08-09T15:04:38Z
CC-MAIN-2022-27queried-clean62552022-07-07T00:28:35Z → 2022-07-07T02:51:43Z
CC-MAIN-2022-21queried-clean1982022-05-23T22:48:29Z → 2022-05-24T01:17:31Z
CC-MAIN-2022-05queried-clean95722022-01-28T07:43:41Z → 2022-01-28T09:31:38Z
CC-MAIN-2021-49queried-clean16102021-11-27T04:38:08Z → 2021-11-27T06:28:08Z
CC-MAIN-2021-43queried-clean23152021-10-18T00:23:36Z → 2021-10-18T02:46:25Z
CC-MAIN-2021-39queried-clean26232021-09-25T23:36:22Z → 2021-09-26T01:23:12Z
CC-MAIN-2021-31queried-clean32282021-07-29T04:34:59Z → 2021-07-29T06:58:11Z
CC-MAIN-2021-25queried-clean35192021-06-16T12:51:24Z → 2021-06-16T15:09:11Z
CC-MAIN-2021-21queried-clean27142021-05-15T22:43:33Z → 2021-05-16T00:46:32Z
CC-MAIN-2021-17queried-clean64452021-04-18T10:37:56Z → 2021-04-18T12:29:25Z
CC-MAIN-2021-10queried-clean24172021-03-02T03:46:05Z → 2021-03-02T05:39:50Z
CC-MAIN-2021-04queried-clean81502021-01-21T18:22:48Z → 2021-01-27T21:05:40Z
CC-MAIN-2020-50queried-clean752020-11-25T21:33:09Z → 2020-11-25T23:02:17Z
CC-MAIN-2020-45queried-clean862020-10-23T20:51:51Z → 2020-10-23T22:28:00Z
CC-MAIN-2020-40queried-clean32182020-09-26T10:30:24Z → 2020-09-26T13:24:42Z
CC-MAIN-2020-34queried-clean32152020-08-15T03:55:50Z → 2020-08-15T05:47:45Z
CC-MAIN-2020-29queried-clean73322020-07-10T17:57:24Z → 2020-07-11T21:27:59Z
CC-MAIN-2020-24queried-clean2052020-05-31T05:43:20Z → 2020-05-31T08:34:27Z
CC-MAIN-2020-16queried-clean332020-03-30T05:45:46Z → 2020-03-30T06:38:51Z
CC-MAIN-2020-10queried-clean43432020-02-25T04:57:24Z → 2020-02-25T07:17:38Z
CC-MAIN-2020-05queried-clean66642020-01-23T13:13:24Z → 2020-01-26T19:09:18Z
CC-MAIN-2019-51queried-clean58582019-12-13T02:04:37Z → 2019-12-14T10:51:08Z
CC-MAIN-2019-47queried-clean30302019-11-12T00:24:55Z → 2019-11-12T02:10:05Z
CC-MAIN-2019-43queried-clean48482019-10-14T11:26:16Z → 2019-10-14T11:57:30Z
CC-MAIN-2019-39queried-clean1082019-09-18T12:29:46Z → 2019-09-18T12:31:13Z
CC-MAIN-2019-35queried-clean40372019-08-18T11:57:47Z → 2019-08-18T12:03:08Z
CC-MAIN-2019-30queried-clean16162019-07-21T15:49:29Z → 2019-07-21T15:51:52Z
CC-MAIN-2019-26queried-clean25252019-06-16T16:03:01Z → 2019-06-16T16:07:01Z
CC-MAIN-2019-22queried-clean662019-05-20T07:16:43Z → 2019-05-20T07:17:38Z
CC-MAIN-2019-18queried-clean27272019-04-24T15:00:34Z → 2019-04-24T15:04:21Z
CC-MAIN-2019-13queried-clean552019-03-19T06:39:47Z → 2019-03-19T06:39:59Z
CC-MAIN-2019-09queried-clean33292019-02-17T06:46:05Z → 2019-02-22T21:25:53Z
CC-MAIN-2019-04queried-clean332019-01-21T19:01:22Z → 2019-01-21T19:01:30Z
CC-MAIN-2018-51queried-clean34282018-12-09T20:27:47Z → 2018-12-11T10:11:57Z
CC-MAIN-2018-47queried-clean832018-11-17T22:08:22Z → 2018-11-21T00:37:48Z
CC-MAIN-2018-43queried-clean1282018-10-21T23:57:31Z → 2018-10-23T14:56:01Z
CC-MAIN-2018-39queried-clean222018-09-20T01:42:38Z → 2018-09-20T01:42:39Z
CC-MAIN-2018-34queried-clean1882018-08-16T14:12:15Z → 2018-08-17T01:09:37Z
CC-MAIN-2018-30queried-clean622018-07-20T17:45:19Z → 2018-07-20T19:42:30Z
CC-MAIN-2018-26queried-clean1082018-06-20T16:36:19Z → 2018-06-24T22:36:48Z
CC-MAIN-2018-22queried-clean642018-05-23T08:33:23Z → 2018-05-26T00:38:52Z
CC-MAIN-2018-17queried-clean972018-04-23T21:31:42Z → 2018-04-26T21:05:16Z
CC-MAIN-2018-13queried-clean422018-03-20T07:26:36Z → 2018-03-20T07:26:36Z
CC-MAIN-2018-09queried-clean1082018-02-21T05:21:07Z → 2018-02-21T18:37:10Z
CC-MAIN-2018-05queried-clean00— → —
CC-MAIN-2017-51queried-clean662017-12-13T19:00:32Z → 2017-12-13T19:00:50Z
CC-MAIN-2017-47queried-clean00— → —
CC-MAIN-2017-43queried-clean1082017-10-18T03:57:40Z → 2017-10-22T07:57:07Z
CC-MAIN-2017-39queried-clean00— → —
CC-MAIN-2017-34queried-clean662017-08-21T08:04:36Z → 2017-08-21T08:07:15Z
CC-MAIN-2017-30queried-clean212017-07-22T04:37:15Z → 2017-07-22T04:37:16Z
CC-MAIN-2017-26queried-clean222017-06-27T05:06:47Z → 2017-06-27T05:06:47Z
CC-MAIN-2017-22queried-clean00— → —
CC-MAIN-2017-17queried-clean00— → —
CC-MAIN-2017-13queried-clean222017-03-30T00:37:37Z → 2017-03-30T00:37:38Z
CC-MAIN-2017-09queried-clean322017-02-21T00:34:24Z → 2017-02-21T00:34:25Z
CC-MAIN-2017-04queried-clean222017-01-19T10:39:05Z → 2017-01-19T10:39:05Z
CC-MAIN-2016-50queried-clean222016-12-06T00:49:22Z → 2016-12-06T00:49:23Z
CC-MAIN-2016-44queried-clean442016-10-20T19:27:24Z → 2016-10-21T20:02:26Z
CC-MAIN-2016-40queried-clean442016-09-25T17:35:54Z → 2016-09-26T08:56:49Z
CC-MAIN-2016-36queried-clean752016-08-25T00:53:31Z → 2016-08-27T09:47:31Z
CC-MAIN-2016-30queried-clean222016-07-25T13:56:08Z → 2016-07-28T00:50:41Z
CC-MAIN-2016-26queried-clean222016-06-25T15:59:55Z → 2016-07-01T08:06:21Z
CC-MAIN-2016-22queried-clean112016-05-28T17:56:56Z → 2016-05-28T17:56:56Z
CC-MAIN-2016-18queried-clean222016-05-02T21:17:23Z → 2016-05-05T06:37:54Z
CC-MAIN-2016-07queried-clean222016-02-07T17:07:46Z → 2016-02-12T11:57:00Z
CC-MAIN-2015-48queried-clean222015-11-28T04:00:07Z → 2015-11-29T15:50:00Z
CC-MAIN-2015-40queried-clean222015-10-04T21:14:46Z → 2015-10-05T03:57:35Z
CC-MAIN-2015-35queried-clean222015-08-31T17:39:49Z → 2015-09-02T12:44:42Z
CC-MAIN-2015-32queried-clean222015-07-30T00:02:05Z → 2015-07-30T06:03:37Z
CC-MAIN-2015-27queried-clean222015-06-30T14:12:18Z → 2015-07-05T17:40:50Z
CC-MAIN-2015-22queried-clean222015-05-30T20:20:43Z → 2015-05-30T22:19:47Z
CC-MAIN-2015-18queried-clean222015-04-21T02:54:45Z → 2015-04-28T10:19:06Z
CC-MAIN-2015-14queried-clean112015-03-27T19:03:40Z → 2015-03-27T19:03:40Z
CC-MAIN-2015-11queried-clean202015-03-03T00:31:53Z → 2015-03-05T11:51:22Z
CC-MAIN-2015-06queried-clean202015-01-28T06:31:49Z → 2015-01-31T06:59:58Z
CC-MAIN-2014-52queried-clean222014-12-18T12:24:07Z → 2014-12-28T21:31:26Z
CC-MAIN-2014-49queried-clean442014-11-23T05:31:22Z → 2014-11-28T22:35:19Z
CC-MAIN-2014-42queried-clean662014-10-20T22:43:38Z → 2014-11-01T06:31:43Z
CC-MAIN-2014-41queried-clean332014-09-21T10:05:23Z → 2014-10-01T08:10:33Z
CC-MAIN-2014-35queried-clean442014-08-22T13:43:28Z → 2014-09-02T18:46:52Z
CC-MAIN-2014-23queried-clean442014-07-22T17:25:51Z → 2014-07-29T02:32:56Z
CC-MAIN-2014-15queried-clean442014-04-17T19:05:35Z → 2014-04-24T21:52:35Z
CC-MAIN-2014-10queried-clean222014-03-07T17:49:36Z → 2014-03-10T08:42:41Z
CC-MAIN-2013-48queried-clean222013-12-11T10:08:51Z → 2013-12-12T04:59:45Z
CC-MAIN-2013-20queried-clean222013-05-21T15:52:41Z → 2013-05-22T05:27:43Z
CC-MAIN-2012queried-clean112012-05-23T08:23:59Z → 2012-05-23T08:23:59Z
CC-MAIN-2009-2010queried-clean00— → —
CC-MAIN-2008-2009queried-clean00— → —

The robots posture — a recorded decision

Our robots.txt posture is not an accident of a default file. On October 31, 2026 the owner decided it: Option 1 — open training, made deliberate (Dossier 05 §4, gap P3). Option 1 changes no file: the live robots.txt stands exactly as served. What changed is that the decision is now recorded here with the file’s digest, and two gates keep the record and the file in lockstep — this dataset’s generator refuses to build if the served file’s digest ever differs from the deployed source, and the estate’s verification suite re-checks the recorded decision against the live file on every run.

Decision
Option 1 — open training (decided by the owner, 2026-10-31); file change: none
Served file
https://theflatratemovers.com/robots.txt · 958 bytes · SHA-256 94dea4b3f3e7806c34c1984f54948326f83027607ff95d155012fe7912ceac80 (observed 2026-10-31T21:04:17Z, HTTP 200)
Drift gate
no-drift-observed — served bytes equal the deployed source file’s bytes; no Cloudflare-prepended directives observed in the served file
Content Signals
search: unset · ai-input: unset · ai-train: unset (absent from the served file)
__usage_ai-training token
absent — recorded as decision evidence in the dataset; not deployed, because the owner chose open training
Agent groupPurpose classPosture
GPTBottrainingallowed
ChatGPT-Userretrievalallowed
OAI-SearchBotretrievalallowed
ClaudeBottrainingallowed
Claude-Userretrievalallowed
anthropic-airetrievalallowed
Google-Extendedtrainingallowed
PerplexityBotretrievalallowed
Perplexity-Userretrievalallowed
CCBottrainingallowed
Applebot-Extendedtrainingallowed
Meta-ExternalAgenttrainingallowed
cohere-aitrainingallowed
YouBotretrievalallowed
DuckAssistBotretrievalallowed
MistralAI-Userretrievalallowed
*otherallowed

No archive-specific agent is named in the file; archive admission rides on the wildcard group and on CCBot, whose collections double as the public archive.

The signed signal log

Preference signals only matter as served, so the registry keeps a signed observation log: each entry records a signal exactly as it was served — digests, byte size, parsed directives, validity window — chained to the previous entry and signed with the estate’s Ed25519 key, verifiable against the public key file. The first entry observes today’s robots.txt. No Internet Archive capture of the current robots.txt exists yet (the captures on file are of the predecessor file, March 2026), so its archive field stands honestly absent; the optional RFC 3161 timestamp field stands unpopulated — no Time-Stamp Authority has been adopted.

Entry
sig-2026-10-31-robots-001 · mechanism robots · observed 2026-10-31T21:04:17Z by Flat Rate Machine signal observation (Mira) — urllib fetch + build-crawl-presence parser, 2026-10-31
Body
SHA-256 94dea4b3f3e7806c34c1984f54948326f83027607ff95d155012fe7912ceac80 · 958 bytes · 18 parsed directives · spec RFC 9309
Entry digest
e6927f3889fe39008bad8fac1ccad36029ea1cf726861cb3c237f60510bbdde7 · Ed25519, key theflatratemovers-2026-10-29-1 · previous entry: genesis (none)

Gaps P1–P6, with their solutions

Six named gaps. Each record in the dataset carries its evidence and impact in full; the designed solution is printed here in full — solutions, not problem lists.

GapStatusResolves inDesigned solution
P1 — The current estate has zero corpus presence; its debut is a single upcoming collection that nothing was scheduled to observeopen — the registry instrument is built (this batch); the watch itself wires into the measurement cadence in batch E5-B2E5-B2The November watch, as a standing instrument: on the measurement cadence, poll collinfo; the day a post-CC-MAIN-2026-43 collection appears, run the wildcard query against it and write the debut record into this registry (classes, statuses, digests, timestamps). If a collection misses the domain, the escalation is supply-side only — verify CCBot-facing health and link inflow, record missed-collection, and let the next check be a second observation; two consecutive misses escalate to a named finding in the cadence report.
P2 — Presence, when it comes, will be a sample — which URL classes the frontier samples is unobservable in advance and was unrecorded after the factopen — the accounting is built into this registry; the first sampled-mix observation awaits the first post-cutover collectionE5-B2 (first observation)URL-class accounting in this registry (the presence_summary view): after the debut collection, state the sampled mix as data. If the mix starves the dense classes, the designed response is internal-link and sitemap-priority emphasis on those files from high-authority pages — the one frontier input we control — with the next collection’s mix as the test. No response is designed for a mix that has not been observed.
P3 — The training-data posture was a blanket allow that had never been recorded as a decisionresolved — owner decision recorded 2026-10-31: Option 1, open training, made deliberate. No file change (Option 1 mechanics); the policy gate is armed in verify.js §22 and in this generator’s drift gateE5-B1 (this batch)A one-page decision record with three options and their mechanics, presented to the owner; the chosen option executed exactly as chosen and stored in this registry’s robots_policy record with the file’s digest, so any future drift between the recorded posture and the live file is a gate failure, not an opinion.
P4 — Filter survival is reasoned, not measured — no extracted (WET) record of this domain’s pages has ever been readopen — awaits the first current-estate capture (P1); the filter_inspection table stands empty by design until thenE5-B4The WET inspection, scheduled against the debut capture: pull WET records for a fixed sample (homepage, one category page, one dataset file, llms.txt, one blog post) via the index’s offset/length pointers and score extraction completeness, boilerplate share and repeated-line fraction into this registry’s filter_inspection table; any structural problem becomes a designed estate fix in the normal batch motion.
P5 — Stale-corpus dilution has no counterweight: the predecessor sites’ text sits in dozens of collections and is re-ingested by future corpus buildsopen — measured per collection by this registry; closes by accumulation as post-cutover collections landstanding cadence (E5-B5)Dilution by supply, the only mechanism that exists (published collections are immutable research artifacts — there is no correction channel): maximize the current estate’s presence in new collections (P1/P2), keep URLs stable so recaptures accumulate on the same URLs, and record the staleness honestly in this registry’s content-era fields so no program document claims the corpus “knows” the current company until P1+P4 say so.
P6 — Four 2026 collections could not be verified in the dossier pass because the index API errored under loadresolved — the B1 seed sweep (2026-10-31) returned a definitive answer for every collection in collinfo, the 2026 series included; no collection stands unverifiableE5-B1 (this batch)The registry’s seed sweep runs with retry/back-off until every collection returns a definitive answer (captures or “No Captures”), and any collection that still cannot be read is seeded as unverifiable-index-error — a visible state, not an omission. The cadence runner inherits the same discipline: an errored check is reported as errored, never as “no change.”

Mechanism pins — the facts the decision rests on

Pinned against primary sources in the 2026-10-31 crosscheck reconciliation, so the posture is argued from verified ground.

MechanismPinned factCrawler adherence
TDM Reservation Protocol (TDMRep)A W3C Community Group Final Report (10 May 2024), not a W3C Standard. No major AI crawler is publicly documented as honoring it; its weight is as a legal-reservation record in the EU text-and-data-mining opt-out debate.none documented
IETF AI Preferences (aipref)draft-ietf-aipref-vocab-08 + draft-ietf-aipref-attach-05 — Internet-Drafts, not RFCs; no crawler adoption confirmed as of 2026-10-31.none confirmed
C2PA / CAWG training-mining assertionThe C2PA core specification carries no training/data-mining assertion (C2PA’s own clarification). The only living C2PA-adjacent preference assertion is the CAWG cawg.training-mining assertion, v1.1 (DIF-ratified 16 May 2025). It is a provenance mechanism, not a crawl-preference signal crawlers read.none documented as a crawl preference
Shared __usage_ai-training robots tokenA single-token training opt-out (User-agent: __usage_ai-training + Disallow: /) has public honoring commitments from OpenAI, Google and Microsoft (announced 2026-10-30; effective staggered through 2027 — Microsoft from 2027-02-01, Google aiming 2027, OpenAI “coming months”; Anthropic reported, no announcement of its own). It does not affect search or AI answers. Recorded as decision evidence for P3; the owner chose Option 1 (open training) on 2026-10-31, so the token is not deployed.commitments announced 2026-10-30, effective staggered through 2027
Per-purpose signals generally (Content Signals, TDMRep, aipref)Beyond vendor robots tokens, every per-purpose signal has zero confirmed major-crawler adherence as of 2026-10-31. Content Signals specifically: no crawler or LLM is confirmed to use it (Google’s John Mueller, as documented 2026-10). Cloudflare can nevertheless prepend Content-Signal directives to the SERVED robots.txt without changing the source file — which is why this registry’s drift gate compares served bytes to source bytes.zero confirmed (2026-10-31)

Facts & download

File
datasets-crawl-presence.json · 7,708,560 bytes · SHA-256 042dfa089e24c53b4636ccfd722f65ea1a0173421b59aa9d03a8f2ca72fef6b0
Contents
129 collections · 16197 capture rows · 14822 with status 200 · current-estate captures: 0 · 17 robots agent groups (7 training, 9 retrieval) · 6 gaps (2 resolved)
License
CC BY 4.0 — reuse with attribution to The Flat Rate Movers
API
GET https://api.theflatratemovers.com/v1/crawl-presence (byte-identical file; ?table= filters to collections, presence, summary, robots, signals, inspections, releases, gaps or mechanisms)
Provenance
Sealed in the signed AI master index (Ed25519). Verify any copy: GET https://api.theflatratemovers.com/v1/verify?file=datasets-crawl-presence.json

Download the dataset (JSON)

Moving something heavy, valuable, or hard to place?

One flat rate, set after a full review of scope, distance, manpower and equipment — never an hourly meter. Tell us what is moving and get the number in writing.

Get My Flat Rate Quote Call (540) 422-2153