Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 56 out of 100
- Agent Ease of Use 60 out of 100
- Security & Trust 46 out of 100
- GEO, AIO and AEO 67 out of 100
- SEO 92 out of 100
- Performance 88 out of 100
- Accessibility 78 out of 100
What AI sees of your website
The Luxury Marketplace⢠| LuxuryProperty.com
LuxuryProperty.com- The Luxury Marketplaceā¢. Explore luxury listings: homes, cars, yachts & private jets for sale across the world.
Next step
Turn this report into a fix workflow
3 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 | 56 | Needs work | 32 | 0 | 0 | |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 69 | Needs work | 20 | 0 | 0 | |
| Bot Access Control | 36 | Priority fix | 4 | 0 | 0 | |
| Agent Ease of Use | 60 | Needs work | 40 | 7 | 5 | View details |
| API | 88 | Mostly ready | 12 | 0 | 0 | |
| Auth | 46 | Priority fix | 8 | 0 | 0 | |
| MCP | 37 | Priority fix | 3 | 0 | 0 | |
| Skill Discovery | 43 | Priority fix | 5 | 4 | 5 | View details |
| Agent Commerce | 46 | Priority fix | 9 | 3 | 0 | View details |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 67 | Needs work | 9 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 46 | Priority fix | 8 | 0 | 0 | |
| Security & Trust | 46 | Priority fix | 8 | 0 | 0 | |
| Performance | 88 | Mostly ready | 14 | 0 | 0 | |
| Performance | 88 | Mostly ready | 14 | 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".
55 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
protocol.version must be a YYYY-MM-DD date string.
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
45/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
protocol.version must be a YYYY-MM-DD date string.
ACP discovery protocol metadata is invalid
protocol.version must be a YYYY-MM-DD date string.
protocol.supported_versions must be a non-empty array.
transports must include rest.
Validate ACP endpoint and transports
transports does not include rest.
ACP API endpoint or transport metadata is unsafe or incomplete
Transport "https" is not recognized for this ACP check version.
Validate ACP capabilities
capabilities.services is missing or empty.
ACP capability declarations are invalid or unstable
Evidence log3 steps Ā· 16 lines
Validate ACP discovery shape [fail]! protocol.version must be a YYYY-MM-DD date string.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":true,"protocolName":"acp"} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"protocolVersion":"1.0","supportedVersionCount":0,"supportedVersionsOrdered":true,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILprotocol.version must be a YYYY-MM-DD date string.Validate ACP endpoint and transports [fail]! transports does not include rest.INFOValidate ACP endpoint and transports status="fail"INFOValidate ACP API base URL and supported transportsFAILCheck safe HTTPS api_base_url actual=true expected=true apiBaseUrl="https://www.luxuryproperty.com"FAILCheck REST transport support actual=false expected=true transports=["https"] transportWarnings=["Transport \"https\" is not recognized for this ACP check version."]FAILtransports does not include rest.Validate ACP capabilities [fail]! capabilities.services is missing or empty.INFOValidate ACP capabilities status="fail"INFOValidate ACP services, extensions, intervention types, currencies, and localesFAILCheck capabilities object actual=true 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=[]FAILcapabilities.services is missing or empty.
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
30 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
Needs attention
Agent Skills index
Issue
Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.
Details
Why it matters
An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.
Check name
Agent Skills index
Score
40/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.
Result
Agent Skills index failed at "Validate discovery index schema".
Validation steps
Validate discovery index schema
Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.
Agent Skills discovery index schema is invalid
Top-level issues
- $schema must be https://schemas.agentskills.io/discovery/0.2.0/schema.json
Invalid skills
[ { "index": 0, "valid": false, "name": "api-catalog", "type": "discovery", "description": "API catalog for automated API discovery.", "url": "https://www.luxuryproperty.com/.well-known/api-catalog", "digest": "", "resolvedUrl": "https://www.luxuryproperty.com/.well-known/api-catalog", "originClass": "same-origin", "missing": [ "digest" ], "invalid": [ "type must be skill-md or archive" ], "warnings": [] }, { "index": 1, "valid": false, "name": "robots-policy", "type": "policy", "description": "Robots.txt and content signal policy.", "url": "https://www.luxuryproperty.com/robots.txt", "digest": "", "resolvedUrl": "https://www.luxuryproperty.com/robots.txt", "originClass": "same-origin", "missing": [ "digest" ], "invalid": [ "type must be skill-md or archive" ], "warnings": [ "description should explain when to use the skill" ] } ]Validate skill entries
One or more Agent Skills entries have invalid required fields.
One or more skill entries are invalid
Skill entry findings
[ { "index": 0, "valid": false, "name": "api-catalog", "type": "discovery", "description": "API catalog for automated API discovery.", "url": "https://www.luxuryproperty.com/.well-known/api-catalog", "digest": "", "resolvedUrl": "https://www.luxuryproperty.com/.well-known/api-catalog", "originClass": "same-origin", "missing": [ "digest" ], "invalid": [ "type must be skill-md or archive" ], "warnings": [] }, { "index": 1, "valid": false, "name": "robots-policy", "type": "policy", "description": "Robots.txt and content signal policy.", "url": "https://www.luxuryproperty.com/robots.txt", "digest": "", "resolvedUrl": "https://www.luxuryproperty.com/robots.txt", "originClass": "same-origin", "missing": [ "digest" ], "invalid": [ "type must be skill-md or archive" ], "warnings": [ "description should explain when to use the skill" ] } ]Verify advertised artifacts
No valid skill artifacts were available to verify.
Validate skill content
For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.
Review skill artifact security
Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.
Evidence log5 steps Ā· 20 lines
Validate discovery index schema [fail]! Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=true contentTypeCompatible=trueFAILCompare $schema URI actual="https://agentskills.io/schemas/agent-skills-index-v0.2.0.json" expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0WARNCompare unknown top-level field count actual=2 expected=0FAILAgent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.Validate skill entries [fail]! One or more Agent Skills entries have invalid required fields.INFOValidate skill entriesFAILCompare advertised skill count actual=2 expected="> 0"FAILCompare valid skill entry count actual=0 expected="same as advertised skill count"FAILInvalid skill entry skill={"index":0,"valid":false,"name":"api-catalog","type":"discovery","description":"API catalog for automated API discovery.","url":"https://www.luxuryproperty.com/.well-known/api-catalog","digest":"","resolvedUrl":"https://www.luxuryproperty.com/.well-known/api-catalog","originClass":"same-origin","missing":["digest"],"invalid":["type must be skill-md or archive"],"warnings":[]}FAILInvalid skill entry skill={"index":1,"valid":false,"name":"robots-policy","type":"policy","description":"Robots.txt and content signal policy.","url":"https://www.luxuryproperty.com/robots.txt","digest":"","resolvedUrl":"https://www.luxuryproperty.com/robots.txt","originClass":"same-origin","missing":["digest"],"invalid":["type must be skill-md or archive"],"warnings":["description should explain when to use the skill"]}FAILOne or more Agent Skills entries have invalid required fields.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Detect A2A card version".
26 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
48/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
A2A Agent Card response is not valid JSON.
A2A Agent Card shape is invalid for its version
Validate HTTP delivery
The card was parseable JSON but was not served with a JSON-compatible content type.
A2A Agent Card HTTP delivery is not standards-aligned
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 log4 steps Ā· 17 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]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html; charset=utf-8" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.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.
Sign in to see 43 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