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:49 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
44/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability68%Agent Easeof Use46%Security& Trust83%GEO, AIO, AEO36%SEO77%Performance15%Accessibility0%
  • AI Discoverability 68 out of 100
  • Agent Ease of Use 46 out of 100
  • Security & Trust 83 out of 100
  • GEO, AIO and AEO 36 out of 100
  • SEO 77 out of 100
  • Performance 15 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

AI Software Development & Data Consulting Partner | DataArt favicon

AI Software Development & Data Consulting Partner | DataArt

DataArt is your trusted AI software development company. Learn how we can help you reduce costs, speed innovation, and boost revenue.

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
68
Needs work3040View details
Discoverability
100
Strong1000
Content Readiness
51
Needs work1300
Bot Access Control
57
Needs work740View details
Agent Ease of Use
46
Priority fix2210View details
API
44
Priority fix700
Auth
41
Priority fix600
MCP
48
Priority fix100
Agent Commerce
58
Needs work700
Google Agentic Browsing
34
Priority fix110View details
GEO, AIO and AEO
36
Priority fix413View details
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
59
Needs work213View details
AEO Readiness
Not Applicable
Not Applicable100
SEO
77
Mostly ready700
SEO
77
Mostly ready700
Security & Trust
83
Mostly ready1800
Security & Trust
83
Mostly ready1800
Performance
15
Priority fix900
Performance
15
Priority fix900

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".

100 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

/ai.txt returned HTTP 405.

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

0/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 405.

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

    ai.txt was reachable but empty.

    /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 is too short to provide useful advisory policy guidance.

    /ai.txt content is incomplete or unsafe
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 405.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=405 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType=null length=0FAIL/ai.txt returned HTTP 405. statusCode=405Validate transport [fail]! ai.txt was reachable but empty.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType=null length=0 lineCount=1FAILCompare media type to preferred text/plain transport actual="missing" expected="text/plain preferred; readable text required"FAILai.txt was reachable but empty.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 [fail]! ai.txt is too short to provide useful advisory policy guidance.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=falseFAILCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}FAILai.txt is too short to provide useful advisory policy guidance.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 0/100 and needs a fix.

8 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks, sourceLinks.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 57/100 and needs improvement.

3 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

Expected exactly one h1, found 0. Only 7 visible words were detected. Heading outline issues were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Visible content clarity

Score

57/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Visible content clarity scored 57/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 75/100 and needs improvement.

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

Only 7 words of visible rendered text were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 75/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Google Search eligibility

AIO: Google Search eligibility scored 80/100 and needs improvement.

2 Warning

Needs attention

AIO: Google Search eligibility

Warning
01

Issue

Only 7 visible words were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Google Search eligibility

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Google Search eligibility scored 80/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](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}

Sign in to see 47 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
44/100Level 2, Agent-LimitedCurrent report