Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 84 out of 100
- Agent Ease of Use 58 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 58 out of 100
- SEO 92 out of 100
- Performance 63 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Homepage - Leader Networks
[vc_row row_height_percent="0" override_padding="yes" h_padding="2" top_padding="2" bottom_padding="2" back_color="color-921133" back_image="2440" back_position="right center" parallax="yes" kburns="magnetic" overlay_color="color-jevc" ove...
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 | 84 | Mostly ready | 37 | 0 | 0 | |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 80 | Mostly ready | 22 | 0 | 0 | |
| Bot Access Control | 75 | Mostly ready | 5 | 0 | 0 | |
| Agent Ease of Use | 58 | Needs work | 10 | 4 | 2 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Skill Discovery | 58 | Needs work | 7 | 3 | 2 | View details |
| Google Agentic Browsing | 66 | Needs work | 2 | 1 | 0 | View details |
| GEO, AIO and AEO | 58 | Needs work | 7 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 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 | 45 | Priority fix | 7 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Performance | 63 | Needs work | 12 | 0 | 0 | |
| Performance | 63 | Needs work | 12 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
22 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.
Details
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
55/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.
agents.json schema shape is invalid or incomplete
Validate flows and links
No executable flows were found.
agents.json flows or links are invalid
Review examples and LLM usability
Examples or descriptions are too thin for reliable agent argument generation.
agents.json examples or descriptions need improvement
Evidence log3 steps · 20 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=trueINFORecorded remote OpenAPI/schema reference reference="https://www.leadernetworks.com/wp-json/airewp/v1/info"INFORecorded remote OpenAPI/schema reference reference="https://www.leadernetworks.com/wp-json/wp/v2/pages?per_page=100&_fields=id,title,link,excerpt"INFORecorded remote OpenAPI/schema reference reference="https://www.leadernetworks.com/wp-json/wp/v2/posts"INFORecorded remote OpenAPI/schema reference reference="https://www.leadernetworks.com/wp-json/airewp/v1/services"INFORecorded remote OpenAPI/schema reference reference="https://www.leadernetworks.com/wp-json/airewp/v1/contact"WARNSchema-shape warning warning="no examples were found for LLM argument generation"FAILagents.json does not match the expected Wildcard OpenAPI workflow shape.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"WARNLLM usability warning warning="no examples were found for LLM argument generation"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 "Probe same-origin A2A endpoint".
12 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
77/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 HTTP delivery
legacy A2A card is served at the current agent-card.json path
A2A Agent Card HTTP delivery is not standards-aligned
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 HTTP delivery [warning]! legacy A2A card is served at the current agent-card.json pathINFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="application/json" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNHTTP delivery/path warning warning="legacy A2A card is served at the current agent-card.json path"WARNlegacy A2A card is served at the current agent-card.json pathProbe 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://www.leadernetworks.com/" statusCode=200FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
100 Fail
Agent Ease of UseGoogle Agentic BrowsingBrowser audit
Accessibility tree is not well-formed
Check name
Accessibility tree is not well-formed
Score
0/100
Status
fail
Device
desktop
Category
Google Agentic Browsing
Fix guidance
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
Evidence
{
"description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}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