Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 46 out of 100
- Agent Ease of Use 50 out of 100
- Security & Trust 45 out of 100
- GEO, AIO and AEO 45 out of 100
- SEO 82 out of 100
- Performance 0 out of 100
- Accessibility 48 out of 100
What AI sees of your website
918搏天堂(中国)人生就是搏
918搏天堂(中国)人生就是搏(www.sorealai.com)【百·家·乐·吧✅bjL8.ag✅】,作为领先的数字化转型合作伙伴,918搏天堂数码围绕企业数字化转型的关键要素,开创性的提出“数云融合”战略和技术体系框架,着力在云原生、数字原生、数云融合关键技术和信创产业上架构产品和服务能力
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 | 46 | Priority fix | 18 | 1 | 0 | View details |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 21 | Priority fix | 8 | 0 | 0 | |
| Bot Access Control | 48 | Priority fix | 2 | 1 | 0 | View details |
| Agent Ease of Use | 50 | Needs work | 9 | 2 | 1 | View details |
| API | 50 | Needs work | 4 | 0 | 0 | |
| MCP | 43 | Priority fix | 1 | 0 | 0 | |
| Agent Commerce | 42 | Priority fix | 2 | 2 | 1 | View details |
| Google Agentic Browsing | 67 | Needs work | 2 | 0 | 0 | |
| GEO, AIO and AEO | 45 | Priority fix | 5 | 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 | 1 | 0 | 0 | |
| SEO | 82 | Mostly ready | 6 | 0 | 0 | |
| SEO | 82 | Mostly ready | 6 | 0 | 0 | |
| Security & Trust | 45 | Priority fix | 7 | 1 | 0 | View details |
| Security & Trust | 45 | Priority fix | 7 | 1 | 0 | View details |
| Performance | 0 | Priority fix | 13 | 0 | 0 | |
| Performance | 0 | Priority fix | 13 | 0 | 0 |
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 "Find enforcing CSP delivery".
60 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Find enforcing CSP delivery".
Needs attention
Content-Security-Policy
Issue
Applicable HTML response is missing an enforcing Content-Security-Policy header.
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
40/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 "Find enforcing CSP delivery".
Validation steps
Find enforcing CSP delivery
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.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=200 contentType="application/json" parsed=false error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"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=200 cacheControl="no-transform" retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="no-transform" 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.
Sign in to see 44 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