Meta: 51 of 100 on Ora's agent-readiness scan
In short
Meta scores 51 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44. The maker of Muse shows an agent 296 characters of its own home page.
The score
Meta is the parent of Facebook, Instagram and WhatsApp, and the maker of the Muse agent, based in Menlo Park.
- 51of 100, grade COra's agent-readiness scan of meta.com, read 9 November 2026, listed under Identity & Auth.
- 10Discovery, of 13Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 32Access, of 56Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 19Usability, of 55Whether 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.
60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44.
Ora's one-line summary: Meta offers strong developer documentation discoverability and llms.txt support, but lacks an OpenAPI specification and MCP server for agent integration.
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, Claude-User). Can't verify PerplexityBot. Your site also blocked a normal browser visit, so we can't tell if agents get in. |
| Agent crawler reachability | Pass, 2 of 2 | Reachable to ChatGPT-User, OAI-SearchBot, Claude-User. Your site also blocked a normal browser visit, so we can't tell if agents get in. |
| 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://meta.com/. Declared policy only; |
| Content without JavaScript | Partial, 1 of 3 | Homepage: Only 296 chars of text content - agents see limited content. Sampled pages with almost no text without JavaScript (1 of 4): https://www.meta.com/quest/ (103 chars). |
| 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://developers.meta.com/llms.txt. |
| llms.txt formatting | Pass, 2 of 2 | The llms.txt is well-formatted: 19 lines with markdown links, 1,724 characters in total. |
| 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 | Fail, 0 of 2 | No sitemap found |
| 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 ~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 | Partial, 3 of 7 | API described in documentation at https://developers.meta.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. |
| Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developers.meta.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer portal found at https://developers.meta.com |
| OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://auth.meta.com |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Fail, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q380 (Meta Platforms) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Partial, 2 of 3 | meta.com ranks #6 for "Meta" and appears 3 times in the top 10 (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 #9 (https://developers.meta.com). In a search for your MCP server, SDK or CLI, we found your CLI at #3 (https://developers.meta.com/vr/essentials/metavr-install) |
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.
- MCP server / manifest, worth about 4.8 points by Ora's estimate: No MCP server or manifest found.
- OpenAPI spec published, worth about 4.2 points by Ora's estimate: No OpenAPI/Swagger specification found.
- Scoped permissions, worth about 4 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
Our read
Meta built the Muse agent and a home page that shows an agent 296 characters. ChatGPT-User, OAI-SearchBot and Claude-User reach meta.com while PerplexityBot could not be verified; robots.txt allows the search and training crawlers, the metadata is complete, the Organization block lacks only its description and an llms.txt sits at developers.meta.com, but there is no sitemap, and three of four sampled pages had almost no text without JavaScript, so the Access layer reads 32 of 56. The act layer is a developer portal with the machine half missing: developers.meta.com documents an API with no machine-verifiable surface, OpenID Connect discovery answers at auth.meta.com, and Ora found neither an OpenAPI specification nor an MCP server, and no declared scopes, so the Usability layer reads 19 of 55. The domain ranks sixth for Meta and appears three times in the top ten. The company shipping an agent with its own browser has a site that browser would struggle to read; the template is the row to fix.
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 meta.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 meta.com (ora.ai/score/meta.com), read 9 Nov 2026. Vendor claim.
Last reviewed