Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 73 out of 100
- Agent Ease of Use 71 out of 100
- Security & Trust 55 out of 100
- GEO, AIO and AEO 64 out of 100
- SEO 92 out of 100
- Performance 88 out of 100
- Accessibility 58 out of 100
What AI sees of your website
ora // Agent Readiness Ranking
Rank how ready your business is for AI agents across four layers.
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 | 73 | Needs work | 29 | 0 | 0 | |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 58 | Needs work | 16 | 0 | 0 | |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 71 | Needs work | 43 | 3 | 2 | View details |
| API | 86 | Mostly ready | 12 | 1 | 1 | View details |
| Auth | 59 | Needs work | 5 | 0 | 0 | |
| MCP | 54 | Needs work | 4 | 0 | 0 | |
| Skill Discovery | 62 | Needs work | 8 | 2 | 1 | View details |
| Agent Commerce | 72 | Needs work | 11 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 64 | Needs work | 9 | 1 | 3 | View details |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | 51 | Needs work | 2 | 1 | 3 | View details |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 55 | Needs work | 11 | 0 | 0 | |
| Security & Trust | 55 | Needs work | 11 | 0 | 0 | |
| Performance | 88 | Mostly ready | 15 | 0 | 0 | |
| Performance | 88 | Mostly ready | 15 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
6 items need attention
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
47 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.
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
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.
A2A Agent Card version cannot be classified cleanly
Validate version-specific card shape
Document does not match a supported A2A Agent Card shape.
A2A Agent Card shape is invalid for its version
Invalid skills
- #0: id, tags[]
- #1: id, tags[]
- #2: id, tags[]
- #3: id, tags[]
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.
Advertised same-origin A2A endpoint did not answer a safe probe
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="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=4 expected=0 invalidSkills=[{"index":0,"issues":["id","tags[]"]},{"index":1,"issues":["id","tags[]"]},{"index":2,"issues":["id","tags[]"]},{"index":3,"issues":["id","tags[]"]}]INFOReview declared endpoint interfaces interfaces=[{"url":"https://ora.ai","protocolBinding":"JSONRPC","issues":[]}]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.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
21 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://ora.ai/api/openapi.json (item) advertised application/vnd.oai.openapi+json;version=3.1 but returned application/json.
Details
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
79/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog targets".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
API catalog HEAD Link discovery is incomplete
Validate API catalog targets
API catalog target https://ora.ai/api/openapi.json (item) advertised application/vnd.oai.openapi+json;version=3.1 but returned application/json.
API catalog targets are unreachable or media types mismatch
Evidence log2 steps · 11 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json;profile=\"https://www.rfc-editor.org/info/rfc9727\""WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"INFOReview HEAD Link header linkHeader="<https://ora.ai/llms.txt>; rel=\"describedby\", <https://ora.ai/.well-known/ai-catalog.json>; rel=\"ai-catalog\""WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog targets [fail]! API catalog target https://ora.ai/api/openapi.json (item) advertised application/vnd.oai.openapi+json;version=3.1 but returned application/json.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILAPI catalog target failed validation rel="item" href="https://ora.ai/api/openapi.json" statusCode=200 contentType="application/json" advertisedType="application/vnd.oai.openapi+json;version=3.1" typeMatches=falseFAILAPI catalog target failed validation rel="service-desc" href="https://ora.ai/api/openapi.json" statusCode=200 contentType="application/json" advertisedType="application/vnd.oai.openapi+json;version=3.1" typeMatches=falseFAILCompare API catalog target failure count actual=2 expected=0FAILAPI catalog target https://ora.ai/api/openapi.json (item) advertised application/vnd.oai.openapi+json;version=3.1 but returned application/json.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
9 Fail
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Answer-first passages
AEO: Answer-first passages scored 0/100 and needs a fix.
Needs attention
AEO: Answer-first passages
Issue
11 section(s) bury or omit a concise opening answer. No direct definition pattern was detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Answer-first passages
Score
0/100
Status
fail
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Answer-first passages scored 0/100 and needs a fix.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 70/100 and needs improvement.
3 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Question and answer structure
AEO: Question and answer structure scored 70/100 and needs improvement.
Needs attention
AEO: Question and answer structure
Issue
4 Q&A structured-data value(s) were not found in visible content. Heading structure issues were detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Question and answer structure
Score
70/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Question and answer structure scored 70/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 76/100 and needs improvement.
2 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Entity and definition clarity
AEO: Entity and definition clarity scored 76/100 and needs improvement.
Needs attention
AEO: Entity and definition clarity
Issue
No direct definition sentence was detected.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Entity and definition clarity
Score
76/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Entity and definition clarity scored 76/100 and needs improvement.
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 86/100 and needs improvement.
1 Warning
GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation
AEO: Evidence and trust
AEO: Evidence and trust scored 86/100 and needs improvement.
Needs attention
AEO: Evidence and trust
Issue
Missing answer evidence or trust signals: author.
Details
Why it matters
Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.
Check name
AEO: Evidence and trust
Score
86/100
Status
warning
Category
GEO, AIO & AEO
Maturity
Emerging recommendation
Goal
Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.
Result
AEO: Evidence and trust scored 86/100 and needs improvement.
Sign in to see 38 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