The Record Check

The five parts of the Record

• The Record. Every statement the five engines made about you in 25 answers, classed true, wrong, stale or unverifiable against your own published facts, with the source each engine cited.
• The Wrong List. Each wrong or stale statement traced to the page that carried it: your own page, a directory, a review site, an old article, a forum, or "cause not found".
• The Access Check. Whether the engines' documented crawlers and fetchers can read your robots.txt, home page and pricing page at all. A company the engines cannot read cannot be corrected by content.
• Time to AI. Your three most recent launches: which engines state them, and how many days after launch.
• The Correction List. For every wrong statement, the fix: which page to change or publish, with the exact text, your dated Current Facts block, your Vendor Facts file under our open standard, and the correction requests for pages you do not own, drafted for you to send.

The receipts: all 25 answers with engine, model, time and citations. Captured by people, never by a script.

How it works

1. Buy the Record Check. In your account, confirm your fact sheet: what you are and do, pricing, your three most recent launches with dates, compliance, ownership, one rival, each with the page that proves it.
2. Within three business days our team captures the 25 answers by hand and classes every statement. Priya Nair, Management Consultant, reviews before release.
3. Your Record is live in your account, with the PDF and the Correction List. Add the Fix Sprint and we make the corrections and measure until the engines say it right.

$490 once. Included in the Fix Sprint and monthly in the program. Agencies: $490 per client, under your brand; we never contact your client. Refundable in full within 30 days of delivery. The Record Check carries no credit toward any other offer.

The five fact questions

The same text goes to all five engines, filled in from your fact sheet.

1. Tell me about <company>: what it does, who it is for, and where it is based.
2. What does <company> cost? Describe its pricing and plans.
3. Does <company> offer <launch 1>, <launch 2> and <launch 3>? What has it released recently?
4. Is <company> secure and compliant, and who owns it? Include certifications, data hosting and ownership.
5. <company> vs <rival>: compare them on features, pricing and support. (Without a rival: What are the strengths and weaknesses of <company> compared with its main competitors?)

How we capture and class

Every answer is captured by a member of our team, by hand, in a signed-in seat, one question per fresh chat, with no custom instructions, memory and personalisation off where the product allows, web search on where the product offers it, in US English, using the exact question text and nothing else. We record the engine, the model label as displayed, the seat type, the UTC time, the full answer text (for Perplexity, the 60-word excerpt that carries the statements and the share link), every visible citation, and a screenshot. Google AI Overviews is recorded as present or absent before capture; an absent Overview is a valid record. Google AI Mode is captured in the AI Mode tab. Nothing is captured by a script, an extension or an automation; the engines' terms forbid it, and so do we.

A statement is one factual claim an answer makes about the company. Every statement in the 25 answers is listed and classed by our reviewer against the company's fact sheet and its own public pages: true when it matches; wrong when it contradicts the published fact on the capture date; stale when it was true before a dated change the company documented; unverifiable when neither the fact sheet nor the public pages settle it within five minutes. Unverifiable counts as neither right nor wrong. Each wrong or stale statement is traced to its causing page: the citation the engine attached if it carries the statement, else the page found by searching the statement's distinctive words, else "cause not found". Causing pages are typed: own page, directory, review site, press, forum, other. Time to AI is the number of days from a launch date to the first capture in which an engine states the launch correctly, or "not yet". Time to correction is the number of days from a fix shipping to the first capture in which an engine states the fact correctly. Counts are reported with their bases; answers with at least one wrong or stale statement are reported as n of 25 with a 95 percent interval.

The Access Check reads the company's robots.txt, home page and pricing page once each with the documented user agents of ChatGPT, Claude, Perplexity and Google (the agent traffic guide lists them with their sources), and checks for an llms.txt file and a Vendor Facts file. For each agent it prints allowed or disallowed by robots.txt and the status the server returned; a 403 or a challenge page is printed as "blocked at the edge". Nothing else is fetched, nothing is retried more than once, and the check runs only for a company that bought or requested it. A company the engines cannot read cannot be corrected by content; the Correction List starts there.

Record rules on our method page

The Correction Desk

Any company can report one wrong or stale AI statement about itself, free. Within five business days our team captures by hand whether it reproduces, and you get the dated record and one correction line in a free account. With your consent, the Correction Ledger publishes the statement type, the engine, the found date and the corrected date, so the industry can see what the engines get wrong and how long correction takes.

Report a wrong statement, free or read the Correction Ledger.

What the Record does not prove

The Record records what five AI engines stated about a company in answer to five questions on stated dates, captured by people and verified against the company's own published facts. It does not prove what any buyer was told, that a correction will be learned, or when. "Wrong" means the statement contradicted the published fact on that date; "stale" means it was true before a documented change; a causing page is the page that carried the statement, not proof that the engine read it. Time to AI and time to correction are observations on capture dates. Before and after figures are observations with intervals, not a lift verdict; the controlled-lift verdict belongs to the shortlist measurement under our proof method. The Record promises no correction, no position, no leads and no revenue.

For developers

The Record for an account is available at GET /api/v1/record (statements by class per engine, the Wrong List with causing-page types, the Access Check, Time to AI and the Correction List states, with capture dates; receipts stay in the account) with an account API key; the demo key returns the sample. Read only. The Correction Ledger is public at app.broadcastwell.com/ledger. Developers