Dell Technologies: 74 of 100 on Ora's agent-readiness scan
In short
Dell Technologies scores 74 of 100 on Ora's agent-readiness scan, grade B, read on 9 November 2026. 93 percent of the 132,085 domains Ora ranks score under 70, and the average score is 44. The series' first B, with a soft 404 and a bot shield that answered the probes.
The score
Dell Technologies is a computer and infrastructure maker based in Round Rock, Texas.
- 74of 100, grade BOra's agent-readiness scan of dell.com, read 9 November 2026, listed under Identity & Auth.
- 14Discovery, of 15Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 39Access, of 46Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 25Usability, of 45Whether 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.
93 percent of the 132,085 domains Ora ranks score under 70, and the average score is 44.
Ora's one-line summary: Dell offers strong API discovery and documentation infrastructure, but lacks declared OAuth scopes for secure agent access.
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 (ChatGPT-User, OAI-SearchBot, PerplexityBot). Can't verify Claude-User. A bot shield, rate limit, or timeout stopped our test request. |
| Agent crawler reachability | Pass, 2 of 2 | Reachable to ChatGPT-User, OAI-SearchBot, 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://dell.com/. Declared policy only; |
| Content without JavaScript | Partial, 2 of 3 | 3252 chars with H1, but first content heading is H2, not H1; 3.2% content ratio is below the 5% target |
| 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 | Pass, 1 of 1 | Found the llms.txt at https://developer.dell.com/llms.txt. |
| llms.txt formatting | Partial, 1 of 2 | The llms.txt is well-formatted with markdown links, but at 90,245 characters it exceeds the 30,000-character recommendation for a navigation index. |
| Markdown agent docs | Did not apply, 0 of 1 | Can't verify: a bot shield answered our request to dell.com/ (HTTP 403) instead of the site. That is not counted against the site. |
| Bot-UA markdown serving | Did not apply, 0 of 1 | Can't verify: a bot shield answered our request to dell.com/ (HTTP 403) instead of the site. That is not counted against the site. |
| JSON-LD structured data | Pass, 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (3 block(s)) |
| Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: contactPoint |
| Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.dell.com/index-deals-href-sitemap.xml.gz with multiple sitemaps 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 1 measured page fit an agent context budget (largest ~1K tokens) |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Partial, 2 of 6 | MCP mentioned at https://www.dell.com/community/en/conversations/dell-openmanage-enterprise/ome-47-mcp-server-client-configuration-and-supported-mcp-clients-claudeai/6a3823bd172f524e9cfda3f8 but no standard manifest. |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Partial, 3 of 7 | Documentation site found at https://developer.dell.com but API content unclear. Best-of-protocols score: 3/7. |
| Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developer.dell.com |
| OpenAPI spec published | Did not apply, 0 of 7 | Can't verify: a bot shield answered our request to dell.com/.well-known/openapi.json (HTTP 403); dell.com/openapi.json (HTTP 403) instead of the site. That is not counted against the site. |
| Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developer.dell.com |
| OAuth 2.0 support | Partial, 2 of 5 | OAuth mentioned on homepage but no standard endpoints found |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Did not apply, 0 of 3 | SDK package found only in npm |
| CLI tool available | Did not apply, 0 of 3 | No CLI tool found |
| WebMCP support | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to dell.com/docs (HTTP 403); dell.com/docs/api (HTTP 403) instead of the site. That is not counted against the site. |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Dell Latitude" and Wikidata Q30873 both verified - domain confirmed on both sources |
| Brand name discoverability | Pass, 3 of 3 | dell.com ranks #3 for "Dell computer hardware" |
| 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 | Pass, 3 of 3 | Agent discovered 1 developer-resource type by name (developer portal) across 2 pages |
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.
- Scoped permissions, worth about 4.9 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
- MCP server / manifest, worth about 4 points by Ora's estimate: MCP mentioned at https://www.dell.com/community/en/conversations/dell-openmanage-enterprise/ome-47-mcp-server-client-configuration-and-supported-mcp-clients-claudeai/6a3823bd172f524e9cfda3f8 but no standard manifest endpoint found.
- Public API with reachable endpoints, worth about 4 points by Ora's estimate: Documentation site found at https://developer.dell.com but API content unclear. Best-of-protocols score: 3/7.
Our read
Dell Technologies is the first B in this series, carried by an Access layer of 39 of 46. ChatGPT-User, OAI-SearchBot and PerplexityBot reach dell.com, robots.txt allows the search and training crawlers, the home page gives 3,252 characters with an H1, the JSON-LD is a full Organization with description, sameAs, logo and address, the sitemap and metadata are complete and an llms.txt sits at developer.dell.com; a bot shield answered the markdown and OpenAPI probes with 403, not counted against the site. The act layer is a portal, developer.dell.com, with an SDK on npm, an MCP mention Ora could not resolve into a server, OAuth mentioned without standard endpoints and no declared scopes, so the Usability layer reads 25 of 45. One row is worth fixing on its own: nonexistent paths return 200 with the app shell, a soft 404 that tells a probing agent every file exists. The Wikipedia match landed on Dell Latitude rather than the company. Declared OAuth scopes are the fix Ora values most, at about 4.9 points.
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 dell.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.
Sources
- Ora report for dell.com (ora.ai/score/dell.com), read 9 Nov 2026. Vendor claim.
Last reviewed