Boeing: 66 of 100 on Ora's agent-readiness scan
In short
Boeing scores 66 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. The door open, the sitemap full, and a search for boeing that does not find it.
The score
Boeing is an aircraft and defence manufacturer based in Arlington, Virginia.
- 66of 100, grade COra's agent-readiness scan of boeing.com, read 9 November 2026.
- 10Discovery, of 14Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 20Access, of 36Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 15Usability, of 21Whether 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.
79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44.
Ora's one-line summary: Boeing's developer resources and crawler policy are discoverable, but it lacks WebMCP support and any agent-facing instruction file.
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 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability | Pass, 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| 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://boeing.com/. Declared policy only; |
| Content without JavaScript | Partial, 2 of 3 | Homepage: 5685 chars with H1, but first content heading is H3, not H1; heading hierarchy skips H1 to H3; 3.5% content ratio is below the 5% target. No inner pages checked: the scan found none to sample. |
| 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 | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/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, 3 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: contactPoint, address |
| Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.boeing.com/sitemap.xml with 1945 entries |
| Metadata completeness | Partial, 1 of 2 | 3/4 metadata signals present - missing: og:image |
| 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 | 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://auth.boeing.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 11 of 11 same-origin script bundle(s) for modelContext registrations) |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Boeing 777" and Wikidata Q66 both verified - domain confirmed on both sources |
| Brand name discoverability | Fail, 0 of 3 | boeing.com was not in the top 10 for "boeing" (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 | Pass, 3 of 3 | In a search for your API docs, your docs came up at #4 (https://developer.boeing.com/apis) |
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.
- WebMCP support, worth about 10.6 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 11 of 11 same-origin script bundle(s) for modelContext registrations).
- Brand name discoverability, worth about 4.8 points by Ora's estimate: boeing.com was not in the top 10 for "boeing" (searched your brand name alone: no main product term from your homepage qualified).
- Agent instruction / when-to-use, worth about 2.8 points by Ora's estimate: No agent instruction file with when-to-use guidance found.
Our read
Boeing's 66 is a C with the door wide open. All four agent user agents reach boeing.com, robots.txt allows the search and training crawlers, the sitemap lists 1,945 pages and the home page gives 5,685 characters with an H1, though the heading tree jumps from H1 to H3 and the text ratio is 3.5 percent against the 5 percent target; the Organization block lacks its description, the metadata lacks og:image, and there is no llms.txt, so the Access layer reads 20 of 36. The act layer is thin by nature for a planemaker, which is why the Usability layer has a maximum of 21 and the WebMCP estimate of 10.6 points means less than it looks; OpenID Connect discovery at auth.boeing.com is the one surface Ora found. The odd row is Discovery: boeing.com was not in the top ten for boeing, and the Wikipedia match landed on the 777 rather than the company. An Organization block with a sameAs link would tell the knowledge graph which Boeing this is.
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 boeing.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 boeing.com (ora.ai/score/boeing.com), read 9 Nov 2026. Vendor claim.
Last reviewed