CanAgentUse

CanAgentUse products

MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

UCP ValidatorUCP Playground

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

MCP Playground

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

A2A Playground

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

Agent Website Viewer
New Scan
https://digital.ai/resource-center/product-briefs/digitalai-agility/
SCANNED
Jul 7, 2026, 11:14 AM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
58/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability74%Agent Easeof Use58%Security& Trust52%GEO, AIO, AEO66%SEO92%Performance97%Accessibility0%
  • AI Discoverability 74 out of 100
  • Agent Ease of Use 58 out of 100
  • Security & Trust 52 out of 100
  • GEO, AIO and AEO 66 out of 100
  • SEO 92 out of 100
  • Performance 97 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Digital.ai Agility | Product Briefs | Digital.ai favicon

Digital.ai Agility | Product Briefs | Digital.ai

Drive consistency and efficiency by scaling agile practices across all levels, fromteams to the entire product portfolio.

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
74
Needs work3411View details
Discoverability
67
Needs work800
Content Readiness
79
Mostly ready2111View details
Bot Access Control
75
Mostly ready500
Agent Ease of Use
58
Needs work523View details
API
67
Needs work100
Skill Discovery
51
Needs work213View details
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
66
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
52
Needs work900
Security & Trust
52
Needs work900
Performance
97
Strong2000
Performance
97
Strong2000

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

45 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Validate discovery index schema did not pass.

Details

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

55/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index failed at "Validate discovery index schema".

Validation steps

  1. Validate discovery index schema

    Serve JSON with $schema set to https://schemas.agentskills.io/discovery/0.2.0/schema.json and a non-empty skills array.

    Agent Skills discovery index schema is invalid
    Top-level issues
    • skills array must not be empty

  2. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  3. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  4. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log4 steps · 14 lines
Validate discovery index schema [fail]INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=true contentTypeCompatible=trueFAILCompare $schema URI actual="https://schemas.agentskills.io/discovery/0.2.0/schema.json" expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills step failedVerify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27)..

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

100/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. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

    Sitemap lastmod corroboration is missing

  2. Check date validity and consistency

    dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=2 attempts=12WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=12Check date validity and consistency [fail]! dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-05-14).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).; dateModified (2024-11-20) is earlier than datePublished (2026-04-27).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=8 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-05-14)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-05-14)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-04-27)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-04-27)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-05-14)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-05-14)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-04-27)."},{"severity":"fail","message":"dateModified (2024-11-20) is earlier than datePublished (2026-04-27)."}]FAILInvalid freshness date issue found issues=["dateModified (2024-11-20) is earlier than datePublished (2026-05-14).","dateModified (2024-11-20) is earlier than datePublished (2026-05-14).","dateModified (2024-11-20) is earlier than datePublished (2026-04-27).","dateModified (2024-11-20) is earlier than datePublished (2026-04-27).","dateModified (2024-11-20) is earlier than datePublished (2026-05-14)."]

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 32 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
58/100Level 3, Bot-AwareCurrent report