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 28, 2026, 5:21 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
77/100

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability78%Agent Easeof Use60%Security& Trust91%GEO, AIO, AEO64%SEO92%Performance95%Accessibility93%
  • AI Discoverability 78 out of 100
  • Agent Ease of Use 60 out of 100
  • Security & Trust 91 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 92 out of 100
  • Performance 95 out of 100
  • Accessibility 93 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Lime Sportadmin - Förenkla vardagen för er förening favicon

Lime Sportadmin - Förenkla vardagen för er förening

Hela föreningens administration på samma ställe. Automatiska betalflöden, aktiviteter, kommunikation och LOK-stöd för svenska idrottsföreningar.

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
78
Mostly ready3542View details
Discoverability
100
Strong1000
Content Readiness
68
Needs work2142View details
Bot Access Control
69
Needs work400
Agent Ease of Use
60
Needs work840View details
API
55
Needs work540View details
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
64
Needs work800
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
91
Strong2600
Security & Trust
91
Strong2600
Performance
95
Strong1400
Performance
95
Strong1400

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog media type".

58 Fail

Needs attention

API Catalog

Failed check
01

Issue

Content-Type "null" is not valid for an RFC 9727 API catalog.

Details

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

42/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog media type".

Validation steps

  1. Validate API catalog media type

    Content-Type "null" is not valid for an RFC 9727 API catalog.

    API catalog media type is not application/linkset+json
  2. Validate Linkset shape

    Target 0 for relation "type" is not an object.

    API catalog Linkset shape is invalid

    type: Target 0 for relation "type" is not an object.

    rel: Relation "rel" must be an array of target objects.

    type: Target 0 for relation "type" is not an object.

  3. Classify API catalog relations

    API catalog did not include API endpoint links or useful API discovery relations.

    API catalog lacks useful API relations
  4. Validate API catalog targets

    API catalog did not expose any href targets to validate.

    API catalog targets are unreachable or media types mismatch
Evidence log4 steps · 39 lines
Validate API catalog media type [fail]! Content-Type "null" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual=null expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "null" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Target 0 for relation "type" is not an object.INFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=true expected=trueFAILCompare top-level linkset item count actual=8 expected="> 0"FAILCompare extracted href target count actual=22 expected="> 0"FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="schema-type" issue="Relation \"schema-type\" must be an array of target objects."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="schema-type" issue="Relation \"schema-type\" must be an array of target objects."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="schema-type" issue="Relation \"schema-type\" must be an array of target objects."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="hreflang" issue="Target 0 for relation \"hreflang\" is not an object."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="hreflang" issue="Target 0 for relation \"hreflang\" is not an object."FAILLinkset href issue rel="type" issue="Target 0 for relation \"type\" is not an object."FAILLinkset href issue rel="rel" issue="Relation \"rel\" must be an array of target objects."FAILLinkset href issue rel="hreflang" issue="Target 0 for relation \"hreflang\" is not an object."FAILTarget 0 for relation "type" is not an object.Classify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=["type","rel","schema-type","hreflang"] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":["type","rel","schema-type","hreflang"]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

50 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing any valid freshness date in Last-Modified, Schema.org, Open Graph, Dublin Core, generic meta, or sitemap lastmod.

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

0/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. Validate Last-Modified header

    No valid Last-Modified HTTP header was found.

    Last-Modified freshness signal is missing or invalid
  2. Validate structured freshness dates

    No Schema.org freshness dates were found.

    Structured freshness dates are missing or invalid
  3. Validate metadata freshness dates

    No Open Graph, Dublin Core, or generic meta freshness date was found.

    Metadata freshness dates are missing or invalid
  4. 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
Evidence log4 steps · 16 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [fail]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaFAILCheck structured freshness date count actual=0 expected="> 0" invalidDateCount=0 formats={} alternateDates=[]FAILNo structured freshness dates foundValidate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=4WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=4

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

22 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

Details

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

    Schema.org author attribution is missing or incomplete
  2. Author identity quality

    No named author or publisher identity could be extracted.

    Author identity quality is incomplete
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=2 namedContributors=0 authors=[] publishers=[{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=2 authors=[] publishers=[{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false},{"role":"publisher","id":"https://www.lime-sportadmin.com/#organization","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted

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