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, 3:18 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
46/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability40%Agent Easeof Use50%Security& Trust57%GEO, AIO, AEO65%SEO83%Performance87%Accessibility0%
  • AI Discoverability 40 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 57 out of 100
  • GEO, AIO and AEO 65 out of 100
  • SEO 83 out of 100
  • Performance 87 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Enterprise data. Anywhere. Anytime. Always-on. AI-Ready. | Cirata favicon

Enterprise data. Anywhere. Anytime. Always-on. AI-Ready. | Cirata

Modernize your data, ensure organizational resilience, and accelerate AI ambitions, all with zero risk or downtime with Cirata.

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
40
Priority fix1531View details
Discoverability
33
Priority fix500
Content Readiness
49
Priority fix1011View details
Bot Access Control
38
Priority fix020View details
Agent Ease of Use
50
Needs work110View details
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
65
Needs work900
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
83
Mostly ready700
SEO
83
Mostly ready700
Security & Trust
57
Needs work1400
Security & Trust
57
Needs work1400
Performance
87
Mostly ready1200
Performance
87
Mostly ready1200

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 "Fetch robots.txt".

100 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No robots.txt content was available to inspect for AI bot rules.

Details

02

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

0/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 "Fetch robots.txt".

Validation steps

  1. Fetch robots.txt

    No robots.txt content was available to inspect for AI bot rules.

    robots.txt is missing for AI crawler policy inspection
  2. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

50 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: json-ld datePublished is not a parseable date (2020-01-10T00: 00: 00+00: 00).; json-ld dateModified is not a parseable date (2020-01-10T00: 00: 00+00: 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

50/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. Validate structured freshness dates

    No Schema.org freshness dates were found.

    Structured freshness dates are missing or invalid
  2. Check date validity and consistency

    json-ld datePublished is not a parseable date (2020-01-10T00: 00: 00+00: 00).; json-ld dateModified is not a parseable date (2020-01-10T00: 00: 00+00: 00).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Validate structured freshness dates [warning]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaWARNCheck structured freshness date count actual=2 expected="> 0" invalidDateCount=2 formats={"json-ld":2} alternateDates=[{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2025-08-11","parsed":"2025-08-11T00:00:00.000Z","location":"matching sitemap <lastmod> entry for this page URL"}]WARNStructured freshness dates include invalid values invalidDateCount=2Check date validity and consistency [fail]! json-ld datePublished is not a parseable date (2020-01-10T00: 00: 00+00: 00).; json-ld dateModified is not a parseable date (2020-01-10T00: 00: 00+00: 00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=2 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"json-ld datePublished is not a parseable date (2020-01-10T00: 00: 00+00: 00)."},{"severity":"fail","message":"json-ld dateModified is not a parseable date (2020-01-10T00: 00: 00+00: 00)."}]FAILInvalid freshness date issue found issues=["json-ld datePublished is not a parseable date (2020-01-10T00: 00: 00+00: 00).","json-ld dateModified is not a parseable date (2020-01-10T00: 00: 00+00: 00)."]

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 45 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
46/100Level 2, Agent-LimitedCurrent report