--- title: "Foxconn: 31 of 100 on Ora's scan | Am I Ready for Agents?" description: "Foxconn scores 31 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/foxconn-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Foxconn: 31 of 100 on Ora's scan | Am I Ready for Agents? > Foxconn scores 31 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/foxconn-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Foxconn: 31 of 100 on Ora's agent-readiness scan ## In short Foxconn scores 31 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. Zero characters without JavaScript, a sitemap that will not parse, an llms.txt in HTML. ## The score Foxconn is a contract electronics manufacturer based in Taiwan, formally Hon Hai Precision Industry. - 31of 100, grade D Ora's agent-readiness scan of foxconn.com, read 9 November 2026. - 7Discovery, of 13 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 9Access, of 54 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 15Usability, of 48 Whether they can act through it: an MCP server, an API with a specification, sign-in for agents. - 0Payments, of 0 No 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 | 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://foxconn.com/. Declared policy only; | | Content without JavaScript | Partial, 1 of 3 | Homepage: The homepage has little text without JavaScript (0 chars), though nothing in it shows it needs JavaScript to render. No inner pages checked: the scan found none to sample. | | 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 | Partial, 0 of 1 | A file is present at https://foxconn.com/llms.txt, but it returns an HTML page rather than a plain-text 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 | Partial, 1 of 2 | Sitemap found at /sitemap.xml but XML parsing failed | | Metadata completeness | Fail, 0 of 2 | No metadata signals found - missing: canonical URL, HTML lang attribute, og:image, og:type | | Page token budget | Pass, 1 of 1 | All 1 measured page 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 | Fail, 0 of 6 | No developer portal found | | OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://sso.foxconn.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 Q463094 (Q463094) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage | | Brand name discoverability | Partial, 2 of 3 | foxconn.com ranks #6 for "foxconn" and appears 3 times in the top 10 | | 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. 1. Public API with reachable endpoints, worth about 6.5 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated). 2. MCP server / manifest, worth about 5.6 points by Ora's estimate: No MCP server or manifest found. 3. Developer resource discoverability, worth about 5.1 points by Ora's estimate: In a search for your API docs, none of the 10 results is your official docs. ## Our read Foxconn's home page gives an agent nothing to read: zero characters of text without JavaScript, although nothing in the page shows it needs JavaScript to render. The door is open, with all four agent user agents reaching foxconn.com and robots.txt allowing the search and training crawlers, but there is no JSON-LD, the metadata carries none of its four signals, the sitemap at /sitemap.xml fails to parse and the llms.txt at foxconn.com/llms.txt returns an HTML page, so the Access layer reads 9 of 54. The act layer is one surface, OpenID Connect discovery at sso.foxconn.com, with neither a public API nor a developer portal, and no OpenAPI specification or MCP server, so the Usability layer reads 15 of 48. The domain ranks sixth for foxconn and appears three times in the top ten, and the Wikidata item is confirmed without a Wikipedia match. The company that assembles the world's phones has a site those phones' assistants cannot read; the template is where the D moves. ## Test your own site Run the same scan on your own domain at [ora.ai](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check). The score, the layers and the fixes on this page come from its public result for foxconn.com; a scan of a public site takes a few minutes and needs no account. - [Scan your domain on Ora](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check)The same checks, the same scoring, on your own site. - [The self-check, 18 questions](https://amireadyforagents.com/self-check)What to ask for, in business terms, before the scan. - [All the 360 checks](https://amireadyforagents.com/blog)The other companies in this series, newest first. ## Sources 1. [Ora report for foxconn.com](https://ora.ai/score/foxconn.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/foxconn.com), read 9 Nov 2026. Vendor claim. Last reviewed 9 November 2026 Reviewed 9 November 2026. [1 source](#sources), each with the day it was read.