CanAgentUse

CanAgentUse products

Agentic Browsing AuditCheck dialogs, menus, drawers, popovers, form errors, checkout steps, and other UI states that a standard Lighthouse scan may not capture.View product 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://le.ac.uk/
SCANNED
Jun 29, 2026, 4:27 PM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability56%Agent Easeof Use55%Security& Trust89%GEO, AIO, AEO67%SEO92%Performance27%Accessibility79%
  • AI Discoverability 56 out of 100
  • Agent Ease of Use 55 out of 100
  • Security & Trust 89 out of 100
  • GEO, AIO and AEO 67 out of 100
  • SEO 92 out of 100
  • Performance 27 out of 100
  • Accessibility 79 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

A Leading UK University | University of Leicester favicon

A Leading UK University | University of Leicester

Discover the University of Leicester - pioneering research, world-class teaching, and a diverse community shaping the future through education and innovation.

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
56
Needs work2720View details
Discoverability
67
Needs work800
Content Readiness
58
Needs work1810View details
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
55
Needs work200
Skill Discovery
54
Needs work100
Google Agentic Browsing
71
Needs work100
GEO, AIO and AEO
67
Needs work900
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
89
Mostly ready2100
Security & Trust
89
Mostly ready2100
Performance
27
Priority fix1010View details
Performance
27
Priority fix1010View details

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 "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

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

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

31/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 "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

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

Evidence log1 step · 6 lines
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=21 unspecified=0

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 (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22)..

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. Check date validity and consistency

    dateModified (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22).; Sitemap lastmod dates and structured modified/upload dates do not appear to agree.

Evidence log1 step · 4 lines
Check date validity and consistency [fail]! dateModified (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-18) is earlier than datePublished (2026-06-23).; dateModified (2026-06-22) is earlier than datePublished (2026-06-23).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-23) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-24).; dateModified (2026-06-22) is earlier than datePublished (2026-06-24).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22).; dateModified (2026-06-18) is earlier than datePublished (2026-06-22).; Sitemap lastmod dates and structured modified/upload dates do not appear to agree.INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=18 expected=0 warningIssueCount=1 issues=[{"severity":"fail","message":"dateModified (2026-06-18) is earlier than datePublished (2026-06-23)."},{"severity":"fail","message":"dateModified (2026-06-22) is earlier than datePublished (2026-06-23)."},{"severity":"fail","message":"dateModified (2026-06-18) is earlier than datePublished (2026-06-23)."},{"severity":"fail","message":"dateModified (2026-06-22) is earlier than datePublished (2026-06-23)."},{"severity":"fail","message":"dateModified (2026-06-23) is earlier than datePublished (2026-06-24)."},{"severity":"fail","message":"dateModified (2026-06-18) is earlier than datePublished (2026-06-24)."},{"severity":"fail","message":"dateModified (2026-06-22) is earlier than datePublished (2026-06-24)."},{"severity":"fail","message":"dateModified (2026-06-23) is earlier than datePublished (2026-06-24)."},{"severity":"fail","message":"dateModified (2026-06-18) is earlier than datePublished (2026-06-24)."},{"severity":"fail","message":"dateModified (2026-06-22) is earlier than datePublished (2026-06-24)."}]FAILInvalid freshness date issue found issues=["dateModified (2026-06-18) is earlier than datePublished (2026-06-23).","dateModified (2026-06-22) is earlier than datePublished (2026-06-23).","dateModified (2026-06-18) is earlier than datePublished (2026-06-23).","dateModified (2026-06-22) is earlier than datePublished (2026-06-23).","dateModified (2026-06-23) is earlier than datePublished (2026-06-24)."]

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 41 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