Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 61 out of 100
- Agent Ease of Use 62 out of 100
- Security & Trust 81 out of 100
- GEO, AIO and AEO 69 out of 100
- SEO 92 out of 100
- Performance 88 out of 100
- Accessibility 58 out of 100
What AI sees of your website
PCI Security Standards Council – Protect Payment Data with Industry-driven Security Standards, Training, and Programs
A global forum that brings together payments industry stakeholders to develop and drive adoption of data security standards and resources for safe payments.
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 | 61 | Needs work | 33 | 1 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 76 | Mostly ready | 24 | 0 | 0 | |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 62 | Needs work | 3 | 0 | 0 | |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Google Agentic Browsing | 100 | Strong | 2 | 0 | 0 | |
| GEO, AIO and AEO | 69 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 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 | 81 | Mostly ready | 19 | 1 | 2 | View details |
| Security & Trust | 81 | Mostly ready | 19 | 1 | 2 | View details |
| Performance | 88 | Mostly ready | 13 | 1 | 0 | View details |
| Performance | 88 | Mostly ready | 13 | 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=0Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
35 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
Needs attention
Content-Security-Policy
Issue
default-src allows dangerous script schemes: blob:, data:.
Details
Why it matters
Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.
Check name
Content-Security-Policy
Score
65/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Evaluate script execution".
Validation steps
Evaluate script execution
default-src allows dangerous script schemes: blob:, data:.
CSP script execution policy is unsafe
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri, form-action.
CSP hardening directives are missing or weak
Review CSP reporting
CSP does not define a reporting endpoint.
CSP reporting is missing or incomplete
Evidence log3 steps · 12 lines
Evaluate script execution [fail]! default-src allows dangerous script schemes: blob:, data:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="default-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","fast.fonts.net","*.hubspot.com","*.akamaihd.net","*.vimeo.com","*.hsforms.net","*.sharethis.com","*.google-analytics.com","*.gstatic.com","*.twitter.com","*.addthis.com","*.googleapis.com","*.youtube.com","*.adyen.com","*.hs-scripts.com","*.hs-analytics.net","*.twimg.com","*.wowza.com","*.pcissc.org","latencytimer.azurewebsites.net","cc.cdn.civiccomputing.com","cdnjs.cloudflare.com","cdn.parsely.com","api.parsely.com","p1.parsely.com","*.googletagmanager.com","stats.g.doubleclick.net","apikeys.civiccomputing.com","*.cludo.com","publuu.com","*.pcisecuritystandards.org","*.force.com","pcisecuritystandards.studio","*.hsforms.com","blob:","data:"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":true,"hasBroadScheme":false,"dangerousSchemes":["blob:","data:"]} expected="constrained script sources without unsafe execution allowances" issue="default-src allows dangerous script schemes: blob:, data:."FAILdefault-src allows dangerous script schemes: blob:, data:.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","'unsafe-inline'","'unsafe-eval'","fast.fonts.net","*.hubspot.com","*.akamaihd.net","*.vimeo.com","*.hsforms.net","*.sharethis.com","*.google-analytics.com","*.gstatic.com","*.twitter.com","*.addthis.com","*.googleapis.com","*.youtube.com","*.adyen.com","*.hs-scripts.com","*.hs-analytics.net","*.twimg.com","*.wowza.com","*.pcissc.org","latencytimer.azurewebsites.net","cc.cdn.civiccomputing.com","cdnjs.cloudflare.com","cdn.parsely.com","api.parsely.com","p1.parsely.com","*.googletagmanager.com","stats.g.doubleclick.net","apikeys.civiccomputing.com","*.cludo.com","publuu.com","*.pcisecuritystandards.org","*.force.com","pcisecuritystandards.studio","*.hsforms.com","blob:","data:"] formCount=1WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
PerformancePerformanceBrowser audit
Document request latency
100 Fail
PerformancePerformanceBrowser audit
Document request latency
Check name
Document request latency
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 510Â ms
Fix guidance
Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
References
web.dev/learn/performanceEvidence
{
"displayValue": "Est savings of 510Â ms",
"description": "Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression."
}Sign in to see 40 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 |
|---|---|---|---|
| 67/100 | Level 3, Bot-Aware | Current report |