agentability

← AI-Readiness Index

lichess.org

50/100   D #619 of 1187

Audited November 16, 2026 from public surfaces only. Can AI agents discover, read, and act on lichess.org? Check by check:

GPTBot: partial ClaudeBot: partial PerplexityBot: partial Google-Extended: partial CCBot: partial Claude-User: partial ChatGPT-User: partial Perplexity-User: partial

CheckFindingPointsResult
A1 llms.txt for AI readers
No /llms.txt found — AI readers get no curated entry point.
0/15 fail
A2 AI crawler access policy
robots.txt allows the major AI crawlers and agents.
15/15 pass
A3 Content readable without a browser
Plain fetch of the homepage yields ~561 words of visible text.
25/25 pass
A4 Structured data (schema.org JSON-LD)
No machine-readable entity markup on the homepage.
0/15 fail
A5 Sitemap discoverable
No sitemap found.
0/10 fail
A6 Everyday agent tasks reachable from the homepage
Reached from homepage: support/contact (/contact), legal/privacy (/privacy).
10/20 warn
B1 MCP server advertised
No MCP advertisement (bonus check — most sites skip this).
0/5 skip
B2 OpenAPI description published
No OpenAPI document (bonus check — only relevant for APIs).
0/5 skip
B3 UCP commerce profile published
No UCP profile (bonus check — agentic commerce, relevant to shops).
0/5 skip

What lichess.org would have to change

4 checks cost lichess.org points. Each one below is the specific remedy for what we measured, not general advice.

  1. llms.txt for AI readers0/15

    Serve a plain-text file at https://lichess.org/llms.txt listing the pages an agent most often needs — pricing, docs, support, account management — each as a one-line description and an absolute URL. It is read by an agent arriving cold with no idea of your structure. Fifteen points, and most teams ship it in an afternoon.

  2. Structured data (schema.org JSON-LD)0/15

    Add schema.org JSON-LD to the homepage — Organization at minimum, plus Product or Article where they apply. It is how an agent learns what lichess.org is without inferring it from prose.

  3. Sitemap discoverable0/10

    Serve https://lichess.org/sitemap.xml and point to it from robots.txt. Without it an agent has to guess your URL structure from whatever the homepage happens to link.

  4. Everyday agent tasks reachable from the homepage10/20

    An agent could not reach pricing, support/contact, docs/api, legal/privacy from the lichess.org homepage. These are what agents are sent to find most often. Each needs a plain link an agent can follow from the homepage in one hop — not behind a menu that only appears once JavaScript runs, and not solely in a logged-in view.

  5. MCP server advertised0/5

    Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on lichess.org through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.

  6. OpenAPI description published0/5

    Optional. If lichess.org has a public API, publishing an OpenAPI document at /openapi.json lets an agent call it correctly without a human reading your docs first.

How this score has moved

Unchanged at 50/100 since October 7. Every audit is a fresh fetch, so a change here means something on lichess.org changed.

50Oct 7 50Oct 12 50Oct 14 35Oct 19 50Oct 25 50Oct 26 50Oct 30 50Nov 1 50Nov 2 50Nov 3 50Nov 9 50Nov 16

Put this score on your site

The badge reads live from this page, so it updates itself when the score changes. Free, no attribution required beyond the link it already carries.

AI-Ready 50 out of 100 for lichess.org

HTML

Markdown

Work on lichess.org? Each failed check maps to a concrete fix in the methodology — most ship in under an hour. Scores refresh weekly; request a re-run after you deploy.