--- title: "Daily Mail agent readiness: the 360 check | Agent Ready Crawlers" description: "Daily Mail on Ora's agent-readiness scan, read 2026-11-09: 38 of 100, grade D. The door, what agents can read and do, the fixes worth most." canonical: https://agentreadycrawlers.com/blog/dailymail-agent-readiness site: "Agent Ready Crawlers" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Daily Mail agent readiness: the 360 check | Agent Ready Crawlers > Daily Mail on Ora's agent-readiness scan, read 2026-11-09: 38 of 100, grade D. The door, what agents can read and do, the fixes worth most. Source: https://agentreadycrawlers.com/blog/dailymail-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 # Daily Mail: the 360 agent-readiness check In short Daily Mail scores 38 of 100 on Ora's agent-readiness scan, a D, read 9 November 2026. At the door, agents blocked: ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. 11 of 51 applicable checks pass; the gap worth most is Public API with reachable endpoints. A shut door, a readable page, and a brand its own search cannot find. Daily Mail is MailOnline, the most-visited English-language newspaper site for much of the last decade. On 9 November 2026 its public site scored **38 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 132 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: Turns agents away at the door: robots.txt disallows search and user agents, and bot detection blocks them outright. ## The score | Layer | Asks | Points | Share | | --- | --- | --- | --- | | Discovery | Can agents find and recommend it | 2 of 11 | 18% | | Access | Can agents read it | 18 of 35 | 51% | | Usability | Can agents use it | 8 of 21 | 38% | | Payments | Can agents pay | 0 of 0 | none apply | | Total | Grade D | 38 of 100 | 38% | ** 11 checks pass, 9 are partial, 31 fail and 81 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/), [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 | Fail | 0 of 2 | Agents blocked: ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A normal browser visit from us got in. | | Agent crawler reachability | Fail | 0 of 2 | No agent we tested can reach the homepage - ChatGPT-User: blocked, OAI-SearchBot: blocked, Claude-User: blocked, PerplexityBot: blocked. A normal browser visit from us got in. | | robots.txt AI crawler policy | Fail | 0 of 2 | AI search crawlers: allowed in 0 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 0 of 2 checks (2 crawlers on 1 page), not scored. robots.txt restricts 3/3 evaluated search page/crawler pairs. | | robots.txt agent-user policy | Fail | 0 of 2 | robots.txt restricts 3/3 evaluated page/crawler pairs. Checked 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page. Restricted: chatgpt-user at https://dailymail.co.uk/ (Disallow: /, | | 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: 48784 chars with H1, but heading hierarchy skips H2 to H6. No inner pages checked: the scan found none to sample. | | Page token budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~12K tokens) | | Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.dailymail.com/google-news-sitemap.xml with multiple sitemaps entries | | Sitemap freshness (lastmod) | Fail | 0 of 1 | None of the 500 sampled sitemap entries carries a lastmod date. Add (W3C datetime) so agents can prioritize fresh content. | | llms.txt exists | Pass | 1 of 1 | Found the llms.txt at https://dailymail.co.uk/llms.txt. | | llms.txt formatting | Partial | 1 of 2 | The llms.txt at https://dailymail.co.uk/llms.txt is well-formatted with markdown links, but at 39,603 characters it exceeds the 30,000-character recommendation for a navigation index. | | llms.txt links resolve | Pass | 2 of 2 | The markdown links an llms.txt declares actually resolve - broken links strand agents that follow the index | | 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, | | 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 NewsArticle found - missing name, description, and one of author / datePublished on this entity | | Organization schema completeness | Fail | 0 of 2 | No Organization type found in JSON-LD | | 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 2 more types that match what the homepage shows, for full coverage | | Metadata completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: HTML lang attribute | | Agent instruction / when-to-use | Pass | 3 of 3 | Explicit guidance on when to use your product, written where agents will read it. An agent choosing between ten tools picks the one that says what it is for. | ## 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. 13 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) | | 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 | | OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) | | NLWeb /ask endpoint | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) | ## 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 | Fail | 0 of 3 | dailymail.co.uk was not in the top 10 for "Mail Online" (searched your brand name alone: no main product term from your homepage qualified) | | Wikipedia / Wikidata entity presence | Partial | 2 of 4 | Wikidata Q210534 (Daily Mail) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage | | Developer resource discoverability | Fail | 0 of 3 | In a search for your API docs, none of the 10 results is your official docs | | 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 (1 community skill 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 Daily Mail, 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 14.8 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) Scoped permissions Fail, 0 of 5, about 10.6 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found Developer resource discoverability Fail, 0 of 3, about 6.1 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs Brand name discoverability Fail, 0 of 3, about 6.1 points to gain. Ora saw: dailymail.co.uk was not in the top 10 for "Mail Online" (searched your brand name alone: no main product term from your homepage qualified) robots.txt AI crawler policy Fail, 0 of 2, about 4 points to gain. Ora saw: AI search crawlers: allowed in 0 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 0 of 2 checks (2 crawlers on 1 page), not scored. robots.txt restricts 3/3 evaluated search page/crawler pairs. ## Our read MailOnline posts the strangest Discovery result of the set: Ora's search for "Mail Online" did not return dailymail.co.uk in the top ten, and no Wikipedia page is tied to the domain though the Wikidata item is verified, so the layer reads 2 of 11 for one of the most-visited news sites in the English language. The door is shut on purpose, with bot detection blocking all four test agents and robots.txt restricting every user-triggered agent and every search crawler on the checks Ora ran. The site does publish an llms.txt and a news sitemap, and a home page that gets through carries 48,784 characters of text with an H1. Every developer path Ora probed answered 403 from the bot shield, so those checks are unverifiable rather than failed. A D at 38 would be an F without the readable page, and a C with a knowledge-graph entry. ## 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 dailymail.co.uk, GET /api/score (vendor)](https://ora.ai/api/score/dailymail.co.uk?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 - [Daily Mail home page](https://www.dailymail.com/ushome/index.html) 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