--- title: "UnitedHealth Group: 64 of 100 on Ora's scan | Am I Ready for Agents?" description: "UnitedHealth Group scores 64 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/unitedhealth-group-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # UnitedHealth Group: 64 of 100 on Ora's scan | Am I Ready for Agents? > UnitedHealth Group scores 64 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/unitedhealth-group-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # UnitedHealth Group: 64 of 100 on Ora's agent-readiness scan ## In short UnitedHealth Group scores 64 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. An llms.txt in HTML, an ard.json that will not parse, and a soft 404. ## 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. | Check | Result | What Ora saw | | --- | --- | --- | | Not blocked by bot detection | Pass, 2 of 2 | Site accessible to 3 agent user-agents (OAI-SearchBot, Claude-User, PerplexityBot). Can't verify ChatGPT-User. A bot shield, rate limit, or timeout stopped our test request. | | Agent crawler reachability | Pass, 2 of 2 | Reachable to OAI-SearchBot, Claude-User, PerplexityBot. A bot shield, rate limit, or timeout stopped our test request. Real crawlers come from their own networks and may get through. | | robots.txt AI crawler policy | Pass, 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. | | robots.txt agent-user policy | Pass, 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://unitedhealthgroup.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | Homepage: 2545 chars with H1, but heading hierarchy skips H1 to H4. 4 of 4 sampled inner pages have text without JavaScript. | | Homepage not hidden from search | Pass, 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. | ## 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://unitedhealthgroup.com/.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 (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. | | JSON-LD structured data | Partial, 1 of 4 | JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is | | Organization schema completeness | Fail, 0 of 2 | No Organization type found in JSON-LD | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.unitedhealthgroup.com/content/uhg/en.sitemap.xml with 902 entries | | Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type | | Page token budget | Pass, 1 of 1 | All 5 measured pages fit an agent context budget (largest ~1K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Did not apply, 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 | Did not apply, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) | | Public API/docs linked from homepage | Did not apply, 0 of 3 | No public API or documentation page linked from homepage | | OpenAPI spec published | Did not apply, 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://sso.unitedhealthgroup.com | | 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 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 10 of 10 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "UnitedHealth Group" and Wikidata Q2103926 both verified - domain confirmed on both sources | | Brand name discoverability | Partial, 1 of 3 | unitedhealthgroup.com ranks #6 for "UnitedHealth Group" (searched your brand name alone: no main product term from your homepage qualified) | | 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 | Did not apply, 0 of 3 | In a search for your API docs, none of the 10 results is your official docs | 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](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check). 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 Ora](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check)The same checks, the same scoring, on your own site. - [The self-check, 18 questions](https://amireadyforagents.com/self-check)What to ask for, in business terms, before the scan. - [All the 360 checks](https://amireadyforagents.com/blog)The other companies in this series, newest first. ## Sources 1. [Ora report for unitedhealthgroup.com](https://ora.ai/score/unitedhealthgroup.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/unitedhealthgroup.com), read 9 Nov 2026. Vendor claim. Last reviewed 9 November 2026 Reviewed 9 November 2026. [1 source](#sources), each with the day it was read.