--- title: "LinkedIn agent readiness: the 360 check | Agent Ready Crawlers" description: "LinkedIn on Ora's agent-readiness scan, read 2026-11-09: 48 of 100, grade C. The door, what agents can read and do, the fixes worth most." canonical: https://agentreadycrawlers.com/blog/linkedin-agent-readiness site: "Agent Ready Crawlers" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # LinkedIn agent readiness: the 360 check | Agent Ready Crawlers > LinkedIn on Ora's agent-readiness scan, read 2026-11-09: 48 of 100, grade C. The door, what agents can read and do, the fixes worth most. Source: https://agentreadycrawlers.com/blog/linkedin-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 # LinkedIn: the 360 agent-readiness check In short LinkedIn scores 48 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). 18 of 77 applicable checks pass; the gap worth most is MCP server / manifest. An open server, a real developer portal, and a robots.txt that is an HTML page. LinkedIn is Microsoft's professional network, with more than a billion members. On 9 November 2026 its public site scored **48 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C. 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: LinkedIn offers a published developer API and SDK packages, but lacks an OpenAPI specification for machine-readable endpoint discovery. ## The score | Layer | Asks | Points | Share | | --- | --- | --- | --- | | Discovery | Can agents find and recommend it | 13 of 17 | 76% | | Access | Can agents read it | 23 of 55 | 42% | | Usability | Can agents use it | 23 of 60 | 38% | | Payments | Can agents pay | 0 of 0 | none apply | | Total | Grade C | 48 of 100 | 48% | ** 18 checks pass, 13 are partial, 46 fail and 55 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. 1 check in this group does not apply to this site and is left out. 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/). | 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 | 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 | | Content behind auth | Partial | 1 of 2 | Some sampled pages are auth-gated: 1 returns 401/403 (https://www.linkedin.com/login) | | 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 | 1 of 3 | Homepage: 4220 chars with H1, but 4.2% content ratio is below the 5% target. Sampled pages with almost no text without JavaScript (1 of 3): https://www.linkedin.com/games/zip/ (85 chars). | | Page token budget | Pass | 1 of 1 | All 4 measured pages fit an agent context budget (largest ~1K 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://linkedin.com/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: og:image | | 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. 2 checks in this group do not apply to this site and are left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Public API with reachable endpoints | Partial | 3 of 7 | API described in documentation at https://developer.linkedin.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://developer.linkedin.com | | Developer portal | Pass | 6 of 6 | Developer portal found at https://developer.linkedin.com | | OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found | | API catalog (RFC 9727) | Partial | 1 of 2 | api-catalog responded but body is not valid JSON | | 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 | | A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json | | Agent discovery file | Pass | 2 of 2 | Agent discovery file found at /skills.sh | | OAuth 2.0 support | Partial | 3 of 5 | OAuth mentioned in documentation at https://developer.linkedin.com but no OAuth or OpenID Connect endpoint responded | | 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 | | NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST | | CLI tool available | Fail | 0 of 3 | No CLI tool found | | Multi-language SDK packages | Partial | 1 of 3 | SDK package found only in npm | | 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. 2 checks in this group do not apply to this site and are left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Brand name discoverability | Partial | 1 of 3 | linkedin.com ranks #6 for "LinkedIn" (searched your brand name alone: no main product term from your homepage qualified) | | Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "LinkedIn" and Wikidata Q213660 both verified - domain confirmed on both sources | | 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. | | NPM/PyPI SDK package | Pass | 1 of 1 | An official SDK or CLI on NPM or PyPI gives agents and the developers steering them a ready-made way in, instead of hand-rolling every API call. | | ChatGPT app listed | Pass | 2 of 2 | Listed in the ChatGPT app directory, where hundreds of millions of users can pull your product into a conversation by name. Upside-only: the directory is curated and gated, so absence never costs points. | | Listed on skills.sh | Fail | 0 of 1 | No official skills self-published on skills.sh (91 community skills with potential relation to this domain found, but only self-published official skills count) | | ARD discovery | Partial | 0 of 1 | /.well-known/ard.json exists but is not valid 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 LinkedIn, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog. MCP server / manifest Fail, 0 of 6, about 4.4 points to gain. Ora saw: No MCP server or manifest found OpenAPI spec published Fail, 0 of 7, about 4.2 points to gain. Ora saw: No OpenAPI/Swagger specification found Scoped permissions Fail, 0 of 5, about 3.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found WebMCP support Fail, 0 of 5, about 3.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found MCP Apps support Fail, 0 of 4, about 3 points to gain. Ora saw: No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render. ## Our read LinkedIn's door is open and its robots.txt is missing: all four of Ora's test agents reached the home page, but the request for robots.txt returned an HTML page instead of rules, so Ora could read no crawler policy at all and scored both robots checks as unverifiable. The home page gives 4,220 characters with an H1 at a content ratio of 4.2 percent, sampled pages carry almost no text without JavaScript, one sampled page is the login wall, and there is no JSON-LD, no sitemap and no llms.txt. The developer portal at developer.linkedin.com is real and earns the documentation checks, with an npm package beside it, though no OAuth endpoint answered and no OpenAPI specification was found. A C at 48 for Microsoft's professional network rests on a portal and an open server; a robots.txt that is a text file would be the cheapest point on the page. ## 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 linkedin.com, GET /api/score (vendor)](https://ora.ai/api/score/linkedin.com?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 - [LinkedIn home page](https://www.linkedin.com/) 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