Alphabet: 17 of 100 on Ora's agent-readiness scan
In short
Alphabet scores 17 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44. A one-page holding company site the scan could not fetch, searched under the name abc.
The score
Alphabet is the parent company of Google; its own corporate site is a short page of filings and letters.
- 17of 100, grade FOra's agent-readiness scan of abc.xyz, read 9 November 2026.
- 0Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 7Access, of 45Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 8Usability, of 31Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
2 percent of the 132,085 domains Ora ranks score under 10, and the average score is 44.
Ora's one-line summary: Supports OAuth 2.0, but lacks an OpenAPI specification.
What an assistant meets at the door
Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.
| Check | Result | What Ora saw |
|---|---|---|
| Not blocked by bot detection | error, 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Fail, 0 of 2 | No major AI crawler can reach the homepage - ChatGPT-User: unknown, ClaudeBot: unknown, Google-Extended: unknown, ora-agent: unknown, DeepSeekBot: unknown |
| robots.txt AI crawler policy | Fail, 0 of 2 | No robots.txt found |
| robots.txt agent-user policy | Pass, 2 of 2 | No robots.txt restriction on user-triggered agents - they can read the site |
| Content without JavaScript | error, 0 of 3 | Could not fetch homepage |
What it can read, and what it can do
The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.
| Check | Result | What Ora saw |
|---|---|---|
| llms.txt exists | Partial, 0 of 1 | A file is present at https://abc.xyz/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | Fail, 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md). |
| Bot-UA markdown serving | Fail, 0 of 1 | No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. |
| JSON-LD structured data | error, 0 of 4 | Could not fetch homepage |
| Organization schema completeness | error, 0 of 2 | Could not fetch homepage |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| Metadata completeness | error, 0 of 2 | Could not fetch homepage |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Fail, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage | Fail, 0 of 3 | No public API or documentation page linked from homepage |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Did not apply, 0 of 6 | No developer portal found |
| OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://abc.xyz |
| Scoped permissions | Did not apply, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Did not apply, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 2 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Fail, 0 of 4 | No Wikipedia article or Wikidata entity found for "abc" - creating a Wikipedia page and a Wikidata item with P856 = abc.xyz is the highest-impact step for AI search citation coverage |
| Brand name discoverability | Fail, 0 of 3 | "abc" search returned 6 results but domain did not appear - brand may be too generic or not indexed |
| Category share of voice | Did not apply, 0 of 6 | Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name). |
| Developer resource discoverability | Fail, 0 of 6 | Agent searched for "abc" developer resources but found nothing relevant |
The six payment checks did not apply on this read: Ora did not read the site as a shop.
Three fixes to hand to the web team
Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.
- Developer resource discoverability, worth about 11.1 points by Ora's estimate: Agent searched for "abc" developer resources but found nothing relevant.
- Public API with reachable endpoints, worth about 10 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
- MCP server / manifest, worth about 8.6 points by Ora's estimate: No MCP server or manifest found.
Our read
Alphabet's corporate site is one page of filings and letters, and Ora could not fetch even that: the home page did not come back, the bot test could not run, and there is no robots.txt, so the door, content, policy and structured-data rows are unverified rather than failed, and the Access layer reads 7 of 45. Two things did answer: an OpenID Connect discovery endpoint at abc.xyz, and an llms.txt at /.well-known/llms.txt that returns an HTML page. The Discovery layer reads 0 of 12 because the probe searched for abc, found six results without the domain and no Wikipedia article for that string, which describes the probe more than the parent of Google. The act layer is empty by design, with no public API and no MCP server, and the Usability layer reads 8 of 31. A home page that answers would turn most of this F into a read; the fix with the most points, the developer search, is one this site was never meant to pass.
Test your own site
Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for abc.xyz; a scan of a public site takes a few minutes and needs no account.
- Scan your domain on OraThe same checks, the same scoring, on your own site.
- The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
- All the 360 checksThe other companies in this series, newest first.
Sources
- Ora report for abc.xyz (ora.ai/score/abc.xyz), read 9 Nov 2026. Vendor claim.
Last reviewed