--- title: "Waymark report for posthog.com" canonical: "https://waymark.genedai.me/score/posthog.com" last-updated: "2026-08-24T02:15:04.076Z" --- # Waymark report for posthog.com Waymark scored posthog.com 54.6/100 (C) on 24 Aug 2026. Score: 54.6/100 — Blockers remain Scanned: 2026-08-24T02:15:04.076Z Canonical report: https://waymark.genedai.me/score/posthog.com ## Layer breakdown - Discovery: 13.3/20 (10 of 18 eligible checks passed) - Access: 18/30 (11 of 23 eligible checks passed) - Usability: 17.8/40 (3 of 10 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - 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. Title and description - Layer: access - Result: partial - Evidence: title=false meta=true - Recommended fix: Set a unique 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. 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. ### 6. html lang attribute - Layer: access - Result: failed - Evidence: Missing lang on <html>. - Recommended fix: Set <html lang="en"> (or the correct language). ### 7. RSS or Atom feed - Layer: access - Result: failed - Evidence: No RSS/Atom link. - Recommended fix: Expose an RSS or Atom feed for machine subscribers. ### 8. CSP or X-Frame-Options - Layer: access - Result: failed - Evidence: Neither CSP nor X-Frame-Options on homepage. - Recommended fix: Send Content-Security-Policy or X-Frame-Options. ### 9. 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. ### 10. 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. ### 11. 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. ### 12. Webhook or API docs - Layer: usability - Result: failed - Evidence: No webhook/API docs mention. - Recommended fix: Document webhooks and REST/RPC APIs for agents. ### 13. 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. ### 14. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 15. 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. ### 16. JSON-LD entities - Layer: access - Result: failed - Evidence: No JSON-LD. - Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage. ### 17. Markdown negotiation - Layer: access - Result: failed - Evidence: Homepage did not negotiate markdown. - Recommended fix: Respond to Accept: text/markdown with a markdown body. ### 18. /index.md fallback - Layer: access - Result: failed - Evidence: index.md status 404. - Recommended fix: Serve a markdown homepage at /index.md. ### 19. 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. ### 20. ai-plugin.json - Layer: discovery - Result: failed - Evidence: No /.well-known/ai-plugin.json. - Recommended fix: Optionally publish a plugin-style capability manifest. ### 21. API catalog linkset - Layer: discovery - Result: failed - Evidence: API present without RFC 9727 catalog. - Recommended fix: Add /.well-known/api-catalog pointing at OpenAPI. ### 22. 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. ### 23. Idempotency signal - Layer: usability - Result: partial - Evidence: API surface without idempotency notes. - Recommended fix: Document idempotency keys for mutating calls. ### 24. 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. ### 25. MCP server - Layer: usability - Result: partial - Evidence: MCP probe. - Recommended fix: Publish an MCP card and 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. Sitemap lastmod - Layer: discovery - Result: failed - Evidence: Sitemap without lastmod. - Recommended fix: Add lastmod dates to sitemap entries. ## 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.