60/100 C #417 of 1188
Audited November 2, 2026 from public surfaces only. Can AI agents discover, read, and act on digilocker.gov.in? 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 ~357 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 No sitemap found. |
0/10 | fail |
| A6 | Everyday agent tasks reachable from the homepage Reached from homepage: support/contact (support.digilocker.gov.in). Link found but not confirmed: legal/privacy (/web/about/tos). |
5/20 | fail |
| 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 |
3 checks cost digilocker.gov.in points. Each one below is the specific remedy for what we measured, not general advice.
Serve a plain-text file at https://digilocker.gov.in/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.
Serve https://digilocker.gov.in/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.
An agent could not reach pricing, support/contact, docs/api, legal/privacy from the digilocker.gov.in 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, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on digilocker.gov.in through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.
Optional. If digilocker.gov.in 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