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 14, 2026, 5:54 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
50/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability44%Agent Easeof Use53%Security& Trust83%GEO, AIO, AEO61%SEO100%Performance78%Accessibility0%
  • AI Discoverability 44 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 83 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 100 out of 100
  • Performance 78 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Compressed air technology | BEKO TECHNOLOGIES favicon

Compressed air technology | BEKO TECHNOLOGIES

BEKO TECHNOLOGIES develops, manufactures and sells components and systems worldwide for an optimised compressed air quality.

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 fix1710View details
Discoverability
67
Needs work800
Content Readiness
20
Priority fix800
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
53
Needs work200
Google Agentic Browsing
67
Needs work200
GEO, AIO and AEO
61
Needs work713View details
GEO Readiness
52
Needs work213View details
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
83
Mostly ready2311View details
Security & Trust
83
Mostly ready2311View details
Performance
78
Mostly ready1600
Performance
78
Mostly ready1600

Prioritized recommendations

Issues ranked by score impact

6 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.

Details

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.

    robots.txt lacks explicit AI crawler rules
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

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate script execution".

32 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

script-src allows dangerous script schemes: blob:, data:.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

68/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate script execution".

Validation steps

  1. Evaluate script execution

    script-src allows dangerous script schemes: blob:, data:.

    CSP script execution policy is unsafe
  2. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri, form-action.

    CSP hardening directives are missing or weak
Evidence log2 steps · 8 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:, data:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-eval'","'unsafe-inline'","blob:","data:","nonce","https://*.b-cdn.net","https://*.beko-technologies.com","https://*.google-analytics.com","https://*.google.com","https://*.google.de","https://*.google.be","https://*.googleadservices.com","https://*.googletagmanager.com","https://*.gstatic.com","https://*.linkedin.com","https://*.mouseflow.com","https://*.recaptcha.net","https://*.usercentrics.eu","https://*.youtube.com","https://app.vwo.com","https://cdn.leadinfo.net","https://code.createjs.com","https://dev.visualwebsiteoptimizer.com","https://hm.baidu.com","https://secure.keep0bury.com","https://snap.licdn.com","https://googleads.g.doubleclick.net","'report-sample'"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":["blob:","data:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows dangerous script schemes: blob:, data:."FAILscript-src allows dangerous script schemes: blob:, data:.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'"] formCount=1WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 0/100 and needs a fix.

9 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 50/100 and needs improvement.

4 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways, FAQ or question-answer section where appropriate, typed JSON-LD structured data.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 50/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 67/100 and needs improvement.

3 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: authorOrOwner, entityLinks.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 80/100 and needs improvement.

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Expected exactly one h1, found 0. Title/H1 terms missing from description: technology.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Entity clarity

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Entity clarity scored 80/100 and needs improvement.

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