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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability68%Agent Easeof Use45%Security& Trust45%GEO, AIO, AEO50%SEO100%Performance89%Accessibility0%
  • AI Discoverability 68 out of 100
  • Agent Ease of Use 45 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 50 out of 100
  • SEO 100 out of 100
  • Performance 89 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Get All Information Related to Airports Terminal favicon

Get All Information Related to Airports Terminal

Get Airports Terminal Details Easily And Quickly Search Terminal Guides Turkish Airlines Asiana Airlines Delta Airlines Ethiopian Airlines Spirit Airlines

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 work2800
Discoverability
67
Needs work800
Content Readiness
67
Needs work1600
Bot Access Control
69
Needs work400
Agent Ease of Use
45
Priority fix1140View details
API
50
Needs work400
Auth
41
Priority fix630View details
Google Agentic Browsing
33
Priority fix110View details
GEO, AIO and AEO
50
Needs work600
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable100
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
89
Mostly ready1600
Performance
89
Mostly ready1600
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

90 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=UTF-8" is not Markdown or text/plain; missing registration instructions; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.

Details

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

10/100

Status

fail

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=UTF-8" is not Markdown or text/plain; missing registration instructions; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.

    /auth.md is missing or not usable as agent registration guidance
  2. Validate protected resource metadata

    OAuth Protected Resource Metadata could not be fetched.

    Auth.md protected-resource metadata is missing or incomplete
  3. Validate Auth.md authorization metadata

    OAuth authorization-server metadata could not be fetched.

    Authorization-server metadata lacks Auth.md v1 fields
Evidence log3 steps · 20 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=UTF-8" is not Markdown or text/plain; missing registration instructions; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/html; charset=UTF-8" bytes=194548FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=182688 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. Content-Type \"text/html; charset=UTF-8\" is not Markdown or text/plain; missing registration instructions; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. Content-Type "text/html; charset=UTF-8" is not Markdown or text/plain; missing registration instructions; missing OAuth Protected Resource Metadata discovery guidance; missing OAuth authorization-server metadata guidance; missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance.Validate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" contentType=null bytes=0 error="TimeoutError: The operation was aborted due to timeout"FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" contentType=null bytes=0 error="TimeoutError: The operation was aborted due to timeout"FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.

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

AccessibilityAccessibilityBrowser audit

Certain ARIA roles must contain particular children

100 Fail

Check name

Certain ARIA roles must contain particular children

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Certain ARIA roles must contain particular children

Evidence
{
  "ruleId": "aria-required-children",
  "impact": "critical",
  "description": "Ensure elements with an ARIA role that require child roles contain them",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131",
    "EN-301-549",
    "EN-9.1.3.1",
    "RGAAv4",
    "RGAA-9.3.1"
  ],
  "affectedNodeCount": 6,
  "nodes": [
    {
      "target": [
        ".elementor-element-b55ada0 > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    },
    {
      "target": [
        ".elementor-element-da1318f > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    },
    {
      "target": [
        ".elementor-element-55885e6 > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    },
    {
      "target": [
        ".elementor-element-7da3343 > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    },
    {
      "target": [
        ".elementor-element-d6a6889 > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    },
    {
      "target": [
        ".elementor-element-f615f32 > .elementor-widget-container > .elementor-loop-container.elementor-grid[role=\"list\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 65
      },
      "failureSummary": "Fix any of the following:\n  Element has children which are not allowed: a, h1"
    }
  ]
}

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