Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 61 out of 100
- Agent Ease of Use 55 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 64 out of 100
- SEO 92 out of 100
- Performance 100 out of 100
- Accessibility 58 out of 100
What AI sees of your website
Low-Code Platform - Build Online Database Apps | Caspio
Create powerful online database applications with Caspio's leading low-code platform. Build web apps, automate tasks and more with little to no code.
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 | 61 | Needs work | 38 | 0 | 0 | |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 59 | Needs work | 24 | 0 | 0 | |
| Bot Access Control | 58 | Needs work | 6 | 0 | 0 | |
| Agent Ease of Use | 55 | Needs work | 25 | 7 | 5 | View details |
| API | 37 | Priority fix | 3 | 4 | 1 | View details |
| Auth | 54 | Needs work | 5 | 0 | 0 | |
| MCP | 42 | Priority fix | 4 | 0 | 0 | |
| Skill Discovery | 55 | Needs work | 3 | 1 | 3 | View details |
| Agent Commerce | 45 | Priority fix | 7 | 2 | 1 | View details |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 64 | Needs work | 8 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 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 | 45 | Priority fix | 7 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 0 | 0 | |
| Performance | 100 | Strong | 19 | 0 | 0 | |
| Performance | 100 | Strong | 19 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
63 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog media type".
Needs attention
API Catalog
Issue
Content-Type "null" is not valid for an RFC 9727 API catalog.
Details
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
37/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog media type".
Validation steps
Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
API catalog HEAD Link discovery is incomplete
Validate API catalog media type
Content-Type "null" is not valid for an RFC 9727 API catalog.
API catalog media type is not application/linkset+json
Validate Linkset shape
Unexpected end of JSON input
API catalog Linkset shape is invalid
Unexpected end of JSON input
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
API catalog lacks useful API relations
Validate API catalog targets
API catalog did not expose any href targets to validate.
API catalog targets are unreachable or media types mismatch
Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=204 contentType=nullWARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [fail]! Content-Type "null" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual=null expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "null" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected end of JSON inputINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected end of JSON input"FAILLinkset JSON parse error error="Unexpected end of JSON input"FAILUnexpected end of JSON inputClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.
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 was reachable but did not parse as JSON.
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 was reachable but did not parse as JSON.
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 Cache-Control does not include max-age.
ACP discovery cache or retry metadata needs review
Evidence log3 steps · 14 lines
Fetch ACP discovery [fail]! ACP discovery was reachable but did not parse as JSON.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=204 contentType=null parsed=false error="Unexpected end of JSON input"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery was reachable but did not parse as JSON.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 Cache-Control does not include max-age.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=204 cacheControl="private, no-cache, no-store, must-revalidate" retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="private, no-cache, no-store, must-revalidate" 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 Cache-Control does not include max-age.
Agent Ease of UseSkill DiscoveryEmerging recommendation
Agent Skills index
Agent Skills index failed at "Validate discovery index schema".
45 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 was not served with a JSON-compatible Content-Type.
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
55/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 was not served with a JSON-compatible Content-Type.
Agent Skills discovery index schema is invalid
Response is not valid JSON.
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 log4 steps · 14 lines
Validate discovery index schema [fail]! Agent Skills index was not served with a JSON-compatible Content-Type.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=false contentTypeCompatible=falseFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index was not served with a JSON-compatible Content-Type.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
Sign in to see 36 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