Report card · Agent builders
LangChain
48/100. Says agents are the future. Its own agent can't read the homepage.
Scanned https://langchain.com/ on October 30, 2026.
Subjects
- Arobots.txt rules for AI agentsGood work.All 11 AI agents checked may fetch every key page. No AI agent is named, so they all fall back to the * group.Extra credit: Add explicit User-agent groups for the AI agents you want, so your policy is a decision rather than a default.
- Fllms.txt and llms-full.txtNo llms.txt. Please see me after class.No /llms.txt (HTTP 404).Extra credit: Publish /llms.txt: a markdown file with an H1 product name, a one-paragraph > summary, and sections of links to your most useful docs. Add /llms-full.txt with the full docs inlined if they fit in a model context.
- ASitemapGood work.Sitemap at https://www.langchain.com/sitemap.xml (from robots.txt) with 645 entries.
- AServer-rendered readable HTMLGood work.All 1 key page(s) return readable HTML without running JavaScript.
- FMarkdown versions of key pagesHands in every page as HTML soup. Markdown was on the syllabus.1 of 1 key page(s) have no markdown version: /.Extra credit: Serve markdown for key pages, either at the same path plus .md or when the request sends Accept: text/markdown, and advertise it with <link rel="alternate" type="text/markdown" href="...">. Markdown cuts token cost and removes layout noise for agents.
- FStructured data (JSON-LD)No JSON-LD. Didn't even write its name on the paper.1 of 1 key page(s) lack valid JSON-LD: /.Extra credit: Add schema.org JSON-LD to / (for example Organization, SoftwareApplication or Product with offers, and TechArticle for docs) and fix any blocks that fail to parse.
- FOpenAPI and API docs discoverabilityCouldn't find the API docs. Neither could the robot.No API spec at /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /.well-known/api-catalog and no API docs link on key pages or in llms.txt.Extra credit: Publish an OpenAPI spec at /openapi.json and link API docs from your homepage and llms.txt. If the product has no API, disable this check in config ("api-docs": { "enabled": false }).
- FMCP server discoverabilityNo MCP server in sight. Ironic, for an agent company.No MCP server found: no /.well-known MCP document and no mention on key pages or in llms.txt.Extra credit: If you offer an MCP server, document its URL, transport, and auth in llms.txt and your docs. If you do not, an MCP server is the most direct way for agents like Claude Code to use your product. Disable this check in config ("mcp": { "enabled": false }) if it does not apply.
- AAuth, signup, and bot-challenge frictionGood work.No login walls, bot challenges, or CAPTCHAs on 1 key page(s).
- FPage weight and token costThis homepage weighs more than my car. Agents pay by the token.1 of 1 key page(s) cost over 20k tokens for an agent to read: /.Extra credit: Cut the token cost of /: serve a markdown version, move inline scripts, styles, and SVG out of the HTML, and avoid large inlined JSON state.
Think the grade is wrong? Fix the site and ask for a regrade, or run the scanner yourself. Scores are reproducible. How grading works.