45/100 D #664 of 1187
Audited November 16, 2026 from public surfaces only. Can AI agents discover, read, and act on ibps.in? Check by check:
robots.txt: could not be read, policy unknown
| 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 could not be read (HTTP no answer), so the site's AI policy is unknown. Scored as no rules, as RFC 9309 treats an unavailable file. |
15/15 | pass |
| A3 | Content readable without a browser Plain fetch of the homepage yields ~416 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 No sitemap found. |
0/10 | fail |
| A6 | Everyday agent tasks reachable from the homepage Reached from homepage: support/contact (/index.php/contact-us). |
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 |
4 checks cost ibps.in points. Each one below is the specific remedy for what we measured, not general advice.
Serve a plain-text file at https://ibps.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.
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 ibps.in is without inferring it from prose.
Serve https://ibps.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 ibps.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 ibps.in through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.
Optional. If ibps.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