CanAgentUse

Saved report

https://www.oclc.org/en/home.html?redirect=true

SCANNED

Jun 28, 2026, 7:56 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://www.oclc.org/en/home.html?redirect=true

SCANNED

Jun 28, 2026, 7:56:56 AMJun 28, 2026, 7:56 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

49/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

OCLC: Worldwide, member-driven library organization

OCLC is a nonprofit global library organization that provides shared technology services, original research, and community programs so that libraries can better fuel learning, research, and innovation.

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.

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	54	Needs work	25	1	0	View details
Discoverability	63	Needs work	7	0	0
Content Readiness	56	Needs work	16	0	0
Bot Access Control	44	Priority fix	2	1	0	View details
Agent Ease of Use	52	Needs work	19	4	1	View details
API	52	Needs work	4	4	1	View details
Auth	54	Needs work	5	0	0
MCP	45	Priority fix	2	0	0
Skill Discovery	54	Needs work	1	0	0
Agent Commerce	58	Needs work	7	0	0
GEO, AIO and AEO	57	Needs work	5	0	0
GEO Readiness	Not Applicable	Not Applicable	1	0	0
AIO Readiness	Not Applicable	Not Applicable	2	0	0
AEO Readiness	Not Applicable	Not Applicable	2	0	0
SEO	100	Strong	10	0	0
SEO	100	Strong	10	0	0
Security & Trust	67	Needs work	14	0	0
Security & Trust	67	Needs work	14	0	0
Performance	35	Priority fix	10	0	0
Performance	35	Priority fix	10	0	0
Accessibility	0	Priority fix	0	1	0	View details
Accessibility	0	Priority fix	0	1	0	View details

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 "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check

Issue

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

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

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

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

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

Issue

Content-Type "text/html" is not valid for an RFC 9727 API catalog.

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

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

Check API catalog HEAD Link header
HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".
Validate API catalog media type
Content-Type "text/html" is not valid for an RFC 9727 API catalog.
Validate Linkset shape
Unexpected token '<', " <!DOCTYPE "... is not valid JSON
Unexpected token '<', " <!DOCTYPE "... is not valid JSON
Classify API catalog relations
API catalog did not include API endpoint links or useful API discovery relations.
Validate API catalog targets
API catalog did not expose any href targets to validate.

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"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" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html" 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\n\n<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"\n\n\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.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

References

https://www.deque.com/accessibility/core-documentation/

Evidence

{
  "error": "Execution context was destroyed, most likely because of a navigation."
}

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.

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

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.

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 date	Score	Readiness	Report
Jun 28, 2026	49/100	Level 2, Agent-Limited	Current report

Level 2, Agent-Limited

CAPTURED SCREENSHOT

What AI sees of your website

OCLC: Worldwide, member-driven library organization

Turn this report into a fix workflow

Issues ranked by score impact

AI bot rules in robots.txt

AI bot rules in robots.txt

Issue

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

API Catalog

API Catalog

Issue

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

Accessibility audit

Check name

Score

Status

Device

Category

Fix guidance

References

Sign in to see 46 other issues and the full report

Fix with MCP or CLI

Public scan score over time