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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability59%Agent Easeof Use42%Security& Trust45%GEO, AIO, AEO57%SEO100%Performance70%Accessibility0%
  • AI Discoverability 59 out of 100
  • Agent Ease of Use 42 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 57 out of 100
  • SEO 100 out of 100
  • Performance 70 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Consulte valor IPVA 2026 pela placa - Placa IPVA favicon

Consulte valor IPVA 2026 pela placa - Placa IPVA

Consulte o valor de IPVA 2026 do veículo pela placa: carros, motos, caminhões e ônibus. Não precisa indicar RENAVAM nem informar o seu email.

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
59
Needs work2511View details
Discoverability
67
Needs work800
Content Readiness
47
Priority fix1411View details
Bot Access Control
63
Needs work300
Agent Ease of Use
42
Priority fix110View details
Skill Discovery
54
Needs work100
Google Agentic Browsing
1
Priority fix010View details
GEO, AIO and AEO
57
Needs work500
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable100
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
70
Needs work1810View details
Performance
70
Needs work1810View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

33 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: json-ld datePublished is not a parseable date (2026-07-03T08:00:00+8:00).; json-ld dateModified is not a parseable date (2026-07-03T08:00:00+8: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

67/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 (2026-07-03T08:00:00+8:00).; json-ld dateModified is not a parseable date (2026-07-03T08:00:00+8: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":"http","channel":"header","property":"Last-Modified","value":"Fri, 31 Jul 2026 08:26:40 GMT","parsed":"2026-07-31T08:26:40.000Z","location":"HTTP response header: Last-Modified"},{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2026-06-25T12:15:02-03:00","parsed":"2026-06-25T15:15:02.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 (2026-07-03T08:00:00+8:00).; json-ld dateModified is not a parseable date (2026-07-03T08:00:00+8: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 (2026-07-03T08:00:00+8:00)."},{"severity":"fail","message":"json-ld dateModified is not a parseable date (2026-07-03T08:00:00+8:00)."}]FAILInvalid freshness date issue found issues=["json-ld datePublished is not a parseable date (2026-07-03T08:00:00+8:00).","json-ld dateModified is not a parseable date (2026-07-03T08:00:00+8: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](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."
}

PerformancePerformanceBrowser audit

Avoid large layout shifts

100 Fail

Check name

Avoid large layout shifts

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

5 layout shifts found

Fix guidance

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)

Evidence
{
  "displayValue": "5 layout shifts found",
  "description": "These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)"
}

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