Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 79 out of 100
- Agent Ease of Use 79 out of 100
- Security & Trust 90 out of 100
- GEO, AIO and AEO 69 out of 100
- SEO 100 out of 100
- Performance 95 out of 100
- Accessibility 100 out of 100
What AI sees of your website
AIready: Agentic Readiness & AEO Audits for NZ Business
Can AI agents find, read, trust and buy from your website? Free 30-second scan plus the AIready Agentic Readiness Index of more than 1,200 NZ businesses.
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 | 79 | Mostly ready | 41 | 2 | 1 | View details |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 83 | Mostly ready | 28 | 1 | 1 | View details |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 79 | Mostly ready | 51 | 1 | 1 | View details |
| API | 92 | Strong | 12 | 0 | 0 | |
| Auth | 74 | Needs work | 13 | 0 | 0 | |
| MCP | 75 | Mostly ready | 6 | 0 | 0 | |
| Skill Discovery | 67 | Needs work | 10 | 1 | 1 | View details |
| Agent Commerce | 71 | Needs work | 6 | 0 | 0 | |
| Google Agentic Browsing | 98 | Strong | 4 | 0 | 0 | |
| GEO, AIO and AEO | 69 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 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 | 90 | Strong | 25 | 0 | 0 | |
| Security & Trust | 90 | Strong | 25 | 0 | 0 | |
| Performance | 95 | Strong | 16 | 0 | 0 | |
| Performance | 95 | Strong | 16 | 0 | 0 |
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.
Details
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.
robots.txt lacks explicit AI crawler rules
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=0AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
45 Warning
AI DiscoverabilityContent ReadinessEstablished
Author attribution
Author attribution is partially implemented.
Needs attention
Author attribution
Issue
No named author or publisher identity could be extracted.
Details
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
55/100
Status
warning
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
Schema.org attribution is incomplete or relies only on publisher/fallback evidence.
Schema.org author attribution is missing or incomplete
Author identity quality
No named author or publisher identity could be extracted.
Author identity quality is incomplete
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=1 namedContributors=0 authors=[] publishers=[{"role":"publisher","id":"https://aiready.nz/#organization","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=1 authors=[] publishers=[{"role":"publisher","id":"https://aiready.nz/#organization","sameAs":[],"format":"json-ld","mergedName":false}]Author 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=[{"role":"publisher","id":"https://aiready.nz/#organization","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Probe same-origin A2A endpoint".
30 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Probe same-origin A2A endpoint".
Needs attention
A2A Agent Card
Issue
The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
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
70/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 "Probe same-origin A2A endpoint".
Validation steps
Validate version-specific card shape
A2A Agent Card has compatibility warnings.
A2A Agent Card shape is invalid for its version
Probe same-origin A2A endpoint
The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log2 steps · 9 lines
Validate version-specific card shape [warning]! A2A Agent Card has compatibility warnings.INFOValidate version-specific card shapeWARNCompare missing required card fields actual="none" expected="none"WARNCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[{"url":"https://aiready.nz/api/public/agent/order","protocolBinding":"HTTP+JSON","issues":[]}]WARNA2A Agent Card has compatibility warnings.Probe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://aiready.nz/message:send" statusCode=406 rpcError="Only HTML requests are supported here"FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Sign in to see 27 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