---
title: "Time agent readiness: the 360 check | Agent Ready Crawlers"
description: "Time on Ora's agent-readiness scan, read 2026-11-11: 57 of 100, grade C. What agents meet at the door, what they can read and do, and the fixes worth most."
canonical: https://agentreadycrawlers.com/blog/time-agent-readiness
site: "Agent Ready Crawlers"
last_updated: 2026-11-11
date: 2026-11-11
section: "360 checks"
---

# Time agent readiness: the 360 check | Agent Ready Crawlers

> Time on Ora's agent-readiness scan, read 2026-11-11: 57 of 100, grade C. What agents meet at the door, what they can read and do, and the fixes worth most.

Source: https://agentreadycrawlers.com/blog/time-agent-readiness
Site: Agent Ready Crawlers
Last reviewed: 2026-11-11
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, 11 November 2026

# Time: the 360 agent-readiness check

In short

Time scores 57 of 100 on Ora's agent-readiness scan, a C, read 11 November 2026. At the door, site accessible to 4 AI agent user-agents. 22 of 64 applicable checks pass; the gap worth most is MCP Apps support, about 9.9 points by Ora's estimate. An open door, 11,309 characters to read, and an llms.txt without a single link.

Time is the weekly news magazine founded in 1923. On 11 November 2026 its public site scored **57 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 127 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: TIME.com provides content without JavaScript, but lacks MCP Apps support.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 4 of 10 | 40% |
| Access | Can agents read it | 27 of 44 | 61% |
| Usability | Can agents use it | 11 of 18 | 61% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 57 of 100 | 57% |

**

22 checks pass, 4 are partial, 38 fail and 62 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.

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 | Pass | 2 of 2 | Site accessible to 4 AI agent user-agents |
| Agent crawler reachability | Pass | 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable |
| 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 |
| Content behind auth | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| 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 | Pass | 2 of 3 | 11309 chars with H1 but flat heading structure |
| Page token budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~4K tokens) |
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://time.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 | Pass | 1 of 1 | Found the llms.txt at https://time.com/llms.txt. |
| llms.txt formatting | Partial | 1 of 2 | The llms.txt starts with a heading and has 18 lines, but it contains no markdown links. |
| 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://time.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 | Pass | 1 of 1 | https://time.com serves markdown to the ClaudeBot User-Agent even with Accept: text/html - UA-sniffed agent responses in place |
| Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data | Pass | 3 of 4 | JSON-LD Organization with name + description - add url and sameAs/logo/address for full score |
| 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: BreadcrumbList - add FAQPage, Service, or AggregateRating for full coverage |
| Metadata completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", 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 2 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 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 | Pass | 3 of 3 | time.com appears at position #2 in a clean brand-name search for "TIME" (1 total match) |
| 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 (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery | Fail | 0 of 3 | 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 Time, with what Ora observed. The wording of each fix is Ora's job; the links go to the check in its catalog.

MCP Apps support

Fail, 0 of 4, about 9.9 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.

ARD discovery

Fail, 0 of 3, about 6.7 points to gain. Ora saw: No /.well-known/ai-catalog.json

WebMCP support

Fail, 0 of 2, about 4.9 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 same-origin script bundle(s) for modelContext registrations)

ChatGPT app listed

Fail, 0 of 2, about 4.4 points to gain. Ora saw: Not found in ChatGPT app directory

Agent auth discovery metadata

Fail, 0 of 3, about 2.5 points to gain. Ora saw: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: time.com, api.time.com.

## Our read

Time leaves its door wide open. All four of Ora's test agents reached the home page, robots.txt allows every crawler by default but draws no line between search, training and user-triggered agents, and nothing restricts the agents a reader sends. What they find is readable: 11,309 characters without JavaScript under an H1, though the heading structure is flat, a valid sitemap, complete metadata, and an Organization block with a name and description but no url or sameAs. There is an llms.txt of 18 lines with a heading and not one markdown link, and ClaudeBot is already served markdown by user agent while a request for text/markdown still gets HTML. The Access layer reads 27 of 44. The act layer is empty, with neither an API nor OAuth and no MCP server. The largest gain is MCP Apps support, about 10 points. A C at 57: the magazine wrote agents a contents page and left out the links.

## 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 time.com, GET /api/score (vendor)](https://ora.ai/api/score/time.com?utm_source=agentreadycrawlers.com&utm_medium=referral&utm_campaign=check) read 2026-11-11
-   [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
-   [Time home page](https://time.com/) read 2026-11-11
-   [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-11