CrawlCheck

The workflow, end to end

No llms.txt on supremeconcreteco.com

NO_LLMS_TXT is on 30.9% of all scans. This page is the chain for one real site: 8 of 10 steps on record. Every step is a link to the record that proves it; nothing on this page is a description.

JSON: /api/workflow · the three most common findings · generated 2026-10-07 16:48 UTC

  1. 1

    Problem detected ✓ on record

    NO_LLMS_TXT on /llms.txt, severity 1 — Not present.

    the record before (?, 2026-08-12 04:12 UTC) · the finding explained · machine record

  2. 2

    Exact evidence shown not yet

    evidence bundle · verification

    this record predates the artifact store (sealed manifests from 2026-09-20): the bytes it measured were not retained, so the finding cannot be re-located in them; its own evidence fields and the signed record are what remain

  3. 3
  4. 4

    Impact projected ✓ on record

    projected grade with this fix (/api/impact) · what-if

    the grade formula rerun with this fix's rows cleared, computed from the before record, not measured

  5. 5

    Implementation recorded ✓ on record

    Deployed the vsnary-ml Cloudflare Worker on the zone to serve /llms.txt, /entitymap.json and the robots directives at the edge (x-vsn-ml header) — declared by VSNARY (site owner) on 2026-08-12

    Held in the receipt’s declared_fix, inside the signed body.

  6. 6
  7. 7

    Corroborated by a second observer ✓ on record

    the second observer fetched /llms.txt under 15 identities and was served a non-HTML file each time: the fix holds from a second network

    the signed observation (gha-azure-1, 2026-10-01 19:44 UTC) · corroboration · observer registry

    identitystatusbytescontent_typefile_present
    anon20027798text/plain; charset=utf-8true
    gptbot20027798text/plain; charset=utf-8true
    claudebot20027798text/plain; charset=utf-8true
    oaisearch20027798text/plain; charset=utf-8true
    claudesearch20027798text/plain; charset=utf-8true
    perplexity20027798text/plain; charset=utf-8true
    googlebot20027798text/plain; charset=utf-8true
    browser20027798text/plain; charset=utf-8true
    control20027798text/plain; charset=utf-8true
    bingbot20027798text/plain; charset=utf-8true
    applebot20027798text/plain; charset=utf-8true
    amazonbot20027798text/plain; charset=utf-8true
    bytespider20027798text/plain; charset=utf-8true
    metaexternal20027798text/plain; charset=utf-8true
    ccbot20027798text/plain; charset=utf-8true
  8. 8

    Signed remediation receipt ✓ on record

    rc1:52f4c017188a94cd6ba5… · download · verifies on this observer · node crawlcheck-verify.mjs receipt.json

  9. 9

    Regression watch ✓ on record

    90 readings on 27 days since the fix; the finding has not come back · twice a day

    the certificate (recomputed daily) · newest record (2026-10-06, A) · every measured day (Evidence)

  10. 10

    Business outcome tracked not yet

    computed on the owner's first read of /api/outcomes

    what the connected sources counted after the fix (owner)

Ten steps, each a link to the record that proves it. done:true means the record exists and says what the step claims; a step that is not done says what is missing. Nothing here is asserted without a record behind it.