Is your site agent-ready? →

Home › Tools › The Three-Consumer Check

Free check · 7 items · 5 minutes

Your site has three consumers. Are you operating for all of them?

People, search crawlers and retrieval agents read the same estate differently. This check scores whether the third one can reach you, read you, and budget a read — and refuses to infer anything you have not measured.

7 items Measured against 35 fetches Nothing inferred No email

No email required. Nothing is sent anywhere — your answers stay in this browser.

0 of 7 answered

The Three-Consumer Check

Items 1 and 2 need a measurement taken in the last 14 days. Edge rules change without notice, so an older matrix is a historical document.

Item 1

Have you sent the five common AI user-agent strings at your top 20 URLs and recorded every HTTP status, in the last 14 days?

Direct fetches. It costs an afternoon and no API units.

Item 2

Have you compared those statuses against what your own robots.txt permits, token by token?

A non-200 where the file says “allowed” is an edge ticket, and it is not the SEO team's.

Item 3

Do you have a measured raw-versus-rendered word count for your top templates, taken in the last quarter?

Measured. If you have not measured it, answer no and the check will report it as not measured.

Item 4

Does every template ship JSON-LD, and do your data-carrying pages ship a table and a list?

Tables and lists are the structures retrieval systems extract most reliably.

Item 5

Do you know the token count of your heaviest page type, and is it exposed in metadata?

Without per-page token counts an agent cannot budget a read.

Item 6

Do you publish operational facts with their exclusions attached — what the product does not do — at a stable, machine-readable path?

The exclusions are what make the facts usable rather than promotional.

Item 7

Is the fetch matrix on a recurring 14-day cadence with a named owner?

A one-off measurement of a system that changes without notice.

Your measurements (optional)

Leave the raw-versus-rendered field blank if you have not measured it. The check will return “not measured” and will not infer a rendering risk from anything else.

Your result
Read the method
What you are being scored against

Our own numbers, measured on a live page one and on ourselves

We scored Reachable but not ready — three of seven — the first time we ran this on ourselves. We serve every fetcher and still score 33 on our own scale.

MeasuredWhat it is
13 of 35 refused (37%)AI-fetcher requests refused across a live page oneFive AI fetcher user-agent strings against the seven domains ranking for a head term. Every refusal was an HTTP 403. The matrix was re-run four minutes later and returned the same 35 statuses. · Indexable, 9 September 2026, n = 35 fetches
0 of 7Domains whose robots.txt disallowed any AI agent tokenNot one of the seven published a disallow. Every refusal contradicted the file the audit would have read. · Indexable, 9 September 2026, 7 robots.txt files
40 of 40 servedOur own estate's answer to the same testTen user-agent strings against four URLs. Nothing refused — and we still scored 33 on the readiness scale below. Serving the request is the easy half. · Indexable, 9 September 2026, n = 40 fetches
33 of 100Our own composite agent-readiness score, on Indexable's own scaleDiscoverability 67, content accessibility 0, bot access control 33, protocol discovery 33. This is our scale, not a vendor dashboard score. · Indexable, 9 September 2026
~3,063 tokensOur llms.txt, with no per-page token countsAn agent cannot budget a read against it. Estimated, not exact. · Indexable, 9 September 2026

A refusal is evidence about edge policy, not vendor intent: record it as “refused a request presenting as GPTBot”, never as “blocks <vendor>”. The composite is on Indexable's own scale, not a vendor dashboard score. One day, one country, seven domains.

Reachable is the easy half

We serve every fetcher that asks and still score 33 of 100 on our own scale. Access is a ticket; legibility is an operating habit.

Get an AI search audit

Copied ✓