Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 65 out of 100
- Agent Ease of Use 53 out of 100
- Security & Trust 69 out of 100
- GEO, AIO and AEO 54 out of 100
- SEO 92 out of 100
- Performance 67 out of 100
- Accessibility 63 out of 100
What AI sees of your website
Introduction - Medama Analytics
Medama Analytics is an open-source project dedicated to providing self-hostable, cookie-free website analytics. With a lightweight tracker of less than 1KB, it aims to offer useful analytics while prioritising user privacy.
Next step
Turn this report into a fix workflow
2 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 | 65 | Needs work | 31 | 1 | 0 | View details |
| Discoverability | 78 | Mostly ready | 8 | 0 | 0 | |
| Content Readiness | 62 | Needs work | 20 | 0 | 0 | |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 53 | Needs work | 9 | 1 | 1 | View details |
| API | 67 | Needs work | 2 | 0 | 0 | |
| Auth | 47 | Priority fix | 1 | 0 | 0 | |
| MCP | 45 | Priority fix | 2 | 0 | 0 | |
| Skill Discovery | 54 | Needs work | 4 | 1 | 1 | View details |
| GEO, AIO and AEO | 54 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 69 | Needs work | 17 | 0 | 0 | |
| Security & Trust | 69 | Needs work | 17 | 0 | 0 | |
| Performance | 67 | Needs work | 15 | 0 | 0 | |
| Performance | 67 | Needs work | 15 | 0 | 0 | |
| Accessibility | 63 | Needs work | 0 | 1 | 0 | View details |
| Accessibility | 63 | Needs work | 0 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate version-specific card shape".
33 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate version-specific card shape".
Needs attention
A2A Agent Card
Issue
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
Details
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
67/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 "Validate version-specific card shape".
Validation steps
Validate version-specific card shape
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
Missing required fields
- description
- 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 log2 steps · 9 lines
Validate version-specific card shape [fail]! A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.INFOValidate version-specific card shapeFAILCompare missing required card fields actual=["description","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=[{"url":"https://medama.mintlify.app/","protocolBinding":"HTTP+JSON","issues":[]}]FAILA2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.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 url="https://medama.mintlify.app/" reason="Endpoint is cross-origin; default scanner policy does not probe it."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.
AccessibilityAccessibilityBrowser audit
ARIA attributes must conform to valid values
100 Fail
AccessibilityAccessibilityBrowser audit
ARIA attributes must conform to valid values
Check name
ARIA attributes must conform to valid values
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
ARIA attributes must conform to valid values
Evidence
{
"ruleId": "aria-valid-attr-value",
"impact": "critical",
"description": "Ensure all ARIA attributes have valid values",
"tags": [
"cat.aria",
"wcag2a",
"wcag412",
"EN-301-549",
"EN-9.4.1.2",
"RGAAv4",
"RGAA-7.1.1"
],
"affectedNodeCount": 1,
"nodes": [
{
"target": [
":root"
],
"html": {
"discarded": true,
"reason": "[discarded fetched document data]",
"originalType": "string",
"originalLength": 43
},
"failureSummary": "Fix all of the following:\n Invalid ARIA attribute value: aria-owns=\"rmiz-modal-\""
}
]
}Sign in to see 41 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