AIScoring runs 12 deterministic checks totalling 100 points. Same input, same result. No LLMs in the scoring loop. Results cache for 24 hours per domain. Every check below cites its authoritative source and its exact pass / partial / fail rule.
Methodology v1.0 — Our scoring weights reflect documented, transparent criteria, refined as we scan more of the web. Every change is versioned and public — no black box. Disagree with a rule or a weight? Tell us: hello@aiscoring.io and we'll show our reasoning.
GET /llms.txt and GET /llms-full.txt (8s timeout each). Rejects HTML error pages.
GET /robots.txt, parses User-agent / Disallow groups.
All <script type="application/ld+json"> blocks from the homepage and pricing page.
GET /pricing, /plans, /pricing/. Regexes prices ($/€/£ + digits) and looks for JSON-LD Offer/PriceSpecification.
note: Agents cannot recommend what they cannot price.
GET /docs, /api, /developers, /developer, /api-docs, /openapi.json, /swagger.json.
GET /.well-known/agents.json, /mcp.json, /.well-known/mcp.json, /agents.json.
note: This is the newest and most in-flux check. Weight kept modest (8) until adoption stabilises.
GET /sitemap.xml; greps robots.txt for a `Sitemap:` directive.
The homepage and pricing page HTML.
Homepage <a> tags; fallback GET /signup, /register, /get-started, /sign-up.
note: Agents cannot fill out sales-qualification forms. If your only path to purchase is human-gated, agents cannot buy.
Homepage <title>, meta description, and JSON-LD Organization name/description.
GET / with a plain user-agent, strips <script>/<style>/tags, counts remaining words.
note: Cloudflare's public research shows the vast majority of the web serves little agent-legible content — most AI crawlers do not execute JavaScript, so a client-rendered SPA is effectively invisible.
Homepage links plus GET /terms, /privacy, /.well-known/security.txt (and variants).
The 12 checks above measure your site's agent-readiness — deterministic, verifiable properties of your public surface. They do not measure whether ChatGPT actually recommends you today. That's a separate question, and we're honest about how it can and can't be answered.
For each customer we compile a fixed set of high-intent buying questions in their category (e.g. "best CRM for small SaaS teams"). Every week we ask that set to ChatGPT, Claude, and Perplexity through their public APIs from a clean context, and record which vendors are cited, in which position, and with what supporting URLs. Same prompts, same models, same week → apples-to-apples trend.
No tool — ours or anyone else's — can count how many times you were mentioned inside ChatGPT this week. OpenAI, Anthropic and Google do not publish that data, and there is no back-channel that reveals it. Any vendor claiming a "real" mention count is extrapolating from a sample and calling it a census. We prefer to call sampling sampling.
When an LLM cites you and the user clicks through, that click hits your site with a referrer like chatgpt.com, claude.ai, or perplexity.ai. That is census data — every real click is counted, not sampled. It's a lower bound on impact (many citations don't get clicked) but it's the only ground truth available today, and we surface it directly.
What each letter means for whether AI agents can find, evaluate, and buy from you.