Alibaba Group: 29 of 100 on Ora's agent-readiness scan

The score

Alibaba Group is an ecommerce and cloud group based in Hangzhou.

• 29of 100, grade D
  Ora's agent-readiness scan of alibabagroup.com, read 10 November 2026.
• 7Discovery, of 12
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 9Access, of 47
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 7Usability, of 32
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.

Ora's one-line summary: Serves agents almost nothing: the homepage is empty without JavaScript, with no public API, no OpenAPI spec and no structured data.

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.

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.

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.

1. Public API with reachable endpoints, worth about 9.7 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
2. WebMCP support, worth about 6.9 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
3. Developer resource discoverability, worth about 5.6 points by Ora's estimate: In a search for your API docs, none of the 10 results is your official docs.

Our read

Alibaba Group's corporate site hands an agent 30 characters. The home page is rendered by JavaScript, 100 percent script with almost no text; robots.txt answers with an HTML page instead of rules, so the crawler policy is not stated; the .well-known/llms.txt is an HTML page too; and unknown paths return 200 with the app shell, so an agent probing for files concludes every one exists. The door is open, all four test agents reached the site, which only means they arrived at an empty room. There is no sitemap and no JSON-LD, 1 of 4 metadata signals, and the act layer is bare: neither an API nor an OpenAPI specification, no OAuth, an MCP mentioned without a manifest, and a search for the group's API docs found none of the 10 results official. The brand search ran on the string alibabagroup, the probe's own reading. A D at 29 where the fix worth most, a public API at about 10 points, would sit behind a page that says nothing.

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 alibabagroup.com; 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.