At a glance
Signals scored
137
Pillars
5
Version
v1.0
Evidence-cited
119
published source backs the magnitude
Heuristic
18
expert judgement, openly flagged
Published
6 Jun 2026
Methodology
Every AEO tool in the market today publishes a score. None publishes their methodology. This document does — every signal, every weight, every source we cite for that weight, and the honest label of whether each magnitude is EVIDENCE-backed or an educated HEURISTIC.
At a glance
Signals scored
137
Pillars
5
Version
v1.0
Evidence-cited
119
published source backs the magnitude
Heuristic
18
expert judgement, openly flagged
Published
6 Jun 2026
§
Every AEO measurement tool — Profound, Semrush AI Visibility, Otterly, AthenaHQ, Peec, Brand Radar — uses a proprietary, unpublished scoring algorithm. Customers buy the score on faith and cannot independently audit, replicate, or peer-review the numbers.
That's fine for monitoring tools. It's a problem for a certification. A cert that says “your site scores 87 by the AI Search Ready standard” means nothing if “the AI Search Ready standard” is a closed box.
This document is the open box. The full rule set lives in the scanner's src/lib/scanner/data/signal-rules.ts, schema-rules.ts and ai-crawlers.ts — MIT-licensed, version-controlled, and reproducible from published canonical sources where they exist.
§
Every signal belongs to exactly one pillar. The pillars are independent inputs to the headline score; their weights are documented in the source code and are themselves subject to empirical recalibration via the corpus (see Calibration policy below).
§
Of 137 signals, 119 have their score magnitude backed by a cited public source (Google Search Central docs, schema.org spec, Lighthouse/WebVitals documentation, etc.). The remaining 18 are expert judgment — there is no canonical source that says “a missing H1 costs you 6 SEO points,” so we don't pretend there is.
Every rule's impactRationale field is prefixed EVIDENCE: or HEURISTIC:. Future versions of this standard will gradually move HEURISTIC signals to EVIDENCE as the corpus grows enough to regression-fit the weights against measured citation outcomes.
§
npm run corpus:evaluate. Per-issue Pearson correlation against operator labels is tracked. Rules with consistently positive correlations (firing on the BETTER sites) are softened in subsequent calibration passes.§
The first AEO-audit Model Context Protocol server. Any MCP-compatible client (Claude Desktop, Cursor, LM Studio, Continue.dev, Zed) can call the AI Search Ready audit directly from a chat. Free preview tier; no key required.
claude_desktop_config.json
{
"mcpServers": {
"aisearchready": {
"command": "npx",
"args": ["-y", "@aisearchready/mcp"]
}
}
}Three tools surface: audit_url (137-signal scan), verify_cert (canonical signed cert state for a domain), and get_standard (this document, condensed). Source at github.com/ed2903-web/aisearchready/mcp-server.
§
A standard whose maintainer doesn't audit themselves isn't a standard. We publish our own live scan and well-known files alongside the published score so anyone can verify we apply the same rules to our own site that we apply to anyone else's.
§