We adapt your website for AI traffic.

FAQ

Short answers to common questions.

What is "AI-agent readiness"?

It is the property of a website that allows three distinct kinds of software readers — crawlers, assistants, and buyer agents — to use it fluently against published, vendor-neutral standards. The Checker grades a catalog of deterministic signals across seven groups and returns a letter grade plus a global percentile.

How is this different from SEO?

SEO grades pages against ranking signals for Google’s index. AI-agent readiness grades pages against the standards three different software audiences need: crawlers (/robots.txt, /llms.txt, sitemaps), assistants (JSON-LD identity, OpenAPI 3.1, MCP handshake), and buyer agents (ACP, AP2, x402, schema.org Offer). The overlap with SEO is in the Hygiene group and parts of Citation — perhaps a third of the catalogue. The rest is new surface area.

What does a Setup engagement include?

Setup is the studio’s one-time engagement. We adapt your site so AI agents — crawlers, assistants, and buyer agents — can use it fluently. Scope is agreed on the discovery call; the engagement fixes every failing Checker signal and builds out the signal coverage your site is missing (Discovery, Identity, Agent Contracts, Citation, Rendering, Hygiene, Commerce), including multi-page template audits (catalog, blog, docs) where they apply. It also includes a baseline citation report, server-log crawler analysis installed, GA4 AI-source segmentation configured, and a before/after Checker grade. Fixed-price scope agreed up front, 30 days of post-launch support, and a validation re-scan after launch. Deliverables are pull requests or commits into your repository — the code is yours after the engagement, no runtime dependency on the studio. Afterwards, an optional monthly Retainer keeps the score from decaying as the standards move. The studio adapts existing websites only in v1 (no greenfield builds) and works with whatever your site is built on (Next, Astro, Nuxt, Hugo, WordPress, custom).

Is the AI-bot markdown variant cloaking?

No. Cloaking is serving substantively different content to bots versus humans to manipulate ranking. We serve the same content to both, in two encodings: HTML for humans, a denser markdown variant for AI bots that benefit from it. The text, claims, and structure are identical; only the encoding differs. This is documented on /policy.txt, and the markdown variant is grepped on every build to verify content parity.

Do you grade on a curve, or compare me against my industry?

No curve. The Checker grades against universal published standards, so your letter grade is absolute — it never softens because your industry’s average is also low. But the report does show you a map. Alongside the absolute grade you get a global percentile against the whole corpus, a vertical percentile against your self-classified peers (“among SaaS sites, your 67 is the median”), and a per-signal corpus-wide pass rate. The vertical number is a sales and prioritisation map, not a comfort blanket: it tells you how far the realistic frontier is, while the per-signal rarity tells you which fixes are table-stakes and which are genuine competitive moats.

What data do you store about my site?

One row per scan in a SQLite corpus on a single VPS — the URL, scan mode, score, signal results, and timestamp. No PII (websites are public information; the privacy framework that applies to user data does not apply to scan inputs). No cookies set on visitors. Reports themselves are ephemeral — returned inline as the HTTP response body and discarded after the request.

Can AI agents call the Checker themselves?

Yes. The site is itself agent-callable. The Checker is exposed as a tool via an MCP server at /.well-known/mcp.json and /api/mcp. The studio’s catalogue is published as an ACP feed at /sitesfor.acp.json so buyer agents can discover purchasable SKUs and complete a Stripe Checkout flow on a user’s behalf. The reference implementation is the proof.