--- title: "Waymark report for doordash.com" canonical: "https://waymark.genedai.me/score/doordash.com" last-updated: "2026-08-26T16:17:20.307Z" --- # Waymark report for doordash.com Waymark scored doordash.com 50.1/100 (C) on 26 Aug 2026. Score: 50.1/100 — Blockers remain Scanned: 2026-08-26T16:17:20.307Z Canonical report: https://waymark.genedai.me/score/doordash.com ## Layer breakdown - Discovery: 3.5/20 (3 of 15 eligible checks passed) - Access: 19.4/30 (16 of 27 eligible checks passed) - Usability: 22.2/40 (4 of 11 eligible checks passed) - Payments: N/A (excluded from the denominator) ## Findings ### 1. robots.txt present - Layer: discovery - Result: failed - Evidence: robots.txt status 403. - Recommended fix: Publish /robots.txt with User-agent rules and a Sitemap line. ### 2. XML sitemap - Layer: discovery - Result: failed - Evidence: No sitemap.xml. - Recommended fix: Add /sitemap.xml and reference it from robots.txt. ### 3. llms.txt - Layer: discovery - Result: failed - Evidence: llms.txt status 403. - Recommended fix: Add /llms.txt describing the site for language models. ### 4. AGENTS.md - Layer: discovery - Result: failed - Evidence: agents.md status 403. - Recommended fix: Publish /agents.md with agent-oriented usage notes. ### 5. 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. ### 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. robots.txt AI policy - Layer: discovery - Result: failed - Evidence: No robots.txt. - Recommended fix: Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny. ### 9. Sitemap for agents - Layer: discovery - Result: failed - Evidence: No sitemap. - Recommended fix: Publish /sitemap.xml. ### 10. llms.txt index - Layer: discovery - Result: failed - Evidence: Missing /llms.txt. - Recommended fix: Add a markdown index at /llms.txt. ### 11. llms-full.txt - Layer: discovery - Result: failed - Evidence: llms-full.txt status 403. - 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. Markdown negotiation - Layer: access - Result: failed - Evidence: Advertised markdown twin but homepage did not negotiate markdown. - Recommended fix: Respond to Accept: text/markdown with a markdown body. ### 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. 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. ### 19. 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. ### 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: partial - Evidence: No pricing page. - Recommended fix: Publish /pricing. ### 24. 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. ### 25. RSS or Atom document - Layer: access - Result: partial - Evidence: No /feed or /rss.xml document. - Recommended fix: Publish /rss.xml or /atom.xml. ### 26. Content without JavaScript - Layer: access - Result: failed - Evidence: Raw HTML is thin for agents (H1=true, 157 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. ### 27. Markdown alternate link - Layer: access - Result: failed - Evidence: rel=alternate markdown /index.md - Recommended fix: Advertise a markdown twin with rel=alternate type=text/markdown and serve markdown at that URL. ### 28. Accessible document structure - Layer: usability - Result: partial - Evidence: Landmarks partial (main=false nav=true h1=true skip=false). - Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels. ### 29. Multi-language SDK packages - Layer: usability - Result: partial - Evidence: npm matches; second ecosystem homepage does not. - Recommended fix: Publish official SDK packages on npm and PyPI whose homepage is this domain. ### 30. 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.