Reliance Industries: 37 of 100 on Ora's agent-readiness scan
In short
Reliance Industries scores 37 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. A robots.txt that is an HTML page, in front of 93,890 characters of home page.
The score
Reliance Industries is an energy, retail and telecommunications conglomerate based in Mumbai.
- 37of 100, grade DOra's agent-readiness scan of ril.com, read 9 November 2026.
- 5Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 24Access, of 52Whether 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.
25 percent of the 132,085 domains Ora ranks score under 30, 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 | Partial, 1 of 2 | robots.txt answered an HTML page instead of rules. Crawlers find no rules in it and read the whole site, so your AI crawler policy is not stated. Serve a plain-text robots.txt |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: HTML returned instead of robots.txt |
| Content without JavaScript | Partial, 2 of 3 | Homepage: 93890 chars with H1, but heading hierarchy skips H2 to H4. 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 | Fail, 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness | Fail, 0 of 2 | No JSON-LD found - Organization schema missing |
| Sitemap exists | Pass, 2 of 2 | Valid sitemap found at /sitemap.xml with 178 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 6 measured pages fit an agent context budget (largest ~24K 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 | Partial, 1 of 3 | Documentation found at /docs but not 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 /docs |
| 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 1 of 1 same-origin script bundle(s) for modelContext registrations) |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q908931 (Reliance Industries Limited) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Partial, 1 of 3 | ril.com ranks #4 for "Reliance Industries Limited" |
| 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 1 of 1 same-origin script bundle(s) for modelContext registrations).
Our read
Reliance Industries lets every agent in, and then hands them a robots.txt that is an HTML page: crawlers find no rules in it, so the AI crawler policy is unstated and the user-agent permission row cannot be verified. The home page is 93,890 characters with an H1 and a heading hierarchy that jumps from H2 to H4, five of five inner pages read without JavaScript, the sitemap lists 178 entries and the metadata is complete, but there is no JSON-LD at all, so the Organization row is empty. Ora found a developer portal at /docs that the home page does not link to, with no public API, OpenAPI specification, MCP server or OAuth behind it, so the Usability layer reads 11 of 39. Discovery is 5 of 12: Wikidata confirms the domain, Wikipedia does not, and ril.com ranks fourth for its own name. A robots.txt that is text and an Organization block are two rows a web team can ship in a week; the public API is the long one.
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 ril.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 ril.com (ora.ai/score/ril.com), read 9 Nov 2026. Vendor claim.
Last reviewed