The app
The record, in your hand.
In one sentence
The CrawlCheck app is a native companion to crawlcheck.io, in build for iPhone and Android, that reads the same dated record the site keeps, follows the site's design tokens and section list live from /tokens.css and /app.json, and adds a field kit of instruments that only a phone can run.
Your grade on the home screen. A receipt the moment something moves. And a field kit of instruments that only work in a hand, on a street, or on a network the datacentre will never stand on. In build for iPhone and Android; the record it reads from, and the files it follows, are already live.
What it is
A native companion to this site for paying clients. It scans a domain the way the site does, shows the audit on the same report vocabulary — Reach, Read, Quote, the same 33 sections, the same grade — and keeps the dated record beside it. Nothing about a score is computed on the phone: the app reads the record the site keeps, and adds to it.
What it adds is what a server cannot do. A phone has a camera, a location, a cellular network and a share sheet, and each of those is an instrument here. Every instrument sends what it measured back to the site as a receipt, so the record gets sharper every time one is used.
Everything the app paints — colour, type, the section list, the plans — it takes from two files this site already serves, so it follows the site the moment the site changes and hard-codes none of it.
From the live demo record
What a phone can do that a server cannot
Six instruments ship at launch. Fourteen more are in the design and appear in the app as roadmap — visible, explained, with a notify-me — rather than as promises on this page.
Citation rounds
Ask the engines from your own phone. Share any answer back; the app files whether you were cited, who was cited instead, and the date.
Network replay
Re-run the identity check from your own network. A datacentre reading and a cellular reading of the same page, side by side, on the record.
Field proof
Stand at the address. The camera checks the sign and the hours against the schema; the evidence is hashed into the record.
Deploy handshake
A fix ticket that closes itself. The developer scans the QR when they ship; the app re-measures within the minute and tells you both.
Receipts inbox
Every dated change, as a push. Snooze it, assign it, or mark it known; each one deep-links to the finding with the byte diff open.
Scan from anywhere
A URL in the share sheet becomes a scan; a screenshot of an answer becomes a citation receipt; a log becomes a verifier run.
Already live: what the site serves for the app
68
design tokens at /tokens.css, light and dark
33
sections in /app.json
4
plans in /app.json
8
app API routes live
The app follows /tokens.css (a stable alias of the site’s own design tokens, 5-minute cache, ETag) and /app.json (sections, stage questions, plans, limits, checkout), both served from this site’s Worker with CORS. Its backend is live too: sign in with the licence key from your receipt, read your portfolio and each domain’s record, register for push, and post field-instrument measurements. None of those routes can move a score; they read the record and add receipts to it.
What it measures, and what it never does
Measured
About 30 read-only requests to your public pages and machine files, identified honestly as this scanner. Beyond that, only what an instrument you enabled asks for, only while it runs.
Never
No writes to your site or listings. No scraping of people. No selling your record. No location outside an instrument that needs it, and none kept at rest — a location is written into the receipt it belongs to, then discarded.
Availability
The app is in build for iPhone and Android from a design frozen on 5 September 2026 — 28 screens, the field kit, the live-token contract. It is not on the app stores yet, and this page will say so until it is. It will be free with any plan. A plan today is not waiting on the app: the record keeps measuring twice a day whether the app exists yet or not, and the app will open onto whatever that record holds.
The record the app will open onto is already being kept.
Start with the free 30-day record on one domain; the app reads the same thing when it ships.
Read next
The browser extension (the other client) · Plans · The live demo report · The API