80/100 B #116 of 1187
Audited November 16, 2026 from public surfaces only. Can AI agents discover, read, and act on cloud.microsoft? 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 (a web page was served in its place), 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 ~1219 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 Reached from homepage: pricing, support/contact, 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 |
1 check cost cloud.microsoft points. Each one below is the specific remedy for what we measured, not general advice.
Serve a plain-text file at https://cloud.microsoft/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.
Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on cloud.microsoft through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.
Optional. If cloud.microsoft has a public API, publishing an OpenAPI document at /openapi.json lets an agent call it correctly without a human reading your docs first.
Down 5 points since October 7. Every audit is a fresh fetch, so a change here means something on cloud.microsoft changed.
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