Ready with a few material gaps

84/ 100

B
Grade: 61
Agent readiness
Board average 77 Scanned 14 hours ago

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

Task

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

12 fetches5 found7 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 screenshotone.com over HTTPS in 342 ms and identified it from its title as “The Screenshot API for developers”. The copy is readable without JavaScript (19,073 chars of visible text, 11.2% 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.
2 / 2 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
sitemap.xml presentCrawlable
Generate a sitemap and reference it from robots.txt.
+2 pts
03
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
04
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
05
llms.txt says what you are and links outAgent-ready
Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.
+2 pts

Audit the checks behind the score

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

Crawlable4 of 5 passed · 17/19 pts›

✓Served over HTTPS5/5
https://screenshotone.com/
✓Responds in under 1.5s5/5
342 ms to first byte
✓robots.txt present2/2
User-agent: * Allow: / Sitemap: https://screenshotone.com/sitemap-index.xml
✕sitemap.xml present0/2
no /sitemap.xml
→ Generate a sitemap and reference it from robots.txt.
✓Homepage is indexable5/5
HTTP 200

Metadata7 of 7 passed · 24/24 pts›

✓Title tag 10–70 characters5/5
"The Screenshot API for developers" (33)
✓Meta description 50–160 characters5/5
"ScreenshotOne is the best screenshot rendering platform for developers." (71)
✓Canonical URL set3/3
https://screenshotone.com/
✓Exactly one H14/4
1 × <h1>: "The screenshot API for developers"
✓Mobile viewport set3/3
width=device-width, initial-scale=1, shrink-to-fit=no
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://screenshotone.com/favicon-32x32.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
7 CTA(s), e.g. "Sign Up"
✓Pricing page linked6/6
→ /pricing/
✓HTML under 2 MB3/3
166 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: pirsch

Agent-ready10 of 19 passed · 28/46 pts›

✓Structured data (JSON-LD)4/4
@type: Organization, SoftwareApplication, WebPage, BreadcrumbList
✓Machine-readable pricing3/3
Offer / Product in JSON-LD
✕llms.txt present0/1
no /llms.txt
→ Publish /llms.txt: a short markdown summary of the product, pricing and docs links for AI agents.
✕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 request0/1
Accept: text/markdown → text/html; charset=utf-8
→ Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.
✕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
19,073 chars of visible text, 11.2% of HTML
✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
✓Images have alt text2/2
16/16 images have alt
—Form fields are labelledn/a
✓Descriptive link text2/2
0/103 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 complete2/2
Organization has name, url, logo, sameAs
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
✕llms.txt says what you are and links out0/2
no /llms.txt
→ Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.
✕Contact route discoverable0/2
no contact link or email on the homepage
→ Link /contact or a mailto: so an agent (or a human it hands off to) can reach you.

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:48:42.667Z.

← Back to the board