65/100 C #347 of 1188
Audited November 2, 2026 from public surfaces only. Can AI agents discover, read, and act on login.gov? 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 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 ~276 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 Sitemap advertised in robots.txt or served at /sitemap.xml. |
10/10 | pass |
| A6 | Everyday agent tasks reachable from the homepage Reached from homepage: support/contact (/help/), docs/api (developers.login.gov), legal/privacy. |
15/20 | pass |
| 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 |
2 checks cost login.gov points. Each one below is the specific remedy for what we measured, not general advice.
Serve a plain-text file at https://login.gov/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.
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 login.gov is without inferring it from prose.
Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on login.gov through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.
Optional. If login.gov 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