Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 64 out of 100
- Agent Ease of Use 63 out of 100
- Security & Trust 96 out of 100
- GEO, AIO and AEO 63 out of 100
- SEO 91 out of 100
- Performance 97 out of 100
- Accessibility 100 out of 100
What AI sees of your website
Stripe Dot Dev
Learn how to build web and mobile applications to accept payments, send payouts, and manage your business online with Stripe.
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 | 64 | Needs work | 27 | 1 | 0 | View details |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 36 | Priority fix | 14 | 0 | 0 | |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 63 | Needs work | 15 | 1 | 2 | View details |
| API | 69 | Needs work | 10 | 1 | 2 | View details |
| MCP | 50 | Needs work | 2 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 63 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 91 | Strong | 7 | 0 | 0 | |
| SEO | 91 | Strong | 7 | 0 | 0 | |
| Security & Trust | 96 | Strong | 23 | 0 | 0 | |
| Security & Trust | 96 | Strong | 23 | 0 | 0 | |
| Performance | 97 | Strong | 20 | 1 | 0 | View details |
| Performance | 97 | Strong | 20 | 1 | 0 | View details |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate Linkset shape".
27 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate Linkset shape".
Needs attention
API Catalog
Issue
Target 0 for relation "oauth-scopes" is not an object.
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
73/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 Linkset shape".
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
The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.
API catalog media type is not application/linkset+json
Validate Linkset shape
Target 0 for relation "oauth-scopes" is not an object.
API catalog Linkset shape is invalid
oauth-scopes: Target 0 for relation "oauth-scopes" is not an object.
oauth-scopes: Target 1 for relation "oauth-scopes" is not an object.
Evidence log3 steps · 15 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=200 contentType="application/linkset+json; charset=utf-8"WARNCompare 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 [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json; charset=utf-8" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate Linkset shape [fail]! Target 0 for relation "oauth-scopes" is not an object.INFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=true expected=trueFAILCompare top-level linkset item count actual=3 expected="> 0"FAILCompare extracted href target count actual=12 expected="> 0"FAILLinkset href issue rel="oauth-scopes" issue="Target 0 for relation \"oauth-scopes\" is not an object."FAILLinkset href issue rel="oauth-scopes" issue="Target 1 for relation \"oauth-scopes\" is not an object."FAILTarget 0 for relation "oauth-scopes" is not an object.
PerformancePerformanceBrowser audit
Font display
100 Fail
PerformancePerformanceBrowser audit
Font display
Check name
Font display
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 30 ms
Fix guidance
Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
References
web.dev/learn/performanceEvidence
{
"displayValue": "Est savings of 30 ms",
"description": "Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks)."
}Sign in to see 27 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