Alpha Evals / Website Agent Readiness

Alpha Institute glossary

Is your website ready for AI agents?

Assess how AI agents discover, read, and interact with your website. See what works, identify gaps, and get practical instructions to improve.

Free. No login required. Public HTTPS content only.

Customize scan

Assess a leader or your organization: Executive & company readiness
What do we check?
  • Discoverability: Crawl policy, sitemap, links, discovery headers and a bounded DNS sample.
  • Content accessibility: Meaningful initial HTML, accessible structure, error recovery and Markdown negotiation.
  • Agent access controls: Named AI crawler policies, Content Signals and Web Bot Auth discovery.
  • Protocol discovery: API, OAuth, MCP, A2A, skills, WebMCP and ARD discovery.
  • Agentic commerce: Signals for x402, MPP, UCP and ACP; no purchases or payments.
How Alpha calculates the score

Version 2.0 normalizes category weights over applicable, observed checks. Unknown is not zero. A headline score requires at least 70% evidence coverage. Individual emerging protocols are informational; capability checks avoid requiring every competing protocol.

  • Discoverability: 25% before applicability normalization.
  • Content accessibility: 30% before applicability normalization.
  • Agent access controls: 15% before applicability normalization.
  • Protocol discovery: 20% before applicability normalization.
  • Agentic commerce: 10% before applicability normalization.

Levels: 1 Foundational (0–19), 2 Developing (20–39), 3 Established (40–59), 4 Advanced (60–79), 5 Highly agent-ready (80–100). These are equal-width score bands, not percentile rankings.

This public website diagnostic does not assess enterprise governance, security, legal compliance or internal agent adoption. It is separate from an Alpha Independent Eval or verification decision. Scores from version 1.0 and version 2.0 are not directly comparable.

Where can I learn more?

Explore the Alpha Institute glossary for plain-language definitions, leadership implications, implementation guidance and primary sources.

Report a correction to [email protected], including the website and scan timestamp.