Procter & Gamble: 40 of 100 on Ora's agent-readiness scan
In short
Procter & Gamble scores 40 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 two-letter domain whose developer rows belong to another company entirely.
The score
Procter & Gamble is a consumer goods company based in Cincinnati, the maker of Tide, Pampers and Gillette.
- 40of 100, grade DOra's agent-readiness scan of pg.com, read 9 November 2026.
- 3Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 32Access, of 57Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 17Usability, of 49Whether 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.
Ora's one-line summary: pg.com has a public API with reachable endpoints, but lacks an OpenAPI specification.
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 6 AI agent user-agents |
| Agent crawler reachability | Pass, 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable |
| robots.txt AI crawler policy | Pass, 1 of 2 | robots.txt allows all crawlers (e.g. User-agent: * + Allow: /) - open by default but declares no AI-crawler tier differentiation |
| robots.txt agent-user policy | Pass, 2 of 2 | No robots.txt restriction on user-triggered agents - they can read the site |
| Content without JavaScript | Pass, 2 of 3 | 1311 chars with H1 but flat heading structure |
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://help.zscaler.com/llms.txt. |
| llms.txt formatting | Partial, 1 of 2 | The llms.txt is well-formatted with markdown links, but at 832,842 characters it exceeds the 30,000-character recommendation for a navigation index. |
| 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 (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. |
| JSON-LD structured data | Partial, 2 of 4 | JSON-LD has Organization type but missing key fields (name, description) |
| Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: address |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| 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 ~14K 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 | Partial, 3 of 7 | Documentation site found at https://help.zscaler.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://help.zscaler.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://help.zscaler.com |
| OAuth 2.0 support | Fail, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| 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 | No SDK packages found across language ecosystems |
| CLI tool available | Pass, 3 of 3 | CLI package found on npm: pg-cli |
| WebMCP support | Fail, 0 of 2 | No WebMCP support detected - no tool-attribute forms and 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 | Fail, 0 of 4 | No Wikipedia article or Wikidata entity found for "pg" - creating a Wikipedia page and a Wikidata item with P856 = pg.com is the highest-impact step for AI search citation coverage |
| Brand name discoverability | Pass, 2 of 3 | pg.com appears 2 times in brand-name search results for "Procter & Gamble" (top position: #6) |
| 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 6 | Agent searched for "pg" developer resources but found nothing relevant |
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.
- Developer resource discoverability, worth about 11.1 points by Ora's estimate: Agent searched for "pg" developer resources but found nothing relevant.
- MCP server / manifest, worth about 5.4 points by Ora's estimate: No MCP server or manifest found.
- OAuth 2.0 support, worth about 4.5 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.
Our read
Procter & Gamble's read is in two parts, and one of them belongs to someone else. The site itself is open: six AI agent user agents reach pg.com, robots.txt allows every crawler, the home page gives 1,311 characters with an H1, the metadata is complete and the Organization block has its type but no name or description; there is no sitemap, so the Access layer reads 32 of 57. The act layer as Ora recorded it points at help.zscaler.com for the llms.txt, the documentation and the developer portal, which is not Procter & Gamble's property, and the CLI it found on npm is pg-cli, a Postgres tool; the Usability layer of 17 of 49 is really empty. The Discovery layer is 3 of 12 for the same reason: the probe searched for pg and found nothing for a two-letter string. An Organization block with the company's name and a sameAs link would give every probe the right name to search for.
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 pg.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 pg.com (ora.ai/score/pg.com), read 9 Nov 2026. Vendor claim.
Last reviewed