--- title: "Waymark report for nytimes.com" canonical: "https://waymark.genedai.me/score/nytimes.com" last-updated: "2026-08-26T16:27:27.789Z" --- # Waymark report for nytimes.com Waymark scored nytimes.com 48.6/100 (C) on 26 Aug 2026. Score: 48.6/100 — Blockers remain Scanned: 2026-08-26T16:27:27.789Z Canonical report: https://waymark.genedai.me/score/nytimes.com ## Layer breakdown - Discovery: 8.8/20 (6 of 17 eligible checks passed) - Access: 18.7/30 (19 of 31 eligible checks passed) - Usability: 16.3/40 (5 of 13 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. XML sitemap - Layer: discovery - Result: partial - Evidence: Sitemap referenced in robots.txt only. - Recommended fix: Add /sitemap.xml and reference it from robots.txt. ### 2. llms.txt - Layer: discovery - Result: failed - Evidence: llms.txt status 404. - Recommended fix: Add /llms.txt describing the site for language models. ### 3. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 4. Well-known AI catalog - Layer: discovery - Result: failed - Evidence: No ai-plugin.json or ai-catalog.json. - Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json. ### 5. CORS / API hint - Layer: access - Result: partial - Evidence: No CORS header or obvious API path. - Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients. ### 6. OAuth / OIDC well-known - Layer: access - Result: failed - Evidence: No oauth-authorization-server or openid-configuration. - Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents. ### 7. AI crawlers not blanket-blocked - Layer: access - Result: failed - Evidence: robots.txt Disallow: / for * or common AI bots. - Recommended fix: Avoid Disallow: / for GPTBot, ClaudeBot, PerplexityBot unless intentional. ### 8. MCP SSE / HTTP hint - Layer: usability - Result: failed - Evidence: No MCP/SSE hint on the homepage. - Recommended fix: Document an MCP HTTP or SSE endpoint. ### 9. Webhook or API docs - Layer: usability - Result: failed - Evidence: No webhook/API docs mention. - Recommended fix: Document webhooks and REST/RPC APIs for agents. ### 10. Sitemap for agents - Layer: discovery - Result: partial - Evidence: Sitemap only referenced. - Recommended fix: Publish /sitemap.xml. ### 11. llms.txt index - Layer: discovery - Result: failed - Evidence: Missing /llms.txt. - Recommended fix: Add a markdown index at /llms.txt. ### 12. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 13. HTTP Link header - Layer: discovery - Result: failed - Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage. - Recommended fix: Send RFC 8288 Link headers for related machine resources. ### 14. MCP initialize - Layer: usability - Result: failed - Evidence: No MCP card to initialize - Recommended fix: Expose Streamable HTTP MCP and answer initialize. ### 15. ai-plugin.json - Layer: discovery - Result: failed - Evidence: No /.well-known/ai-plugin.json. - Recommended fix: Optionally publish a plugin-style capability manifest. ### 16. change-password well-known - Layer: access - Result: failed - Evidence: Login surface without /.well-known/change-password. - Recommended fix: If users have passwords, serve /.well-known/change-password. ### 17. llms.txt size and links - Layer: discovery - Result: failed - Evidence: No llms.txt to score. - Recommended fix: Keep /llms.txt over ~200 characters with absolute URLs to docs. ### 18. Rate limit signal - Layer: usability - Result: partial - Evidence: API surface without a rate-limit signal. - Recommended fix: Document or send rate-limit headers on APIs. ### 19. Idempotency signal - Layer: usability - Result: partial - Evidence: API surface without idempotency notes. - Recommended fix: Document idempotency keys for mutating calls. ### 20. Machine-readable errors - Layer: usability - Result: partial - Evidence: API surface without a JSON error shape. - Recommended fix: Return a JSON or problem+json error body. ### 21. OpenAPI document - Layer: access - Result: partial - Evidence: OpenAPI probe. - Recommended fix: Publish an OpenAPI document at a stable URL. ### 22. Developer portal - Layer: access - Result: partial - Evidence: No developer portal. - Recommended fix: Offer a self-serve docs hub. ### 23. Pricing page - Layer: access - Result: failed - Evidence: No pricing page. - Recommended fix: Publish /pricing. ### 24. CLI tool - Layer: usability - Result: failed - Evidence: No CLI mention. - Recommended fix: Publish an official CLI. ### 25. MCP server - Layer: usability - Result: partial - Evidence: MCP mentioned without a documented initialize. - Recommended fix: Publish an MCP card or document the MCP URL in llms.txt, then answer initialize. ### 26. Trust pages - Layer: access - Result: failed - Evidence: No about/privacy/contact link. - Recommended fix: Link about or privacy from the homepage. ### 27. RSS or Atom document - Layer: access - Result: partial - Evidence: No /feed or /rss.xml document. - Recommended fix: Publish /rss.xml or /atom.xml. ### 28. Package homepage match - Layer: discovery - Result: failed - Evidence: No npm package homepage matching nytimes.com. - Recommended fix: Publish an official package whose homepage is this domain. ### 29. robots.txt agent-user policy - Layer: access - Result: failed - Evidence: robots.txt Disallow: / covers agent-user crawlers (ChatGPT-User, Claude-User, Perplexity-User). - Recommended fix: Stop blocking user-triggered agents in robots.txt. Remove any Disallow: / that applies to ChatGPT-User, Claude-User or Perplexity-User. Silence passes. ### 30. Organization schema completeness - Layer: access - Result: failed - Evidence: Organization JSON-LD missing contactPoint and address. - Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). ### 31. Agent-UA markdown docs - Layer: access - Result: failed - Evidence: Docs host did not serve markdown to GPTBot (HTTP 530, text/plain; charset=utf-8). - Recommended fix: Serve text/markdown to GPTBot (and similar agent UAs) on your docs host. ## Interpretation Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan. The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.