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 29, 2026, 8:43 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
37/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability52%Agent Easeof Use44%Security& Trust45%GEO, AIO, AEO29%SEO92%Performance43%Accessibility0%
  • AI Discoverability 52 out of 100
  • Agent Ease of Use 44 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 29 out of 100
  • SEO 92 out of 100
  • Performance 43 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

ゆめ画材 | 国内最大級の品揃え【画材・額縁の通販ショップ】 favicon

ゆめ画材 | 国内最大級の品揃え【画材・額縁の通販ショップ】

取り扱い点数 168,072。国内最大級のオンライン画材通販サイト。絵の具、キャンバス、額縁など取扱い。漫画、油彩画、水彩画、日本画などの画材用品の他、手芸クラフトなど創作活動に関する商品の品揃えも豊富です。

Open Agent View

Next step

Turn this report into a fix workflow

1 failed check is 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
52
Needs work1600
Discoverability
40
Priority fix400
Content Readiness
44
Priority fix800
Bot Access Control
69
Needs work400
Agent Ease of Use
44
Priority fix110View details
Auth
48
Priority fix100
Google Agentic Browsing
23
Priority fix010View details
GEO, AIO and AEO
29
Priority fix241View details
AIO Readiness
Not Applicable
Not Applicable100
AEO Readiness
19
Priority fix141View details
SEO
92
Strong800
SEO
92
Strong800
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
43
Priority fix900
Performance
43
Priority fix900
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

7 items need attention

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

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

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

16 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 36/100 and needs a fix.

4 Fail

Needs attention

AEO: Entity and definition clarity

Failed check
01

Issue

Expected exactly one h1, found 0. Title, h1, description, and opening copy are weakly aligned. 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

36/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: Entity and definition clarity scored 36/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 46/100 and needs a fix.

4 Fail

Needs attention

AEO: Extractable visible copy

Failed check
01

Issue

Only 45 visible words were detected for answer extraction. 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

46/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: Extractable visible copy scored 46/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 47/100 and needs a fix.

4 Fail

Needs attention

AEO: Question and answer structure

Failed check
01

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were 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: Question and answer structure

Score

47/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: Question and answer structure scored 47/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

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

3 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: author, freshnessDate, sameAs.

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

57/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 57/100 and needs improvement.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents) helps AI agents to navigate and interact with the page."
}

AccessibilityAccessibilityBrowser audit

Buttons must have discernible text

100 Fail

Check name

Buttons must have discernible text

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Buttons must have discernible text

Evidence
{
  "ruleId": "button-name",
  "impact": "critical",
  "description": "Ensure buttons have discernible text",
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412",
    "section508",
    "section508.22.a",
    "TTv5",
    "TT6.a",
    "EN-301-549",
    {
      "truncated": true,
      "omittedCount": 4,
      "originalCount": 12
    }
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".btn"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 110
      },
      "failureSummary": "Fix any of the following:\n  Element does not have inner text that is visible to screen readers\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute\n  Element does not have an implicit (wrapped) <label>\n  Element does not have an explicit <label>\n  Element's default semantics were not overridden with role=\"none\" or role=\"presentation\""
    }
  ]
}

Sign in to see 54 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