--- title: "Waymark report for target.com" canonical: "https://waymark.genedai.me/score/target.com" last-updated: "2026-08-26T16:30:04.043Z" --- # Waymark report for target.com Waymark scored target.com 49.4/100 (C) on 26 Aug 2026. Score: 49.4/100 — Blockers remain Scanned: 2026-08-26T16:30:04.043Z Canonical report: https://waymark.genedai.me/score/target.com ## Layer breakdown - Discovery: 12.8/20 (8 of 17 eligible checks passed) - Access: 17.4/30 (18 of 32 eligible checks passed) - Usability: 14.3/40 (4 of 12 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. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 404. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 3. 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. ### 4. RSS or Atom feed - Layer: access - Result: failed - Evidence: No RSS/Atom link. - Recommended fix: Expose an RSS or Atom feed for machine subscribers. ### 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. 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. ### 8. Webhook or API docs - Layer: usability - Result: failed - Evidence: No webhook/API docs mention. - Recommended fix: Document webhooks and REST/RPC APIs for agents. ### 9. 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. ### 10. Sitemap for agents - Layer: discovery - Result: partial - Evidence: Sitemap only referenced. - Recommended fix: Publish /sitemap.xml. ### 11. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 404. - Recommended fix: Optionally publish /llms-full.txt for one-shot ingest. ### 12. 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. ### 13. JSON-LD entities - Layer: access - Result: partial - Evidence: JSON-LD present without common product types. - Recommended fix: Embed Organization, Product, Offer, SoftwareApplication, or FAQPage. ### 14. 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. ### 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. security.txt - Layer: access - Result: failed - Evidence: No /.well-known/security.txt Contact. - Recommended fix: Publish /.well-known/security.txt with a Contact field. ### 17. 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. ### 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. JSON-LD sameAs - Layer: access - Result: failed - Evidence: JSON-LD without sameAs. - Recommended fix: Add sameAs profile URLs. ### 28. Package homepage match - Layer: discovery - Result: failed - Evidence: No npm package homepage matching target.com. - Recommended fix: Publish an official package whose homepage is this domain. ### 29. 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. ### 30. 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. ### 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.