Ready with a few material gaps

89/ 100

B
Grade: 71
Agent readiness
Board average 77 Scanned 13 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does opus.pro do and how do I use it? A fetch-only agent finds out.

12 fetches7 found5 missing

⋯home

/robots.txt⋯/sitemap.xml
/llms.txt⋯/llms-full.txt
/pricing
/docs
/openapi.json
mcp.json⋯MCP initialize
/privacy · /terms

⋯404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached opus.pro over HTTPS in 106 ms and identified it from its title as “OpusClip: #1 AI video clipping and editing tool”. The copy is readable without JavaScript (86,838 chars of visible text, 25.1% of HTML). It found pricing and docs. It looked for an OpenAPI spec and an MCP server and found none.

Critical access is clean

Whether an ordinary agent can enter, read, and operate the public site.

✓
Agents can reach the site
Crawler access and bot defenses.
4 / 4 passed
✓
Core content is available
Useful content remains accessible without a fragile browser-only path.
2 / 2 passed
✓
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
2 / 2 passed
✓
Controls are understandable
Forms and interactive controls expose usable names and structure.
3 / 3 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

01
OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts
02
Agent manifest (MCP, A2A or ai-plugin)Agent-ready
Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
+2 pts
03
Trust pages (privacy, terms, security)Agent-ready
Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
+2 pts
04
Organization schema completeAgent-ready
Give the Organization JSON-LD a name, url, logo, description and sameAs links.
+2 pts
05
llms-full.txt presentAgent-ready
Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
+1 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable5 of 5 passed · 19/19 pts›

✓Served over HTTPS5/5
https://www.opus.pro/
✓Responds in under 1.5s5/5
106 ms to first byte
✓robots.txt present2/2
User-agent: * Allow: / Disallow: /*?* Sitemap: https://www.opus.pro/sitemap.xml
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata7 of 7 passed · 24/24 pts›

✓Title tag 10–70 characters5/5
"OpusClip: #1 AI video clipping and editing tool" (47)
✓Meta description 50–160 characters5/5
"OpusClip turns long videos into high-quality viral clips, and publishes them to all social platforms…" (160)
✓Canonical URL set3/3
https://www.opus.pro
✓Exactly one H14/4
1 × <h1>: "1 long video, 10 viral clips. Create 10x faster."
✓Mobile viewport set3/3
width=device-width, initial-scale=1
✓Language declared2/2
<html lang="en-US">
✓Favicon declared2/2
https://cdn.prod.website-files.com/6388604483b03a9ecb34d695/64351a9e4e9223f5e0f46d64_ico-final.png

Shareable3 of 3 passed · 14/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✓Twitter/X card type set3/3
twitter:card = summary_large_image
✓Links to X or LinkedIn3/3
2 social link(s)

Converts3 of 3 passed · 17/17 pts›

✓Clear call to action8/8
1 CTA(s), e.g. "Sign up - It’s FREE"
✓Pricing page linked6/6
→ /pricing
✓HTML under 2 MB3/3
338 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: gtag(

Agent-ready15 of 20 passed · 34/48 pts›

✓Structured data (JSON-LD)4/4
@type: FAQPage
✓Machine-readable pricing3/3
/pricing lists prices as text
✓llms.txt present1/1
/llms.txt → 200, 4000+ chars
✕llms-full.txt present0/1
no /llms-full.txt
→ Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
✓No noai / TDM reservation2/2
no opt-out signals
✓Serves markdown on request1/1
Accept: text/markdown → text/markdown; charset=utf-8
✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
✓Docs or API link from the homepage3/3
homepage links to docs / API
✓Content readable without JavaScript3/3
86,838 chars of visible text, 25.1% of HTML
✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
✓Images have alt text2/2
121/121 images have alt
✓Form fields are labelled2/2
2/2 fields have a label, name or aria-label
✓Descriptive link text2/2
0/138 links say "click here" / "learn more"
✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
✕Trust pages (privacy, terms, security)0/2
none of /privacy, /terms, /security respond
→ Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
✕Organization schema complete0/2
no Organization in JSON-LD
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
✓llms.txt says what you are and links out2/2
4000+ chars, has H1, has links
✓Contact route discoverable2/2
mailto:, /contact or /support link found

APIn/a›

—Spec parses and declares a versionn/a
—Operations have summaries and operationIdsn/a
—Error responses documentedn/a
—Auth scheme declaredn/a
—Versioned paths or serversn/a
—Spec within a model context budgetn/a

MCPn/a›

—Server answers initializen/a
—Tools listedn/a
—Tools carry descriptionsn/a
—Tool parameters have schemasn/a

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T13:49:15.257Z.

← Back to the board