Phillips 66: 45 of 100 on Ora's agent-readiness scan
In short
Phillips 66 scores 45 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. A refiner that reads well and does nothing, with a developer portal at /dashboard.
The score
Phillips 66 is a refiner, midstream and chemicals company based in Houston.
- 45of 100, grade DOra's agent-readiness scan of phillips66.com, read 9 November 2026.
- 8Discovery, of 14Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 32Access, of 55Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 11Usability, of 39Whether 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.
43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44.
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://phillips66.com/. Declared policy only; |
| Content without JavaScript | Partial, 2 of 3 | Homepage: 2558 chars with H1, but 3.2% content ratio is below the 5% target. 5 of 5 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 | 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.phillips66.com/sitemap_index.xml with multiple sitemaps entries |
| Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en-US", og:image, og:type |
| Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 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 | Fail, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage | Fail, 0 of 3 | No public API or documentation page linked from homepage |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer portal found at /dashboard |
| OAuth 2.0 support | Did not apply, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| 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 8 of 8 same-origin script bundle(s) for modelContext registrations) |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Phillips 66" and Wikidata Q1656230 both verified - domain confirmed on both sources |
| Brand name discoverability | Partial, 1 of 3 | phillips66.com ranks #6 for "Phillips 66" (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 | Fail, 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.
- Public API with reachable endpoints, worth about 8 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
- MCP server / manifest, worth about 6.8 points by Ora's estimate: No MCP server or manifest found.
- WebMCP support, worth about 5.7 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 same-origin script bundle(s) for modelContext registrations).
Our read
Phillips 66 opens its door to every agent Ora tested, and the reading layer mostly holds: 2,558 characters of home page with an H1, five of five inner pages readable without JavaScript, a valid sitemap index, complete metadata, and an Organization block that lacks only a description, a contactPoint and an address. There is no llms.txt, and the developer portal Ora found at /dashboard has no public API, OpenAPI specification, MCP server or OAuth behind it, so the Usability layer reads 11 of 39. Discovery is 8 of 14: Wikipedia and Wikidata both confirm the domain, and phillips66.com ranks sixth for its own name. The 45 is a D for a site that reads well and does nothing; the six fixes Ora lists are all act-layer rows. A description in the Organization block and an llms.txt are the cheap rows; the public API is a decision for the business rather than a ticket for the web team.
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 phillips66.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 phillips66.com (ora.ai/score/phillips66.com), read 9 Nov 2026. Vendor claim.
Last reviewed