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 8, 2026, 1:57 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
52/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability46%Agent Easeof Use59%Security& Trust76%GEO, AIO, AEO60%SEO100%Performance94%Accessibility0%
  • AI Discoverability 46 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 76 out of 100
  • GEO, AIO and AEO 60 out of 100
  • SEO 100 out of 100
  • Performance 94 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Ambrose Choy - Simply Good Health Tech Enterprises | LinkedIn favicon

Ambrose Choy - Simply Good Health Tech Enterprises | LinkedIn

I am an entrepreneur, product guy, and investor. Specialties: - Product… · Experience: Simply Good Health Tech Enterprises · Education: University of Waterloo · Location: Canada · 500+ connections on LinkedIn. View Ambrose Choy’s profile o...

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
46
Priority fix2200
Discoverability
20
Priority fix200
Content Readiness
50
Needs work1700
Bot Access Control
63
Needs work300
Agent Ease of Use
59
Needs work200
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
60
Needs work712View details
GEO Readiness
69
Needs work312View details
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
76
Mostly ready2011View details
Security & Trust
76
Mostly ready2011View details
Performance
94
Strong1500
Performance
94
Strong1500
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

5 items need attention

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate CSP frame-ancestors".

40 Fail

Needs attention

Frame protection

Failed check
01

Issue

frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.

Details

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

60/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection failed at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.

    CSP frame-ancestors is missing or ineffective
  2. Review CSP and XFO interaction

    CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.

    CSP and X-Frame-Options conflict or leave legacy gaps
Evidence log2 steps · 8 lines
Validate CSP frame-ancestors [fail]! frame-ancestors contains invalid source expressions: *.www.linkedin.com:*.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=true reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=1 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual={"values":["'self'","*.www.linkedin.com:*"],"mode":"malformed","valid":false,"restrictive":false,"broadSources":[]} expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors contains invalid source expressions: *.www.linkedin.com:*."FAILframe-ancestors contains invalid source expressions: *.www.linkedin.com:*.Review CSP and XFO interaction [warning]! CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.INFOReview CSP and XFO interactionINFOCompare modern CSP and legacy XFO behavior modernBrowserMechanism="csp-frame-ancestors" cspOverridesXfo=true cspMode="malformed" xfoDirective="sameorigin"WARNCheck CSP/XFO policy alignment actual="aligned or single mechanism" expected="no conflicting framing policy" issue="CSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting."WARNCSP frame-ancestors controls modern browser behavior, but the X-Frame-Options fallback is invalid or conflicting.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI retrieval access

GEO: AI retrieval access scored 0/100 and needs a fix.

12 Fail

Needs attention

GEO: AI retrieval access

Failed check
01

Issue

Relevant AI retrieval crawler(s) appear blocked for this URL: ChatGPT-User, PerplexityBot, Perplexity-User, ClaudeBot, Claude-User. Snippet or data-nosnippet controls restrict extractable/citable text.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: AI retrieval access

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

GEO: AI retrieval access scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 53/100 and needs improvement.

5 Warning

Needs attention

GEO: Citable passages

Warning
01

Issue

2 explanatory paragraph(s) could be stronger for citation or AI extraction.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

53/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

GEO: Citable passages scored 53/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 63/100 and needs improvement.

4 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, FAQ or question-answer section where appropriate.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

63/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

GEO: Structured extraction scored 63/100 and needs improvement.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "Accessibility audit did not return a result."
}

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