---
title: "Waymark report for reddit.com"
canonical: "https://waymark.genedai.me/score/reddit.com"
last-updated: "2026-08-26T16:28:17.073Z"
---

# Waymark report for reddit.com

Waymark scored reddit.com 62.6/100 (C) on 26 Aug 2026.
Score: 62.6/100 — Blockers remain
Scanned: 2026-08-26T16:28:17.073Z
Canonical report: https://waymark.genedai.me/score/reddit.com

## Layer breakdown

- Discovery: 12.8/20 (10 of 17 eligible checks passed)
- Access: 15.5/30 (12 of 26 eligible checks passed)
- Usability: 28/40 (8 of 13 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. XML sitemap

- Layer: discovery
- Result: failed
- Evidence: No sitemap.xml.
- Recommended fix: Add /sitemap.xml and reference it from robots.txt.

### 2. 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.

### 3. Title and description

- Layer: access
- Result: partial
- Evidence: title=true meta=false
- Recommended fix: Set a unique <title> and meta name=description.

### 4. JSON-LD structured data

- Layer: access
- Result: failed
- Evidence: No JSON-LD on the homepage.
- Recommended fix: Add JSON-LD (Organization, WebSite, or SoftwareApplication).

### 5. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 6. 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.

### 7. OAuth / OIDC well-known

- Layer: access
- Result: partial
- Evidence: No oauth-authorization-server or openid-configuration.
- Recommended fix: Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.

### 8. Login or docs link

- Layer: access
- Result: failed
- Evidence: No login/docs/developers link.
- Recommended fix: Link to login and developer documentation from the homepage.

### 9. 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.

### 10. MCP well-known card

- Layer: usability
- Result: failed
- Evidence: MCP mentioned without a well-known card.
- Recommended fix: Publish /.well-known/mcp.json describing your MCP server.

### 11. Webhook or API docs

- Layer: usability
- Result: failed
- Evidence: No webhook/API docs mention.
- Recommended fix: Document webhooks and REST/RPC APIs for agents.

### 12. robots.txt AI policy

- Layer: discovery
- Result: partial
- Evidence: robots.txt present but no named AI crawlers.
- Recommended fix: Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny.

### 13. Sitemap for agents

- Layer: discovery
- Result: failed
- Evidence: No sitemap.
- Recommended fix: Publish /sitemap.xml.

### 14. 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.

### 15. JSON-LD entities

- Layer: access
- Result: failed
- Evidence: No JSON-LD.
- Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage.

### 16. MCP server card

- Layer: usability
- Result: partial
- Evidence: MCP mentioned without a card.
- Recommended fix: Publish /.well-known/mcp.json or mcp/server-card.json.

### 17. ai-plugin.json

- Layer: discovery
- Result: failed
- Evidence: No /.well-known/ai-plugin.json.
- Recommended fix: Optionally publish a plugin-style capability manifest.

### 18. Trust pages

- Layer: access
- Result: failed
- Evidence: No about/privacy/contact link.
- Recommended fix: Link about or privacy from the homepage.

### 19. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching reddit.com.
- Recommended fix: Publish an official package whose homepage is this domain.

### 20. Content without JavaScript

- Layer: access
- Result: failed
- Evidence: Raw HTML is thin for agents (H1=false, 6 chars).
- Recommended fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

### 21. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 22. robots.txt agent-user policy

- Layer: access
- Result: failed
- Evidence: robots.txt Disallow: / covers agent-user crawlers (*).
- 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.

### 23. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 1 real, 0 homepage-shell, 2 dead of 3 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

### 24. Accessible document structure

- Layer: usability
- Result: partial
- Evidence: Incomplete document structure (main=true nav=false h1=false).
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 25. Agent auth WWW-Authenticate hint

- Layer: usability
- Result: failed
- Evidence: MCP 401 without resource_metadata (WWW-Authenticate: missing).
- Recommended fix: Return 401 with WWW-Authenticate: Bearer resource_metadata= on a documented API entry point.

### 26. Agent-UA markdown docs

- Layer: access
- Result: failed
- Evidence: Docs host did not serve markdown to GPTBot (HTTP 403, text/html).
- 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.
