CanAgentUse

CanAgentUse products

Agentic Browsing AuditCheck dialogs, menus, drawers, popovers, form errors, checkout steps, and other UI states that a standard Lighthouse scan may not capture.View product MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

UCP ValidatorUCP Playground

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

MCP Playground

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

A2A Playground

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

Agent Website Viewer
New Scan
https://www.sling.com/
SCANNED
Jul 28, 2026, 4:19 PM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
65/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability56%Agent Easeof Use56%Security& Trust84%GEO, AIO, AEO41%SEO92%Performance66%Accessibility97%
  • AI Discoverability 56 out of 100
  • Agent Ease of Use 56 out of 100
  • Security & Trust 84 out of 100
  • GEO, AIO and AEO 41 out of 100
  • SEO 92 out of 100
  • Performance 66 out of 100
  • Accessibility 97 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Sling TV: Stream Live TV Channels, Sports, & News Online favicon

Sling TV: Stream Live TV Channels, Sports, & News Online

Ditch cable & stream live TV for the best price with Sling. Watch live news, sports, movies, and entertainment + top channels like ESPN, TNT, TBS and more.

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
56
Needs work2610View details
Discoverability
67
Needs work800
Content Readiness
46
Priority fix1300
Bot Access Control
55
Needs work510View details
Agent Ease of Use
56
Needs work1841View details
API
37
Priority fix341View details
Auth
54
Needs work500
MCP
45
Priority fix200
Agent Commerce
58
Needs work700
Google Agentic Browsing
93
Strong100
GEO, AIO and AEO
41
Priority fix531View details
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
56
Needs work231View details
AEO Readiness
Not Applicable
Not Applicable100
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
84
Mostly ready1900
Security & Trust
84
Mostly ready1900
Performance
66
Needs work1000
Performance
66
Needs work1000

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

Agent Ease of UseAPIEstablished

API Catalog

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

63 Fail

Needs attention

API Catalog

Failed check
01

Issue

Content-Type "text/html;charset=utf-8" 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

37/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. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

    API catalog HEAD Link discovery is incomplete

  2. Validate API catalog media type

    Content-Type "text/html;charset=utf-8" is not valid for an RFC 9727 API catalog.

    API catalog media type is not application/linkset+json

  3. Validate Linkset shape

    Unexpected token '<', " <!DOCTYPE "... is not valid JSON

    API catalog Linkset shape is invalid

    Unexpected token '<', " <!DOCTYPE "... is not valid JSON

  4. Classify API catalog relations

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

    API catalog lacks useful API relations

  5. Validate API catalog targets

    API catalog did not expose any href targets to validate.

    API catalog targets are unreachable or media types mismatch
Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="text/html;charset=utf-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [fail]! Content-Type "text/html;charset=utf-8" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html;charset=utf-8" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html;charset=utf-8" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', "
<!DOCTYPE "... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"\n<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"\n<!DOCTYPE \"... is not valid JSON"FAILUnexpected token '<', "
<!DOCTYPE "... is not valid JSONClassify 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=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}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.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 0/100 and needs a fix.

8 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate, aboutOrContact, policyLinks, sourceLinks.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Structured data consistency

AIO: Structured data consistency scored 29/100 and needs a fix.

5 Fail

Needs attention

AIO: Structured data consistency

Failed check
01

Issue

20 structured-data value(s) were not found in visible page text.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Structured data consistency

Score

29/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Structured data consistency scored 29/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 45/100 and needs a fix.

4 Fail

Needs attention

AIO: Page experience proxy

Failed check
01

Issue

Only 97 words of visible rendered text were detected. 57 image(s) are missing width/height attributes. 56 possible modal/interstitial element(s) detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

45/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 45/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 76/100 and needs improvement.

2 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

Only 97 visible words were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Visible content clarity

Score

76/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Visible content clarity scored 76/100 and needs improvement.

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