---
title: "Waymark report for wordpress.com"
canonical: "https://waymark.genedai.me/score/wordpress.com"
last-updated: "2026-08-26T16:31:02.939Z"
---

# Waymark report for wordpress.com

Waymark scored wordpress.com 78.6/100 (B) on 26 Aug 2026.
Score: 78.6/100 — Usable with gaps
Scanned: 2026-08-26T16:31:02.939Z
Canonical report: https://waymark.genedai.me/score/wordpress.com

## Layer breakdown

- Discovery: 14.6/20 (11 of 18 eligible checks passed)
- Access: 23.6/30 (28 of 35 eligible checks passed)
- Usability: 32.5/40 (11 of 20 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. AGENTS.md

- Layer: discovery
- Result: failed
- Evidence: agents.md status 403.
- Recommended fix: Publish /agents.md with agent-oriented usage notes.

### 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. OpenAPI / Swagger link

- Layer: access
- Result: failed
- Evidence: No OpenAPI/Swagger link in HTML.
- Recommended fix: Link to an OpenAPI or Swagger document from the homepage.

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

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

### 6. llms-full.txt

- Layer: discovery
- Result: failed
- Evidence: llms-full.txt status 404.
- Recommended fix: Optionally publish /llms-full.txt for one-shot ingest.

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

### 8. ai-plugin.json

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

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

### 10. Idempotency signal

- Layer: usability
- Result: partial
- Evidence: API surface without idempotency notes.
- Recommended fix: Document idempotency keys for mutating calls.

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

### 12. OpenAPI document

- Layer: access
- Result: failed
- Evidence: OpenAPI probe.
- Recommended fix: Publish an OpenAPI document at a stable URL.

### 13. Package homepage match

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

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

### 15. Organization schema completeness

- Layer: access
- Result: failed
- Evidence: Organization JSON-LD missing contactPoint.
- Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).

### 16. Markdown frontmatter metadata

- Layer: access
- Result: failed
- Evidence: Served markdown has no YAML frontmatter block.
- Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated.

### 17. MCP tool listing

- Layer: usability
- Result: failed
- Evidence: tools/list HTTP 200 at https://automattic.ai/mcp, 0 tool(s).
- Recommended fix: Expose tools via tools/list on a discovered MCP endpoint. OAuth-gated 401 is N/A, not fail.

### 18. MCP tool descriptions

- Layer: usability
- Result: failed
- Evidence: 0/0 tools have descriptions ≥20 chars.
- Recommended fix: Add detailed descriptions (≥20 chars) to every MCP tool.

### 19. MCP parameter schemas

- Layer: usability
- Result: failed
- Evidence: 0/0 tools have inputSchema.
- Recommended fix: Define inputSchema with typed properties for each tool.

### 20. MCP tool naming

- Layer: usability
- Result: failed
- Evidence: 0/0 tools use descriptive names.
- Recommended fix: Use consistent snake_case or camelCase names that are descriptive (≥4 chars), not generic run/get/do.

### 21. MCP tool annotations

- Layer: usability
- Result: failed
- Evidence: 0/0 tools have behavioral annotations.
- Recommended fix: Add readOnlyHint and destructiveHint so agents avoid unsafe calls.

### 22. MCP error handling

- Layer: usability
- Result: failed
- Evidence: Bad tools/call did not return a JSON-RPC error object.
- Recommended fix: Return structured JSON-RPC errors (code and message) for invalid tools or arguments.

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