Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 71 out of 100
- Agent Ease of Use 51 out of 100
- Security & Trust 92 out of 100
- GEO, AIO and AEO 67 out of 100
- SEO 100 out of 100
- Performance 97 out of 100
- Accessibility 95 out of 100
What AI sees of your website
Ownkube - Ship at lightning speed. On your own cloud.
Developer platform in your own AWS account. Named agents (Cost, Incident, Scaling, Security) run your ops. Free Starter tier on one AWS instance.
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 | 71 | Needs work | 39 | 5 | 1 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 69 | Needs work | 26 | 3 | 1 | View details |
| Bot Access Control | 75 | Mostly ready | 5 | 0 | 0 | |
| Agent Ease of Use | 51 | Needs work | 2 | 0 | 0 | |
| Auth | 48 | Priority fix | 1 | 0 | 0 | |
| Skill Discovery | 54 | Needs work | 1 | 0 | 0 | |
| GEO, AIO and AEO | 67 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| SEO | 100 | Strong | 9 | 0 | 0 | |
| Security & Trust | 92 | Strong | 23 | 0 | 0 | |
| Security & Trust | 92 | Strong | 23 | 0 | 0 | |
| Performance | 97 | Strong | 18 | 0 | 0 | |
| Performance | 97 | Strong | 18 | 0 | 0 | |
| Accessibility | 95 | Strong | 5 | 1 | 0 | View details |
| Accessibility | 95 | Strong | 5 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
Evidence log2 steps · 15 lines
Find useful Link headers [fail]! No useful agent discovery Link headers were found.INFOFind useful Link headersINFOParse response Link header linkCount=6FAILCompare registered agent-useful relation count actual=0 expected="> 0"FAILCompare community relation count actual=0 expected="accepted as weaker evidence"INFOIgnored non-discovery Link relation rel="sitemap" url="/sitemap-index.xml"INFOIgnored non-discovery Link relation rel="alternate" url="/index.md"INFOIgnored non-discovery Link relation rel="alternate" url="/llms.txt"INFOIgnored non-discovery Link relation rel="alternate" url="/llms-full.txt"INFOIgnored non-discovery Link relation rel="describedby" url="/robots.txt"INFOIgnored non-discovery Link relation rel="alternate" url="/llms.txt"FAILNo useful agent discovery Link headers were found.Fetch same-origin Link header targets [fail]! Link headers did not expose any same-origin targets to validate.INFOFetch same-origin Link header targetsINFOFetch same-origin Link header targets and record external skipsFAILCompare same-origin Link target failures actual=1 expected=0FAILLink headers did not expose any same-origin targets to validate.
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
95 Fail
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
Applicable editorial content has no usable author, creator, publisher, visible byline, or HTML attribution signal.
Why it matters
Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.
Check name
Author attribution
Score
5/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Identify content authors or publishers for trust and attribution.
Result
Author attribution is partially implemented.
Validation steps
Schema.org attribution
Editorial content has no Schema.org author, creator, or publisher attribution.
Author identity quality
No named author or publisher identity could be extracted.
Visible byline parity
Structured author/publisher names were not found in visible byline text.
HTML attribution support
No supporting HTML author metadata, rel=author link, or visible byline was found.
Evidence log4 steps · 16 lines
Schema.org attribution [fail]! Editorial content has no Schema.org author, creator, or publisher attribution.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsFAILCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]FAILNo Schema.org author, creator, or publisher attribution foundAuthor identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity foundHTML attribution support [warning]! No supporting HTML author metadata, rel=author link, or visible byline was found.INFOHTML attribution supportINFOChecking meta author, rel=author, and visible byline supportWARNCheck HTML attribution support signals actual=0 expected="> 0" metaAuthor=false relAuthor=false visibleByline=falseWARNNo supporting HTML attribution signal found
AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
100 Fail
AccessibilityAccessibilityBrowser audit
Background and foreground colors do not have a sufficient contrast ratio.
Check name
Background and foreground colors do not have a sufficient contrast ratio.
Score
0/100
Status
fail
Device
desktop
Category
Accessibility
Fix guidance
Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast).
Evidence
{
"description": "Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.11/color-contrast)."
}Sign in to see 23 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