UnitedHealth Group: 64 of 100 on Ora's agent-readiness scan

The score

UnitedHealth Group is a health insurer and health services group based in Minnesota, the parent of UnitedHealthcare and Optum.

• 64of 100, grade C
  Ora's agent-readiness scan of unitedhealthgroup.com, read 9 November 2026.
• 8Discovery, of 11
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 21Access, of 39
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 14Usability, of 21
  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.

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

Ora's one-line summary: UnitedHealth Group offers solid discovery and passes key crawler checks, but lacks WebMCP support and an agent instruction file for agents to use it reliably.

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. WebMCP support, worth about 10.6 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 10 of 10 same-origin script bundle(s) for modelContext registrations).
2. Agent-friendly 404s, worth about 4.2 points by Ora's estimate: Nonexistent paths return HTTP 200 with the app shell (soft-404). Agents probing for resources conclude every path exists. Return a real HTTP 404 status for unknown paths.
3. Brand name discoverability, worth about 4 points by Ora's estimate: unitedhealthgroup.com ranks #6 for "UnitedHealth Group" (searched your brand name alone: no main product term from your homepage qualified).

Our read

UnitedHealth Group lets OAI-SearchBot, Claude-User and PerplexityBot in; the ChatGPT-User probe was stopped by a shield, rate limit or timeout. The reading layer is mostly in order: 2,545 characters of home page with an H1, four of four inner pages readable without JavaScript, a 902-entry sitemap, complete metadata and an open robots.txt. Three files are the wrong shape. The llms.txt returns an HTML page, the JSON-LD block carries no identity type so the Organization row is empty, and /.well-known/ard.json is not valid JSON. Nonexistent paths return 200 with the app shell, which Ora scores as a soft 404. The act layer has one real row, an OpenID Connect discovery endpoint at sso.unitedhealthgroup.com, with no public API, developer portal or MCP server beside it, so the Usability layer reads 14 of 21. An insurer whose members ask assistants what their plan covers has three files that answer in the wrong format; fixing them is a week of work and most of the distance to a B.

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 unitedhealthgroup.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.