Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 35 out of 100
- Agent Ease of Use 49 out of 100
- Security & Trust 52 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 100 out of 100
- Performance 97 out of 100
- Accessibility 99 out of 100
What AI sees of your website
Developer Roadmaps - roadmap.sh
Community driven roadmaps, articles and guides for developers to grow in their career.
Next step
Turn this report into a fix workflow
3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 35 | Priority fix | 16 | 0 | 0 | |
| Discoverability | 47 | Priority fix | 6 | 0 | 0 | |
| Content Readiness | 24 | Priority fix | 9 | 0 | 0 | |
| Bot Access Control | 33 | Priority fix | 1 | 0 | 0 | |
| Agent Ease of Use | 49 | Priority fix | 18 | 8 | 3 | View details |
| API | 66 | Needs work | 6 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| MCP | 40 | Priority fix | 3 | 0 | 0 | |
| Skill Discovery | 47 | Priority fix | 5 | 5 | 2 | View details |
| Agent Commerce | 43 | Priority fix | 3 | 3 | 1 | View details |
| GEO, AIO and AEO | 68 | Needs work | 11 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 52 | Needs work | 9 | 0 | 0 | |
| Security & Trust | 52 | Needs work | 9 | 0 | 0 | |
| Performance | 97 | Strong | 16 | 0 | 0 | |
| Performance | 97 | Strong | 16 | 0 | 0 | |
| Accessibility | 99 | Strong | 8 | 0 | 0 | |
| Accessibility | 99 | Strong | 8 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".
57 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery is missing protocol.
Details
Why it matters
ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.
Check name
ACP - Agentic Commerce Protocol
Score
43/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.
Result
ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".
Validation steps
Validate ACP discovery shape
ACP discovery is missing protocol.
ACP discovery is missing protocol.
ACP discovery is missing api_base_url.
ACP discovery is missing transports array.
ACP discovery is missing capabilities.
Validate ACP endpoint and transports
api_base_url is missing or unsafe.
Validate ACP capabilities
ACP discovery is missing capabilities.
Review ACP cache and retry metadata
ACP discovery is missing Cache-Control guidance.
Evidence log4 steps · 21 lines
Validate ACP discovery shape [fail]! ACP discovery is missing protocol.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":true,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery is missing protocol.Validate ACP endpoint and transports [fail]! api_base_url is missing or unsafe.INFOValidate ACP endpoint and transports status="fail"INFOValidate ACP API base URL and supported transportsFAILCheck safe HTTPS api_base_url actual=false expected=trueFAILCheck REST transport support actual=false expected=true transports=[] transportWarnings=[]FAILapi_base_url is missing or unsafe.Validate ACP capabilities [fail]! ACP discovery is missing capabilities.INFOValidate ACP capabilities status="fail"INFOValidate ACP services, extensions, intervention types, currencies, and localesFAILCheck capabilities object actual=false expected=trueFAILCheck stable ACP service declarations actual=[] expected="one or more known services such as checkout, orders, or delegate_payment"FAILCheck ACP capability values use stable service, extension, intervention, currency, and locale names actual="no compatibility warnings" expected="no unknown or unstable capability values" warnings=[]FAILACP discovery is missing capabilities.Review ACP cache and retry metadata [warning]! ACP discovery is missing Cache-Control guidance.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=200 cacheControl=null retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"WARNCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"WARNACP discovery is missing Cache-Control guidance.
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
33 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json does not match the expected Wildcard OpenAPI workflow shape.
Why it matters
Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.
Check name
agents.json
Score
35/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.
Result
agents.json failed at "Validate Wildcard schema shape".
Validation steps
Validate Wildcard schema shape
agents.json does not match the expected Wildcard OpenAPI workflow shape.
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
Validate flows and links
No executable flows were found.
Review examples and LLM usability
Examples or descriptions are too thin for reliable agent argument generation.
Evidence log4 steps · 17 lines
Validate Wildcard schema shape [fail]! agents.json does not match the expected Wildcard OpenAPI workflow shape.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=true expected=trueFAILagents.json does not match the expected Wildcard OpenAPI workflow shape.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNExamples or descriptions are too thin for reliable agent argument generation.
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
24 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
Needs attention
A2A Agent Card
Issue
The discovered JSON document does not match a supported A2A Agent Card version family.
Why it matters
A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.
Check name
A2A Agent Card
Score
53/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.
Result
A2A Agent Card failed at "Detect A2A card version".
Validation steps
Detect A2A card version
The discovered JSON document does not match a supported A2A Agent Card version family.
Validate version-specific card shape
Document does not match a supported A2A Agent Card shape.
Missing required fields
- skills[]
Probe same-origin A2A endpoint
A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.
Evidence log3 steps · 13 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! Document does not match a supported A2A Agent Card shape.INFOValidate version-specific card shapeFAILCompare missing required card fields actual=["skills[]"] expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILDocument does not match a supported A2A Agent Card shape.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.
Sign in to see 34 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history