Readiness
—
scored public-surface checks
AgentFit dashboard
Ensure customers can reach, understand, and complete work through your site with AI agents.
—
Create an account or use your existing account token. Tokens are shown once and only their hashes are stored.
Add a site to begin
Run the seven-stage audit to measure the site without treating missing instruments as zero.
—
scored public-surface checks
—
attempted tasks completed
—
answers naming the site
—
answers citing the site
—
share and position in answers
How prominently it features, and what to improve across OpenAI, Anthropic, and more. No completed run selected. A dash means not measured, never zero.
Each stage writes one row when it finishes. Unavailable instruments are named explicitly and remain distinct from failures and zero values.
| Stage | Status | Finding | Unavailable instrument | Evidence |
|---|
Source: the selected run’s persisted stage rows and R2 evidence keys.
Compare prompts and responses across models, and see how AI agents interpret your content before you ship changes.
As web traffic shifts from human visitors to autonomous AI engines, structuring your site for machine consumption is the next frontier of web development: from SEO to answer-engine optimization (AEO), so agents can discover, digest, and cite your content. Agent readiness is still emerging, and the standards behind these checks keep evolving.
Stage 01
Read the site the way an agent does: crawler policy, sitemaps, Markdown, entity data, and agent interfaces.
origin checks + passive company-surface discovery via crt.name · no key required
Stage 03
Compare exact citation, mention, prominence, and share-of-voice measurements across enabled providers.
Stage 05
Readiness and recommendation are separate conditions. Citation and mention booleans remain exact; models add diagnosis, not scores.
Optimization
Ingest source passages, retrieve supporting evidence, and produce capsules only when their claims already exist in the source.
Stage 06
Turn deterministic gaps and observed provider behavior into generated, source-bound files rather than advice.
Run Map first.
Stage 07
Import content, approve source-led edits, probe citations, and measure interventions against the matching control period.
discovers sitemap.xml or RSS automatically · re-imports update, never duplicate
Approved edits receive a before snapshot and 28/56-day readings. A post-level change is reported only against blog-wide movement for the same dates.
Operator evidence
Import access logs or operator summaries to separate crawling from customer referrals. The crawl-to-refer ratio is pages fetched per visitor sent back. Access logs cannot measure referred visits, so that ratio stays a dash, not a zero.
Just handle it
Send one customer prompt through the answer panel. Transactional prompts also attempt the site's real task path within the selected safety boundary.
Provider access
Keys remain in this browser’s localStorage and are sent only with the corresponding probe request. The server does not persist them.