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, 3:16 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
AIDiscoverability31%Agent Easeof Use49%Security& Trust68%GEO, AIO, AEO60%SEO82%Performance79%Accessibility0%
  • AI Discoverability 31 out of 100
  • Agent Ease of Use 49 out of 100
  • Security & Trust 68 out of 100
  • GEO, AIO and AEO 60 out of 100
  • SEO 82 out of 100
  • Performance 79 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Low Cost Online Courses for College Credit | Sophia Learning favicon

Low Cost Online Courses for College Credit | Sophia Learning

Save time and money by earning credits toward a college degree with Sophia’s on-demand, self-paced courses.

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
31
Priority fix1420View details
Discoverability
30
Priority fix400
Content Readiness
22
Priority fix800
Bot Access Control
39
Priority fix220View details
Agent Ease of Use
49
Priority fix2024View details
API
52
Needs work400
Auth
54
Needs work500
MCP
45
Priority fix200
Skill Discovery
50
Needs work114View details
Agent Commerce
58
Needs work700
Google Agentic Browsing
33
Priority fix110View details
GEO, AIO and AEO
60
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable300
SEO
82
Mostly ready600
SEO
82
Mostly ready600
Security & Trust
68
Needs work1400
Security & Trust
68
Needs work1400
Performance
79
Mostly ready1200
Performance
79
Mostly ready1200

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Fetch robots.txt".

100 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No robots.txt content was available to inspect for AI bot rules.

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

0/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 "Fetch robots.txt".

Validation steps

  1. Fetch robots.txt

    No robots.txt content was available to inspect for AI bot rules.

    robots.txt is missing for AI crawler policy inspection
  2. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

52 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not served with a JSON-compatible Content-Type.

Details

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

48/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index failed at "Validate discovery index schema".

Validation steps

  1. Discover Agent Skills index

    Agent Skills index was found only at the legacy /.well-known/skills/index.json path.

    Agent Skills index is only available at the legacy path
  2. Validate discovery index schema

    Agent Skills index was not served with a JSON-compatible Content-Type.

    Agent Skills discovery index schema is invalid

    Response is not valid JSON.

  3. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  4. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  5. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log5 steps · 19 lines
Discover Agent Skills index [warning]! Agent Skills index was found only at the legacy /.well-known/skills/index.json path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://www.sophia.org/.well-known/agent-skills/index.json" statusCode=404PASSFetched Agent Skills index candidate path="/.well-known/skills/index.json" url="https://www.sophia.org/.well-known/skills/index.json" statusCode=200 contentType="text/html; charset=utf-8" bytes=23017 selected="selected"WARNAgent Skills index was found only at the legacy /.well-known/skills/index.json path.Validate discovery index schema [fail]! Agent Skills index was not served with a JSON-compatible Content-Type.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=false contentTypeCompatible=falseFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index was not served with a JSON-compatible Content-Type.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

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