--- title: "Wikipedia agent readiness: the 360 check | Agent Ready Crawlers" description: "Wikipedia on Ora's agent-readiness scan, read 2026-11-09: 65 of 100, grade C. The door, what agents can read and do, the fixes worth most." canonical: https://agentreadycrawlers.com/blog/wikipedia-agent-readiness site: "Agent Ready Crawlers" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Wikipedia agent readiness: the 360 check | Agent Ready Crawlers > Wikipedia on Ora's agent-readiness scan, read 2026-11-09: 65 of 100, grade C. The door, what agents can read and do, the fixes worth most. Source: https://agentreadycrawlers.com/blog/wikipedia-agent-readiness Site: Agent Ready Crawlers Last reviewed: 2026-11-09 Agent endpoints: https://agentreadycrawlers.com/llms.txt (index), https://agentreadycrawlers.com/openapi.json (API), https://agentreadycrawlers.com/mcp (MCP server), https://agentreadycrawlers.com/ask (search) Access: https://agentreadycrawlers.com/auth.md (no key). Pricing: https://agentreadycrawlers.com/pricing.md (free). 360 check, 9 November 2026 # Wikipedia: the 360 agent-readiness check In short Wikipedia scores 65 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. At the door, site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). 16 of 61 applicable checks pass; the gap worth most is WebMCP support. The scan reads the portal domain, not the language editions where the articles live. Wikipedia is the encyclopedia that every large model was trained on, run by the Wikimedia Foundation. On 9 November 2026 its public site scored **65 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C, in Ora's News & Intelligence category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. The check below walks through all 132 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: Wikipedia offers strong discoverability and clean robots.txt crawler policy, but lacks WebMCP support and JSON-LD structured data for agents. ## The score | Layer | Asks | Points | Share | | --- | --- | --- | --- | | Discovery | Can agents find and recommend it | 11 of 12 | 92% | | Access | Can agents read it | 13 of 37 | 35% | | Usability | Can agents use it | 17 of 23 | 74% | | Payments | Can agents pay | 0 of 0 | none apply | | Total | Grade C | 65 of 100 | 65% | ** 16 checks pass, 4 are partial, 41 fail and 71 do not apply to this site. Every check is defined in [Ora's catalog](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) (read 2026-11-05); the result for each one is in the groups below, with what Ora saw where it said. ## At the door What the site answers when a request arrives with an agent’s user agent, and what robots.txt says to the crawlers in the Index. Agents named in Ora's results, with their Index rows: [ChatGPT-User](https://agentreadycrawlers.com/crawlers/chatgpt-user/), [OAI-SearchBot](https://agentreadycrawlers.com/crawlers/oai-searchbot/), [Claude-User](https://agentreadycrawlers.com/crawlers/claude-user/), [PerplexityBot](https://agentreadycrawlers.com/crawlers/perplexitybot/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/). | Check | Result | Points | 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://wikipedia.org/. Declared policy only; | | Content behind auth | Pass | 2 of 2 | All 1 sampled page is publicly readable (1 with substantive content) | | 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. | | Redirect hygiene | Pass | 1 of 1 | Pages agents land on serve real content, not meta-refresh or JavaScript-only redirect stubs that strand non-JS agents | | Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found | ## What an agent can read Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them. 2 checks in this group do not apply to this site and are left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Content without JavaScript | Partial | 2 of 3 | Homepage: 4229 chars with H1, but heading hierarchy skips H1 to H3. 1 of 1 sampled inner page has text without JavaScript. | | Page token budget | Pass | 1 of 1 | All 2 measured pages fit an agent context budget (largest ~3K tokens) | | Sitemap exists | Fail | 0 of 2 | No sitemap found | | 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, | | Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://wikipedia.org/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). | | 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. | | Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) | | 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 | | JSON-LD entity linking (sameAs) | Fail | 0 of 2 | No JSON-LD found - no entity linking possible | | Schema type breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity | | Metadata completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: canonical URL | | Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found | ## What an agent can do The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, a command line. 10 checks in this group do not apply to this site and are left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) | | MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered | | A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json | | Agent discovery file | Fail | 0 of 2 | No agent discovery file found | | OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) | | auth.md exists | Fail | 0 of 2 | No /auth.md found at site root | | WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations) | | NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST | | JSON error responses | Pass | 4 of 4 | When something breaks, agents need a structured JSON error, not an HTML error page. One is recoverable, the other is a dead end. | ## Found and recommended Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 3 checks in this group do not apply to this site and are left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Brand name discoverability | Pass | 3 of 3 | wikipedia.org ranks #1 for "Wikipedia" (searched your brand name alone: no main product term from your homepage qualified) | | Wikipedia / Wikidata entity presence | Partial | 2 of 4 | Wikidata Q52 (Wikipedia) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage | | Developer resource discoverability | Pass | 3 of 3 | Can an agent find your developer resources with the searches it would really run? We search for your API docs and expect your own docs page among the results, then for your MCP server, SDK or CLI and, when you have one, expect your own page for it. Pages on other sites, including other companies with a similar name, don't count, unless your homepage or llms.txt links that site's docs, or your homepage redirects to a parent company's site and the page's address names your product. GitHub repos count only in an org your site links to. | | ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory | | Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (100 community skills with potential relation to this domain found, but only self-published official skills count) | | ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json | ## The fixes worth most points Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Wikipedia, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog. WebMCP support Fail, 0 of 5, about 9.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations) JSON-LD structured data Fail, 0 of 4, about 3.6 points to gain. Ora saw: No JSON-LD structured data found on homepage Agent instruction / when-to-use Fail, 0 of 3, about 2.7 points to gain. Ora saw: No agent instruction file with when-to-use guidance found Agent-friendly 404s Partial, 1 of 2, about 1.9 points to gain. Ora saw: The nonexistent path https://wikipedia.org/\_\_ora-404-probe-1byb5v3k correctly returns HTTP 404. Partial credit: no Markdown error body was detected. ARD discovery Fail, 0 of 1, about 1.9 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json ## Our read Wikipedia is the site every large model was trained on, and its door reads like it: all four of Ora's test agents reached the home page, robots.txt allows the AI search crawlers on three of three checks and the training crawlers on both, and places no restriction on the user-triggered agents. The Discovery layer at 11 of 12 and the Usability layer at 17 of 23 carry the C. What Ora marks down is the shape of the portal page: 4,229 characters with an H1 and a heading hierarchy that skips to H3, no JSON-LD, no sitemap at wikipedia.org itself, and API documentation at /api that the home page does not link. Ora's largest estimated gap, WebMCP, is a product-company check and beside the point here. A C at 65 for the encyclopedia is a reminder that the scan reads the portal domain, not the language editions where the sitemaps and the articles live. ## Check your own door The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then compare the door with the [Block Rate Report](https://agentreadycrawlers.com/block-rates/) for sites of your rank and kind. Our [guide to testing whether agents can reach your site](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) has the curl commands for a manual check, and the [robots.txt builder](https://agentreadycrawlers.com/robots-builder/) writes a policy file from the Index. Payments did not apply to this site; a site that sells would read that layer against the [vendors at the door](https://agentreadycrawlers.com/vendors/ranking/). [Scan your own domain on Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) [All 360 checks](https://agentreadycrawlers.com/blog/). One company a day; corrections to [the corrections page](https://agentreadycrawlers.com/corrections/). ** The check we recommend [Ora](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) scans a public URL: 16 Discovery checks and 42 Access checks, read from its catalog on 2026-11-05. Its Journey sends a real agent to the site. [How to run it](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/). **Limits.** Ora reads public URLs only, and what it records as blocked comes from its own network. It says the same scan run twice converges within a couple of points ([Ora's Deep Scan post](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)), and the pages we read give no repeat-scan figures. Its fixing product is behind a waitlist ([Ora's home page](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check)). ## Sources - [Ora's scan of wikipedia.org, GET /api/score (vendor)](https://ora.ai/api/score/wikipedia.org?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-09 - [Ora's scoring rules, version 2 (vendor)](https://ora.ai/api/ranker/releases/2/rules?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-09 - [Ora's check catalog, GET /api/checks (vendor)](https://ora.ai/api/checks?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05 - [Wikipedia home page](https://www.wikipedia.org/) read 2026-11-09 - [How to test whether AI agents can reach your site (this site)](https://agentreadycrawlers.com/guides/test-whether-ai-agents-can-reach-your-site/) read 2026-11-04 - [Ora: Deep Scan v2 (vendor)](https://ora.ai/blog/introducing-deep-scan?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05 - [Ora home page, waitlist (vendor)](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-05 Last reviewed 2026-11-09