--- title: "The New Yorker agent readiness: the 360 check | Agent Ready Crawlers" description: "The New Yorker on Ora's agent-readiness scan, read 2026-11-13: 42 of 100, grade D. The door, what agents can read and do, the fixes worth most." canonical: https://agentreadycrawlers.com/blog/newyorker-agent-readiness site: "Agent Ready Crawlers" last_updated: 2026-11-13 date: 2026-11-13 section: "360 checks" --- # The New Yorker agent readiness: the 360 check | Agent Ready Crawlers > The New Yorker on Ora's agent-readiness scan, read 2026-11-13: 42 of 100, grade D. The door, what agents can read and do, the fixes worth most. Source: https://agentreadycrawlers.com/blog/newyorker-agent-readiness Site: Agent Ready Crawlers Last reviewed: 2026-11-13 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, 13 November 2026 # The New Yorker: the 360 agent-readiness check In short The New Yorker scores 42 of 100 on Ora's agent-readiness scan, a D, read 13 November 2026. At the door, some agents blocked: ClaudeBot, PerplexityBot, Applebot-Extended. 10 of 60 applicable checks pass; the gap worth most is WebMCP support, about 10.6 points by Ora's estimate. ChatGPT-User reads the magazine; the Claude and Perplexity agents are turned away by name. The New Yorker is the Condé Nast weekly of reporting, criticism and fiction. On 13 November 2026 its public site scored **42 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a D. 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 125 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: The New Yorker offers native interactive controls, but lacks WebMCP support. ## The score | Layer | Asks | Points | Share | | --- | --- | --- | --- | | Discovery | Can agents find and recommend it | 1 of 6 | 17% | | Access | Can agents read it | 17 of 39 | 44% | | Usability | Can agents use it | 11 of 21 | 52% | | Payments | Can agents pay | 0 of 0 | none apply | | Total | Grade D | 42 of 100 | 42% | ** 10 checks pass, 10 are partial, 40 fail and 64 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/), [Claude-User](https://agentreadycrawlers.com/crawlers/claude-user/), [Claude-SearchBot](https://agentreadycrawlers.com/crawlers/claude-searchbot/), [PerplexityBot](https://agentreadycrawlers.com/crawlers/perplexitybot/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/), [ClaudeBot](https://agentreadycrawlers.com/crawlers/claudebot/). | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Not blocked by bot detection | Partial | 1 of 2 | Some agents blocked: ClaudeBot, PerplexityBot, Applebot-Extended | | Agent crawler reachability | Partial | 0 of 2 | Some AI crawlers are blocked - ChatGPT-User: reachable, ClaudeBot: blocked, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable | | robots.txt AI crawler policy | Partial | 0 of 2 | AI crawlers actively blocked: claudebot, claude-searchbot, perplexitybot, google-extended, applebot-extended - this hurts AEO/GEO discoverability | | robots.txt agent-user policy | Partial | 1 of 2 | Some user-triggered agents blocked (claude-user, perplexity-user); reachable for chatgpt-user | | 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. 1 check in this group does not apply to this site and is left out. | Check | Result | Points | What Ora saw | | --- | --- | --- | --- | | Content without JavaScript | Partial | 2 of 3 | 11404 chars with H1, but heading hierarchy skips H1 to H3; 3.7% content ratio is below the 5% target | | Page token budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~3K tokens) | | Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.newyorker.com/sitemap.xml with multiple sitemaps entries | | Sitemap freshness (lastmod) | Pass | 1 of 1 | Dates in your sitemap tell agents what changed and when, so they reread fresh pages instead of guessing. We check lastmod dates parse and the newest is recent. | | 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://newyorker.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 (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. | | Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) | | JSON-LD structured data | Partial | 2 of 4 | JSON-LD has Organization type but missing key fields (name, description) | | Organization schema completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address | | JSON-LD entity linking (sameAs) | Fail | 0 of 2 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand | | Schema type breadth | Partial | 1 of 2 | Some extended schema types found: ItemList - add FAQPage, Service, or AggregateRating for full coverage | | Metadata completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en-US", og:image, og:type | | 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. 11 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 tool-attribute forms and 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 | ## Found and recommended Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 4 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 | newyorker.com appears once in brand-name search results for "The New Yorker" (position #4 out of 7) | | Wikipedia / Wikidata entity presence | Unverified | 0 of 4 | Wikipedia and Wikidata presence could not be verified - try rescanning | | 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 (28 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 (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 The New Yorker, 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 10.6 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations) MCP Apps support Fail, 0 of 4, about 8.5 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. Brand name discoverability Partial, 1 of 3, about 7.4 points to gain. Ora saw: newyorker.com appears once in brand-name search results for "The New Yorker" (position #4 out of 7) robots.txt AI crawler policy Partial, 0 of 2, about 7.4 points to gain. Ora saw: AI crawlers actively blocked: claudebot, claude-searchbot, perplexitybot, google-extended, applebot-extended - this hurts AEO/GEO discoverability ChatGPT app listed Fail, 0 of 2, about 4.6 points to gain. Ora saw: Not found in ChatGPT app directory ## Our read The New Yorker keeps a door that opens for some agents and shuts for others. Bot detection blocked ClaudeBot, PerplexityBot and Applebot-Extended while ChatGPT-User, Google-Extended and DeepSeekBot reached the page, and robots.txt puts the policy in writing: claudebot, claude-searchbot, perplexitybot, google-extended and applebot-extended are actively blocked, and among the user-triggered agents claude-user and perplexity-user are shut out while chatgpt-user is reachable. The Access layer reads 17 of 39. For the agents that get in, the reading is decent: the home page gives 11,404 characters without JavaScript under an H1, though the headings skip from H1 to H3 and the content ratio sits at 3.7 percent; a valid sitemap is in place and the metadata is complete. There is no llms.txt, and the JSON-LD names an Organization without its name or description. The act layer is bare, with neither an MCP server nor a public API. The fix worth most is WebMCP, about 10.6 points. A D at 42: one assistant reads the magazine, and the rest read its robots.txt. ## 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 newyorker.com, GET /api/score (vendor)](https://ora.ai/api/score/newyorker.com?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-13 - [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 - [The New Yorker home page](https://www.newyorker.com/) read 2026-11-13 - [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-13