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 11, 2026, 10:35 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
55/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability44%Agent Easeof Use51%Security& Trust83%GEO, AIO, AEO55%SEO100%Performance90%Accessibility43%
  • AI Discoverability 44 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 83 out of 100
  • GEO, AIO and AEO 55 out of 100
  • SEO 100 out of 100
  • Performance 90 out of 100
  • Accessibility 43 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

North Data Smarte Recherche favicon

North Data Smarte Recherche

Wirtschaftsinformationen, finanzielle Kennzahlen, Verflechtungen: kostenlose Online-Recherche, Daten und API

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
44
Priority fix1831View details
Discoverability
48
Priority fix500
Content Readiness
28
Priority fix1000
Bot Access Control
54
Needs work331View details
Agent Ease of Use
51
Needs work721View details
API
50
Needs work400
Agent Commerce
72
Needs work211View details
Google Agentic Browsing
33
Priority fix110View details
GEO, AIO and AEO
55
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
83
Mostly ready1900
Security & Trust
83
Mostly ready1900
Performance
90
Strong1400
Performance
90
Strong1400

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEmerging recommendation

ai.txt policy

ai.txt policy failed at "Fetch /ai.txt".

82 Fail

Needs attention

ai.txt policy

Failed check
01

Issue

/ai.txt returned HTTP 429.

Details

02

Why it matters

ai.txt is a fragmented emerging convention. It can communicate human-readable AI crawling, training, attribution, restriction, and contact guidance, but it is not a standard access-control mechanism and absence should not be penalized.

Check name

ai.txt policy

Score

18/100

Status

fail

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish an advisory human-readable AI usage policy only when the site intentionally needs one.

Result

ai.txt policy failed at "Fetch /ai.txt".

Validation steps

  1. Fetch /ai.txt

    /ai.txt returned HTTP 429.

    /ai.txt could not be fetched when present
  2. Validate transport

    ai.txt appears to be an HTML page or error document rather than a plain-text policy.

    /ai.txt transport is invalid or not plain text
  3. Parse ai.txt policy

    Transport validation failed before policy parsing could be trusted.

    /ai.txt policy format is missing required sections or non-standard
  4. Validate policy content

    ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

    /ai.txt content is incomplete or unsafe
Evidence log4 steps · 18 lines
Fetch /ai.txt [fail]! /ai.txt returned HTTP 429.INFOFetch /ai.txtINFORequesting optional advisory policy file at /ai.txtFAILCompare /ai.txt HTTP response actual=429 expected="2xx when ai.txt is intentionally published; 404/410 means absent optional file" contentType="text/html;charset=utf-8" length=8579FAIL/ai.txt returned HTTP 429. statusCode=429Validate transport [fail]! ai.txt appears to be an HTML page or error document rather than a plain-text policy.INFOValidate transportINFOChecking ai.txt media type, size, line count, and whether the response looks like plain text contentType="text/html;charset=utf-8" length=8579 lineCount=427FAILCompare media type to preferred text/plain transport actual="text/html" expected="text/plain preferred; readable text required"FAILai.txt appears to be an HTML page or error document rather than a plain-text policy.Parse ai.txt policy [fail]! Transport validation failed before policy parsing could be trusted.INFOParse ai.txt policyINFODetecting ai.txt convention from bracket sections, frontmatter, headings, and ai.txt context linksINFODetected policy structure convention="unknown-text" sections=[] markdownHeadings=[]WARNCheck AI Visibility required sections actual="missing identity, permissions, restrictions" expected="identity, permissions, and restrictions" missingRecommended=["attribution","contact","content-types"]WARNTransport validation failed before policy parsing could be trusted.Validate policy content [warning]! ai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.INFOValidate policy contentINFOChecking required section content, permission/restriction language, attribution, contact details, and safety risks convention="unknown-text"INFODetected policy signals hasPermissionLanguage=false hasRestrictionLanguage=false hasTrainingLanguage=false hasAttributionLanguage=false hasContact=falseWARNCheck required and recommended section coverage actual={"missingRequired":["identity","permissions","restrictions"],"missingRecommended":["attribution","contact","content-types"]} expected={"missingRequired":[],"recommendedPresentWhenPossible":true}WARNai.txt does not follow the AI Visibility section model; treating it as non-standard advisory text.

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".

28 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery returned 429 or 503 without Retry-After.

Details

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

72/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol failed at "Review ACP cache and retry metadata".

Validation steps

  1. Fetch ACP discovery

    ACP-like signals were found, but /.well-known/acp.json was not available.

    ACP discovery is missing or not parseable
  2. Review ACP cache and retry metadata

    ACP discovery returned 429 or 503 without Retry-After.

    ACP discovery cache or retry metadata needs review
Evidence log2 steps · 10 lines
Fetch ACP discovery [warning]! ACP-like signals were found, but /.well-known/acp.json was not available.INFOFetch ACP discovery status="warning"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=429 contentType="text/html;charset=utf-8" parsed=falseINFOFetch compatibility ACP discovery /.well-known/acp statusCode=429 contentType="text/html;charset=utf-8" parsed=falseWARNCheck canonical ACP discovery response actual=false expected=true canonicalFound=false compatibilityFound=falseWARNACP-like signals were found, but /.well-known/acp.json was not available.Review ACP cache and retry metadata [fail]! ACP discovery returned 429 or 503 without Retry-After.INFOReview ACP cache and retry metadata status="fail"INFOInspect ACP discovery cache headers and retry guidance statusCode=429 cacheControl=null retryAfter=nullFAILCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"FAILCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"FAILACP discovery returned 429 or 503 without Retry-After.

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