Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 30 out of 100
- Agent Ease of Use 41 out of 100
- Security & Trust 47 out of 100
- GEO, AIO and AEO 32 out of 100
- SEO 92 out of 100
- Performance 83 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Matrix Infotech Solution | Web, Mobile App & Software Development Company
Matrix Infotech Solution provides web development, mobile apps, digital marketing, and custom software solutions.
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 | 30 | Priority fix | 16 | 0 | 0 | |
| Discoverability | 33 | Priority fix | 5 | 0 | 0 | |
| Content Readiness | 28 | Priority fix | 10 | 0 | 0 | |
| Bot Access Control | 28 | Priority fix | 1 | 0 | 0 | |
| Agent Ease of Use | 41 | Priority fix | 21 | 6 | 2 | View details |
| API | 44 | Priority fix | 7 | 0 | 0 | |
| Auth | 41 | Priority fix | 6 | 0 | 0 | |
| MCP | 37 | Priority fix | 3 | 0 | 0 | |
| Skill Discovery | 46 | Priority fix | 2 | 3 | 1 | View details |
| Agent Commerce | 42 | Priority fix | 2 | 2 | 1 | View details |
| Google Agentic Browsing | 33 | Priority fix | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 32 | Priority fix | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 1 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 47 | Priority fix | 9 | 0 | 0 | |
| Security & Trust | 47 | Priority fix | 9 | 0 | 0 | |
| Performance | 83 | Mostly ready | 13 | 0 | 0 | |
| Performance | 83 | Mostly ready | 13 | 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".
65 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
agents.json
agents.json failed at "Validate Wildcard schema shape".
Needs attention
agents.json
Issue
agents.json response is not valid JSON.
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
35/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 response is not valid JSON.
agents.json schema shape is invalid or incomplete
Validate API actions
Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.
agents.json action definitions are invalid or missing
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 log4 steps · 17 lines
Validate Wildcard schema shape [fail]! agents.json response is not valid JSON.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=false expected=trueFAILagents.json response is not valid JSON.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.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"WARNExamples or descriptions are too thin for reliable agent argument generation.
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
58 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery content type "text/html" is not JSON-compatible.
Details
Why it matters
ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.
Check name
ACP - Agentic Commerce Protocol
Score
42/100
Status
fail
Category
Agent Commerce
Maturity
Informational
Goal
Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.
Result
ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".
Validation steps
Fetch ACP discovery
ACP discovery content type "text/html" is not JSON-compatible.
ACP discovery is missing or not parseable
Validate ACP discovery shape
ACP discovery could not be parsed.
ACP discovery protocol metadata is invalid
Review ACP cache and retry metadata
ACP discovery is missing Cache-Control guidance.
ACP discovery cache or retry metadata needs review
Evidence log3 steps · 14 lines
Fetch ACP discovery [fail]! ACP discovery content type "text/html" is not JSON-compatible.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=200 contentType="text/html" parsed=false error="Unexpected token '<', \"<!doctype \"... is not valid JSON"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery content type "text/html" is not JSON-compatible.Validate ACP discovery shape [fail]! ACP discovery could not be parsed.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":false,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery could not be parsed.Review ACP cache and retry metadata [warning]! ACP discovery is missing Cache-Control guidance.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=200 cacheControl=null retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"WARNCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"WARNACP discovery is missing Cache-Control guidance.
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 49 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