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 9, 2026, 5:18 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
40/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability52%Agent Easeof Use44%Security& Trust45%GEO, AIO, AEO36%SEO100%Performance39%Accessibility9%
  • AI Discoverability 52 out of 100
  • Agent Ease of Use 44 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 36 out of 100
  • SEO 100 out of 100
  • Performance 39 out of 100
  • Accessibility 9 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Songtradr | Songtradr favicon

Songtradr | Songtradr

Songtradr crafts complete music solutions for digital platforms, businesses, agencies, artists, rightsholders, & fans.

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
52
Needs work2100
Discoverability
67
Needs work800
Content Readiness
47
Priority fix1200
Bot Access Control
45
Priority fix100
Agent Ease of Use
44
Priority fix242View details
Skill Discovery
44
Priority fix132View details
Google Agentic Browsing
33
Priority fix110View details
GEO, AIO and AEO
36
Priority fix432View details
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
30
Priority fix132View details
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
39
Priority fix1200
Performance
39
Priority fix1200

Prioritized recommendations

Issues ranked by score impact

7 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json failed at "Validate Wildcard schema shape".

75 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json response is not valid JSON.

Details

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

25/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json failed at "Validate Wildcard schema shape".

Validation steps

  1. Discover agents.json

    agents.json was found only at the fallback /agents.json path.

    agents.json is missing or only available at a fallback path
  2. Validate Wildcard schema shape

    agents.json response is not valid JSON.

    agents.json schema shape is invalid or incomplete
  3. Validate API actions

    Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.

    agents.json action definitions are invalid or missing
  4. Validate flows and links

    No executable flows were found.

    agents.json flows or links are invalid
  5. Review examples and LLM usability

    Examples or descriptions are too thin for reliable agent argument generation.

    agents.json examples or descriptions need improvement
Evidence log5 steps · 23 lines
Discover agents.json [warning]! agents.json was found only at the fallback /agents.json path.INFODiscover agents.jsonINFOTry agents.json discovery paths in priority order paths=["/.well-known/agents.json","/agents.json"]WARNagents.json candidate path did not return a usable contract path="/.well-known/agents.json" statusCode=504 contentType="text/html"PASSFound an agents.json candidate path="/agents.json" statusCode=200 contentType="text/html" bytes=7228WARNSelected fallback agents.json location path="/agents.json" requestedUrl="https://www.songtradr.com/agents.json"WARNagents.json was found only at the fallback /agents.json path.Validate Wildcard schema shape [fail]! agents.json response is not valid JSON.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=false expected=trueFAILagents.json response is not valid JSON.Validate API actions [fail]! Wildcard agents.json must include valid OpenAPI-derived action or operation definitions.INFOValidate API actionsFAILCompare API action count actual=0 expected="> 0"FAILCompare invalid action definitions actual=0 expected=0FAILWildcard agents.json must include valid OpenAPI-derived action or operation definitions.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNExamples or descriptions are too thin for reliable agent argument generation.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 0/100 and needs a fix.

7 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

Missing answer evidence or trust signals: author, publisher, freshnessDate, sources, sameAs, aboutOrContact, policyLinks.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Evidence and trust scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 31/100 and needs a fix.

5 Fail

Needs attention

AEO: Extractable visible copy

Failed check
01

Issue

Only 2 visible words were detected for answer extraction. Client-rendering root signals were found with limited visible text. Visible text has few answer-oriented terms or explanatory markers.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Extractable visible copy

Score

31/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Extractable visible copy scored 31/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 40/100 and needs a fix.

4 Fail

Needs attention

AEO: Question and answer structure

Failed check
01

Issue

No natural question headings were detected. No visible FAQ or Q&A pattern was detected. Heading structure issues were detected. No list or table answer format was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Question and answer structure scored 40/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 55/100 and needs improvement.

3 Warning

Needs attention

AEO: Answer-first passages

Warning
01

Issue

No h2/h3 answer sections were detected. No direct definition pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

55/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Answer-first passages scored 55/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 62/100 and needs improvement.

3 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Expected exactly one h1, found 0. No direct definition sentence was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

62/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

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

Result

AEO: Entity and definition clarity scored 62/100 and needs improvement.

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
40/100Level 2, Agent-LimitedCurrent report