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 16, 2026, 11:20 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
43/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability45%Agent Easeof Use50%Security& Trust45%GEO, AIO, AEO43%SEO67%Performance92%Accessibility0%
  • AI Discoverability 45 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 43 out of 100
  • SEO 67 out of 100
  • Performance 92 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

socaltech.com - startup, technology, and venture capital news in Los Angeles, San Diego, Orange County, Santa Barbara, and the rest of Sout... favicon

socaltech.com - startup, technology, and venture capital news in Los Angeles, San Diego, Orange County, Santa Barbara, and the rest of Sout...

No page metadata or readable excerpt was captured.

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
45
Priority fix1421View details
Discoverability
40
Priority fix400
Content Readiness
27
Priority fix611View details
Bot Access Control
63
Needs work410View details
Agent Ease of Use
50
Needs work110View details
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
43
Priority fix300
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable100
AEO Readiness
Not Applicable
Not Applicable100
SEO
67
Needs work500
SEO
67
Needs work500
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
92
Strong1600
Performance
92
Strong1600

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlInformational

Content Signal

Content Signal failed at "Validate declared usage preferences".

50 Fail

Needs attention

Content Signal

Failed check
01

Issue

Declared content usage preferences did not include any recognized preference terms.

Details

02

Why it matters

Content usage preference signals communicate intended downstream AI use separately from robots.txt crawl permission. They can express training and search preferences for compliant systems without replacing access-control rules.

Check name

Content Signal

Score

50/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Declare AI content usage preferences when the site intentionally publishes machine-readable usage policy.

Result

Content Signal failed at "Validate declared usage preferences".

Validation steps

  1. Validate declared usage preferences

    Declared content usage preferences did not include any recognized preference terms.

    Content usage declarations are missing, malformed, or partial
Evidence log1 step · 5 lines
Validate declared usage preferences [fail]! Declared content usage preferences did not include any recognized preference terms.INFOValidate declared usage preferencesINFOParsing declared preferences into terms and values recordCount=1INFORecognized declaration formats formats=["ietf-aipref"] sources=["robots.txt"]FAILCompare valid declarations to declared records actual=0 expected=">= 1 valid declaration with recognized preference terms" invalidRecords=[] warningRecords=[{"source":"robots.txt","directive":"Content-Usage","format":"ietf-aipref","line":72,"preferences":["ai=n"],"warnings":["Unknown preference term: ai."]}]WARNUnknown preference term: ai. record={"source":"robots.txt","directive":"Content-Usage","format":"ietf-aipref","line":72,"preferences":["ai=n"]}

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

45 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=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]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=[]FAILNo named contributor identity could be extracted

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 49 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

socaltech.com AI Agent Readiness Report: 43/100 (Level 2, Agent-Limited)