---
title: "The Telegraph agent readiness: the 360 check | Agent Ready Crawlers"
description: "The Telegraph on Ora's agent-readiness scan, read 2026-11-09: 20 of 100, grade F. The door, what agents can read and do, the fixes worth most."
canonical: https://agentreadycrawlers.com/blog/telegraph-agent-readiness
site: "Agent Ready Crawlers"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# The Telegraph agent readiness: the 360 check | Agent Ready Crawlers

> The Telegraph on Ora's agent-readiness scan, read 2026-11-09: 20 of 100, grade F. The door, what agents can read and do, the fixes worth most.

Source: https://agentreadycrawlers.com/blog/telegraph-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

# The Telegraph: the 360 agent-readiness check

In short

The Telegraph scores 20 of 100 on Ora's agent-readiness scan, an F, read 9 November 2026. At the door, could not test bot user agents. 6 of 53 applicable checks pass; the gap worth most is Public API with reachable endpoints, about 11.5 points by Ora's estimate. The most permissive policy here, on a server that did not answer.

The Telegraph is a British broadsheet with a metered paywall. On 9 November 2026 its public site scored **20 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, an F. 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 124 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: telegraph.co.uk offers a robots.txt AI crawler policy, but lacks an OpenAPI specification.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 3 of 13 | 23% |
| Access | Can agents read it | 2 of 46 | 4% |
| Usability | Can agents use it | 8 of 27 | 30% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade F | 20 of 100 | 20% |

**

6 checks pass, 3 are partial, 44 fail and 63 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. 2 checks in this group do not apply to this site and are left out.

Agents named in Ora's results, with their Index rows: [ChatGPT-User](https://agentreadycrawlers.com/crawlers/chatgpt-user/), [ClaudeBot](https://agentreadycrawlers.com/crawlers/claudebot/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Unverified | 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Fail | 0 of 2 | No major AI crawler can reach the homepage - ChatGPT-User: unknown, ClaudeBot: unknown, Google-Extended: blocked, ora-agent: blocked, DeepSeekBot: blocked |
| robots.txt AI crawler policy | Pass | 1 of 2 | robots.txt allows all crawlers (e.g. `User-agent: *` + `Allow: /`) - open by default but declares no AI-crawler tier differentiation |
| robots.txt agent-user policy | Pass | 2 of 2 | No robots.txt restriction on user-triggered agents - they can read the site |
| 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. 3 checks in this group do not apply to this site and are left out.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript | Unverified | 0 of 3 | Could not fetch homepage |
| 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://telegraph.co.uk/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 | No agent mode view detected at ?mode=agent (optional) |
| JSON-LD structured data | Unverified | 0 of 4 | Could not fetch homepage |
| Organization schema completeness | Unverified | 0 of 2 | Company details (contact, address) in your structured data. AIs use them to verify you are a real business before recommending you. |
| JSON-LD entity linking (sameAs) | Unverified | 0 of 2 | sameAs links from your structured data to your official profiles (GitHub, LinkedIn, app stores). They let AIs confirm that every mention of you is actually you. |
| Schema type breadth | Unverified | 0 of 2 | The more kinds of content you mark up with schema.org (FAQs, reviews, services, events, videos), the more kinds of questions an AI can answer about you with confidence. |
| Metadata completeness | Unverified | 0 of 2 | Could not fetch homepage |
| 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. 6 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 | 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 |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| MCP server / manifest | Partial | 3 of 6 | MCP server listed in registry (Smithery, seamlesstax/calculator, 1546 uses) but no live MCP protocol handshake - add /.well-known/mcp or ensure the deployment responds to initialize |
| 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 2 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via 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. 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 | telegraph.co.uk appears once in brand-name search results for "telegraph" (position #6 out of 10) |
| Wikipedia / Wikidata entity presence | Unverified | 0 of 4 | Wikipedia and Wikidata presence could not be verified - try rescanning |
| Developer resource discoverability | Fail | 0 of 6 | Agent searched for "telegraph" developer resources but found nothing relevant |
| 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 | 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/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 Telegraph, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog.

Public API with reachable endpoints

Fail, 0 of 7, about 11.5 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)

Developer resource discoverability

Fail, 0 of 6, about 10.3 points to gain. Ora saw: Agent searched for "telegraph" developer resources but found nothing relevant

OpenAPI spec published

Fail, 0 of 7, about 5.1 points to gain. Ora saw: No OpenAPI/Swagger specification found

MCP server / manifest

Partial, 3 of 6, about 4.9 points to gain. Ora saw: MCP server listed in registry (Smithery, seamlesstax/calculator, 1546 uses) but no live MCP protocol handshake - add /.well-known/mcp or ensure the deployment responds to initialize

Brand name discoverability

Partial, 1 of 3, about 3.4 points to gain. Ora saw: telegraph.co.uk appears once in brand-name search results for "telegraph" (position #6 out of 10)

## Our read

The Telegraph is the odd one out: its robots.txt is the most permissive on this list, allowing every crawler with a plain wildcard and placing no restriction on user-triggered agents, yet Ora could not test the bot user agents at all and recorded Google-Extended as blocked and the rest as unknown, with the home page unfetched. The policy says come in; the server did not answer. With nothing read, the Access layer sits at 2 of 46 and the Discovery layer at 3 of 13, the Wikipedia and Wikidata checks unverified on this read and the brand sixth for its own name. Ora also matched a tax-calculator MCP server in a registry to the name, which counts for nothing real. No sitemap, no llms.txt, no API. An F at 20 for a broadsheet with an open policy is a hosting answer, and a rescan on a day the server responds would read differently.

## 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 telegraph.co.uk, GET /api/score (vendor)](https://ora.ai/api/score/telegraph.co.uk?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
-   [The Telegraph home page](https://www.telegraph.co.uk/) 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