CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 14, 2026, 4:21 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
67/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability57%Agent Easeof Use53%Security& Trust93%GEO, AIO, AEO65%SEO92%Performance95%Accessibility65%
  • AI Discoverability 57 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 93 out of 100
  • GEO, AIO and AEO 65 out of 100
  • SEO 92 out of 100
  • Performance 95 out of 100
  • Accessibility 65 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

EE88 - Nhà Cái Uy Tín #1 VN 2026 | Đánh Giá Độc Lập favicon

EE88 - Nhà Cái Uy Tín #1 VN 2026 | Đánh Giá Độc Lập

EE88 - Nhà cái cá cược uy tín 2026. Đánh giá độc lập: giấy phép Curaçao 8048/JAZ, RTP 96-98%, nạp rút 4 phút. 24 tháng thử nghiệm.

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
57
Needs work2542View details
Discoverability
40
Priority fix400
Content Readiness
71
Needs work1711View details
Bot Access Control
59
Needs work431View details
Agent Ease of Use
53
Needs work200
Google Agentic Browsing
67
Needs work200
GEO, AIO and AEO
65
Needs work813View details
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
51
Needs work213View details
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
93
Strong2500
Security & Trust
93
Strong2500
Performance
95
Strong1700
Performance
95
Strong1700

Prioritized recommendations

Issues ranked by score impact

6 items need attention

AI DiscoverabilityBot Access ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Fetch /ai.txt".

82 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

/ai.txt returned HTTP 503.

Details

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

18/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Fetch /ai.txt".

Validation steps

  1. Fetch /ai.txt

    /ai.txt returned HTTP 503.

    /ai.txt could not be fetched when present
  2. Validate transport

    ai.txt appears to be an HTML page or error document rather than a plain-text policy.

    /ai.txt transport is invalid or not plain text
  3. Parse ai.txt policy

    Transport validation failed before policy parsing could be trusted.

    /ai.txt policy format is missing required sections or non-standard
  4. Validate policy content

    ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

    /ai.txt content is incomplete or unsafe
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 503.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=503 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/html" length=805FAIL/ai.txt returned HTTP 503. statusCode=503Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html" length=805 lineCount=14FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="unknown-text" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 0/100 and needs a fix.

9 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

21 section(s) bury or omit a concise opening answer. No direct definition pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 71/100 and needs improvement.

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

No direct definition sentence was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

71/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Entity and definition clarity scored 71/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 71/100 and needs improvement.

3 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: sameAs, policyLinks.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

71/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 71/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 81/100 and needs improvement.

2 Warning

Needs attention

AEO: Extractable visible copy

Warning
01

Issue

Visible text has few answer-oriented terms or explanatory markers.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Extractable visible copy

Score

81/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Extractable visible copy scored 81/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: dateModified (2026-07-11) is earlier than datePublished (2026-07-11T11:00:00+07:00)..

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

100/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

    Sitemap lastmod corroboration is missing
  2. Check date validity and consistency

    dateModified (2026-07-11) is earlier than datePublished (2026-07-11T11:00:00+07:00).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=6 attempts=6WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=6Check date validity and consistency [fail]! dateModified (2026-07-11) is earlier than datePublished (2026-07-11T11:00:00+07:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=1 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2026-07-11) is earlier than datePublished (2026-07-11T11:00:00+07:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-07-11) is earlier than datePublished (2026-07-11T11:00:00+07:00)."]

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.

Fix with MCP / CLI

Score history