85/100 A #107 of 1220
Audited October 25, 2026 from public surfaces only. Can AI agents discover, read, and act on kbag.se? Check by check:
GPTBot: allowed ClaudeBot: allowed Claude-User: allowed PerplexityBot: allowed Google-Extended: allowed CCBot: allowed
| Check | Finding | Points | Result |
|---|---|---|---|
| A1 | llms.txt for AI readers Present with 7791 chars and links. |
15/15 | pass |
| 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 ~330 words of visible text. |
25/25 | pass |
| A4 | Structured data (schema.org JSON-LD) Valid JSON-LD found on the homepage. |
15/15 | pass |
| A5 | Sitemap discoverable Sitemap advertised in robots.txt or served at /sitemap.xml. |
10/10 | pass |
| A6 | Everyday agent tasks reachable from the homepage None of pricing, support, docs, or legal are linked from the homepage. |
0/20 | fail |
| B1 | MCP server advertised Serves /.well-known/mcp/server-card.json. |
5/5 | pass |
| B2 | OpenAPI description published No OpenAPI document (bonus check — only relevant for APIs). |
0/5 | skip |
1 check cost kbag.se points. Each one below is the specific remedy for what we measured, not general advice.
An agent could not reach pricing, support/contact, docs/api, legal/privacy from the kbag.se 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.
Optional. If kbag.se has a public API, publishing an OpenAPI document at /openapi.json lets an agent call it correctly without a human reading your docs first.
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.
HTML
Markdown