01
Direct acquisition
Records the public HTTP outcome, final URL, redirect chain, content type, bounded byte count, and cryptographic artifact hash.
Can AI systems read your site? Stop assuming. Audit the evidence.
A per-actor access-policy audit of the layer below visibility: the robots and AI-usage-header policy that applies to GPTBot, ClaudeBot, PerplexityBot, and others, one request carrying each actor's token, and what a non-JavaScript fetch receives versus what a browser renders — with sealed evidence on every verdict.
For AI-visibility, growth, and content teams accountable for what machines can actually retrieve. We audit the GEO layer; we do not sell rankings, citations, or a score.
Free quick check, no account needed. We record only what the server returns.
Free account, no card. First audit: usually under two minutes.
No universal score. No indexing, ranking, citation, or model-behavior guarantee.
No logo wall — we have no customer logos to show you yet, so we publish artifacts instead: inspect a real audit and the sealed digest it came from. The full bundle, not just the badge, ships with your own scan.
Generative Metrics is an AI access assurance service. The AI Access Audit records the robots and AI-usage-header policy that applies to each documented AI actor — GPTBot, ClaudeBot, PerplexityBot, and others — plus one request carrying each actor's own token, and what a non-JavaScript fetch receives versus what a browser renders. Results are PASS, FAIL, or INCOMPLETE with a sealed evidence bundle and evidence-linked remediations; a rescan reports each fix as VERIFIED, NOT VERIFIED, or INDETERMINATE. No universal score. No promises about AI behavior.
A real audit
A U.S. federal government site — FAIL
Main content appears only after browser rendering — the raw HTTP response exposes almost none of it.
- 36 words visible to a raw crawler · 412 in a browser.
- Scanned 2026-09-19.
- Nothing visibly wrong to a human visitor.
Result contract
PASS
All required protocols completed; no production blocker is open.
FAIL
At least one evidence-linked production blocker is open.
INCOMPLETE
Required evidence was not obtained; compatibility is not established.
Every result names its audit profile, actor, protocol version, execution state, limitations, artifact references, and integrity hash.
No logo wall. Open artifacts.
Verify this product the way it verifies a page
Every claim below is a link you can inspect right now.
Production protocol set
Concrete observations before interpretation
The protocol set deliberately starts with signals that can be recorded, repeated, and challenged. Experimental detectors remain separate and cannot create a production blocker.
02
Named actor policy
Evaluates robots.txt separately for documented discovery, training, grounding, and user-action actors. Training controls are not mislabeled as discovery failures.
03
Raw versus rendered
Keeps the initial response, browser-rendered DOM, and no-JavaScript representation distinct instead of pretending one view represents every consumer.
04
Main-content extraction
Runs a deterministic extraction protocol and reports material raw-to-rendered deficits without claiming universal language comprehension.
05
Structured data
Checks JSON-LD parsing, raw availability, bounded visible-text consistency, and whether markup appears only after client-side rendering.
06
Date evidence
Reports strict machine-readable publication, modification, and HTTP date signals. Missing dates and contradictory dates remain different facts.
07
llms.txt availability
Acquires /llms.txt as a separate hashed artifact and records presence, bounded byte count, media type, and whether the required title heading is present.
08
AI-usage header policy
Reads site-declared AI usage signals from the captured raw response, including x-robots-tag tokens and TDM reservation headers, for each audited actor as an observation-only policy layer.
09
Sitemap availability
Acquires /sitemap.xml as a separate hashed artifact and records presence, validity, listed URL count, newest lastmod, and whether the audited URL path was listed.
10
Structured-data completeness
Compares raw versus rendered schema type presence and records bounded Organization identity fields as booleans, without storing property values.
Closed-loop workflow
01
Audit
Run the versioned protocol set against one URL and one explicit consumer profile.
02
Diagnose
Review evidence-linked blockers, warnings, limitations, and concrete remediation steps.
03
Verify
Rescan after a fix. Each remediation is checked against its named protocol outcome: VERIFIED, NOT VERIFIED, or INDETERMINATE.
What the audit can establish
- What the direct public HTTP protocol received.
- Which named robots policy group and rule applied to the audited path.
- Whether meaningful content or supported structured data appeared only after rendering.
- Whether strict machine-readable date signals were observed or contradicted.
- Whether a specific remediation satisfied its expected protocol outcome on a later scan.
What it cannot establish
- That any provider will crawl, index, train on, rank, cite, or recommend the page.
- That one browser representation is identical to every provider's acquisition path.
- That detected text is true, trustworthy, useful, or semantically understood.
- That absence under a bounded protocol proves universal absence.
- That an experimental detector is production truth.
Questions before you rely on it
Is this another AI visibility score?
No. The core product audits acquisition, policy, representation, extraction, structured-data, and date evidence — the schema a page actually offers AI consumers. The evidence-first result does not calculate a universal readiness score.
Does PASS mean an AI provider will index, rank, cite, train on, or understand my page?
No. PASS means the required protocols in the named audit profile completed without an open production blocker. Provider selection and downstream model behavior are outside that verdict.
What happens when the scanner cannot obtain reliable evidence?
The result is INCOMPLETE, or a remediation verification is INDETERMINATE. The product does not convert missing evidence into a pass, failure, or improvement claim.
Why not ask a general-purpose chatbot to review the page?
A chatbot can offer useful editorial advice, but it is not a substitute for recorded HTTP artifacts, actor-specific policy decisions, deterministic protocol execution, immutable evidence, and finding-specific rescans.
Which AI crawlers does it check?
GPTBot, ClaudeBot, PerplexityBot and other documented AI actors. Each is audited separately, with its own robots-policy reading and its own protocol outcome — never a blended average.
Is Generative Metrics free?
Free tier: up to 5 scans per month, no credit card. The PDF report and the sealed evidence bundle are downloadable on every tier.
What makes it different from AI visibility or GEO tools?
It audits execution facts: the access policy that applies to each documented AI actor and what a non-JavaScript fetch receives versus what a browser renders, using deterministic, reproducible protocols and a sealed evidence trail. It does not sell rankings or promised citations. Visibility predictions vary run to run and are not evidence.
Does it work with my CMS?
It audits what a public URL serves, so it works with any stack or framework. The audit is about what your server and a crawler actually see, not about your tooling.
What is included in Generative Metrics?
Up to 5 scans per month, PDF report and downloadable evidence bundle on every tier. Limits govern scale, not honesty: verdicts stay PASS/FAIL/INCOMPLETE with full evidence.
Start with one important URL
Run one audit, fix one production blocker, and turn the verification rescan into client-ready proof.