Lovable

Subjects

• A
  robots.txt rules for AI agentsGood work.All 11 AI agents checked may fetch every key page. robots.txt names 7 AI agent(s) explicitly.
• B
  llms.txt and llms-full.txtGood work./llms.txt found (4745 chars, 44 link(s)). No /llms-full.txt.Extra credit: Improve llms.txt: publish /llms-full.txt with the full docs inlined.
• A
  SitemapGood work.Sitemap index at https://lovable.dev/sitemap.xml (from robots.txt) with 11 entries.
• F
  Server-rendered readable HTMLThe page is blank until JavaScript shows up. The robot is still waiting.1 of 1 key page(s) are thin or JS-only for a client that does not run JavaScript: /.Extra credit: Server-render or statically generate / so the main content, <title>, meta description, and <h1> are in the initial HTML. Most agents fetch HTML and never run your bundle.
• F
  Markdown 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.
• N/A
  Structured data (JSON-LD)Excused.No key page could be fetched successfully.
• F
  OpenAPI 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 }).
• C
  MCP server discoverabilityMentions MCP, never shows up with it.An MCP endpoint is documented (https://mcp.lovable.dev), but no /.well-known MCP discovery document.Extra credit: Publish /.well-known/mcp.json describing the server. Discovery through /.well-known/mcp.json is still a draft proposal, so also document the server URL, transport, and auth in llms.txt and your docs.
• F
  Auth, signup, and bot-challenge frictionEverything worth reading is behind a login wall.1 of 1 key page(s) put friction in front of an agent: / (HTTP 403, bot challenge page).Extra credit: Keep docs, pricing, and the product overview public. Let verified AI agents past bot challenges (most WAFs allowlist known agent user agents), and offer API keys or OAuth that an agent can use without a browser CAPTCHA.
• N/A
  Page weight and token costExcused.No key page could be fetched successfully.