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

# Los Angeles Times: the 360 check | Agent Ready Crawlers

> Los Angeles Times on Ora's agent-readiness scan, read 2026-11-09: 57 of 100, grade C. The door, what agents can read and do, the fixes worth most.

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

# Los Angeles Times: the 360 agent-readiness check

In short

Los Angeles Times scores 57 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. At the door, site accessible to 6 AI agent user-agents. 14 of 63 applicable checks pass; the gap worth most is WebMCP support, about 8.9 points by Ora's estimate. Search crawlers in, training crawlers out, readers' agents unrestricted: the split Ora rewards.

Los Angeles Times is the largest newspaper on the US west coast. On 9 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 125 of its checks for this one domain, grouped the way an agent meets them. Ora's one-line summary: latimes.com offers agent crawler reachability, but lacks WebMCP support.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Discovery | Can agents find and recommend it | 6 of 10 | 60% |
| Access | Can agents read it | 19 of 38 | 50% |
| Usability | Can agents use it | 15 of 25 | 60% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade C | 57 of 100 | 57% |

**

14 checks pass, 8 are partial, 41 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. 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/), [Claude-SearchBot](https://agentreadycrawlers.com/crawlers/claude-searchbot/), [Perplexity-User](https://agentreadycrawlers.com/crawlers/perplexity-user/), [GPTBot](https://agentreadycrawlers.com/crawlers/gptbot/), [ClaudeBot](https://agentreadycrawlers.com/crawlers/claudebot/).

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection | Pass | 2 of 2 | Site accessible to 6 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 | Partial | 1 of 2 | Training: 0/2. Search: 3/3 page/crawler pairs permitted. robots.txt restricts 2/5 evaluated page/crawler pairs. Checked 5 training and search crawlers (gptbot, claudebot, oai-searchbot, claude-searchbot, |
| robots.txt agent-user policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://latimes.com/. Declared policy only; |
| 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 | 8585 chars with H1, but first content heading is H2, not H1; 1.5% content ratio is below the 5% target |
| Page token budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~2K tokens) |
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.latimes.com/sitemaps/sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) | Partial | 0 of 1 | Sitemap lastmod dates are all stale - the newest is 1598 days old. Update lastmod when content changes or agents will deprioritize the whole site as unmaintained. |
| 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://latimes.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 | 3 of 4 | JSON-LD Organization found - missing description and url on this entity |
| 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 | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| 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 |
| 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 | latimes.com ranks #6 for "Los Angeles Times" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Los Angeles Times" and Wikidata Q188515 both verified - domain confirmed on both sources |
| 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 |
| 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 Los Angeles Times, 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 8.9 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found

MCP Apps support

Fail, 0 of 4, about 7.1 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 4.4 points to gain. Ora saw: latimes.com ranks #6 for "Los Angeles Times" (searched your brand name alone: no main product term from your homepage qualified)

Agent instruction / when-to-use

Fail, 0 of 3, about 2.6 points to gain. Ora saw: No agent instruction file with when-to-use guidance found

Pricing info accessible

Fail, 0 of 3, about 2.6 points to gain. Ora saw: No pricing page or pricing data found

## Our read

The Los Angeles Times is the open publisher of the American set: Ora's home page request was accepted for six agent user agents, robots.txt lets the AI search crawlers through on three of three checks while refusing training crawlers on both, and places no restriction on the user-triggered agents. That is exactly the split Ora's methodology rewards, and it puts the Access layer at 19 of 38. The page gives 8,585 characters of text with an H1, though the first content heading is an H2 and the content ratio is 1.5 percent against a 5 percent target; the Organization JSON-LD lacks a description and URL. There is no llms.txt, no developer side to speak of, and the site ranks sixth for its own name. A C at 57 shows what a newspaper gets for keeping the door open and the training crawlers out.

## 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 latimes.com, GET /api/score (vendor)](https://ora.ai/api/score/latimes.com?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
-   [Los Angeles Times home page](https://www.latimes.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