Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 38 out of 100
- Agent Ease of Use 46 out of 100
- Security & Trust 63 out of 100
- GEO, AIO and AEO 53 out of 100
- SEO 83 out of 100
- Performance 59 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Skigit | Thirty Seconds on Skigit could change your life!
You gotta check this out. Thirty seconds on Skigit could change your life!
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 | 38 | Priority fix | 18 | 0 | 0 | |
| Discoverability | 47 | Priority fix | 6 | 0 | 0 | |
| Content Readiness | 33 | Priority fix | 9 | 0 | 0 | |
| Bot Access Control | 36 | Priority fix | 3 | 0 | 0 | |
| Agent Ease of Use | 46 | Priority fix | 34 | 6 | 2 | View details |
| API | 47 | Priority fix | 7 | 0 | 0 | |
| Auth | 49 | Priority fix | 6 | 0 | 0 | |
| MCP | 45 | Priority fix | 4 | 0 | 0 | |
| Skill Discovery | 48 | Priority fix | 7 | 2 | 1 | View details |
| Agent Commerce | 54 | Needs work | 9 | 3 | 1 | View details |
| Google Agentic Browsing | 33 | Priority fix | 1 | 1 | 0 | View details |
| GEO, AIO and AEO | 53 | Needs work | 6 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| SEO | 83 | Mostly ready | 7 | 0 | 0 | |
| SEO | 83 | Mostly ready | 7 | 0 | 0 | |
| Security & Trust | 63 | Needs work | 15 | 0 | 0 | |
| Security & Trust | 63 | Needs work | 15 | 0 | 0 | |
| Performance | 59 | Needs work | 13 | 0 | 0 | |
| Performance | 59 | Needs work | 13 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".
57 Fail
Agent Ease of UseAgent CommerceInformational
ACP - Agentic Commerce Protocol
ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".
Needs attention
ACP - Agentic Commerce Protocol
Issue
ACP discovery is missing protocol.
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
43/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 "Validate ACP discovery shape".
Validation steps
Validate ACP discovery shape
ACP discovery is missing protocol.
ACP discovery protocol metadata is invalid
ACP discovery is missing protocol.
ACP discovery is missing api_base_url.
ACP discovery is missing transports array.
Validate ACP endpoint and transports
api_base_url is missing or unsafe.
ACP API endpoint or transport metadata is unsafe or incomplete
Validate ACP capabilities
ACP discovery is missing capabilities.
ACP capability declarations are invalid or unstable
Review ACP cache and retry metadata
ACP discovery is missing Cache-Control guidance.
ACP discovery cache or retry metadata needs review
Evidence log4 steps · 21 lines
Validate ACP discovery shape [fail]! ACP discovery is missing protocol.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":true,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery is missing protocol.Validate ACP endpoint and transports [fail]! api_base_url is missing or unsafe.INFOValidate ACP endpoint and transports status="fail"INFOValidate ACP API base URL and supported transportsFAILCheck safe HTTPS api_base_url actual=false expected=trueFAILCheck REST transport support actual=false expected=true transports=[] transportWarnings=[]FAILapi_base_url is missing or unsafe.Validate ACP capabilities [fail]! ACP discovery is missing capabilities.INFOValidate ACP capabilities status="fail"INFOValidate ACP services, extensions, intervention types, currencies, and localesFAILCheck capabilities object actual=false expected=trueFAILCheck stable ACP service declarations actual=[] expected="one or more known services such as checkout, orders, or delegate_payment"FAILCheck ACP capability values use stable service, extension, intervention, currency, and locale names actual="no compatibility warnings" expected="no unknown or unstable capability values" warnings=[]FAILACP discovery is missing capabilities.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 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
Missing required fields
- skills[]
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=["skills[]"] expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]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 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 56 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
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 41/100 | Level 2, Agent-Limited | Current report |