Usable, with real friction

73/ 100

C
Grade: 35
Agent readiness
Board average 77 Scanned 14 hours ago

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

Task

What does triplewhale.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 triplewhale.com over HTTPS in 1041 ms and identified it from its title as “Triple Whale”. The copy is readable without JavaScript (27,381 chars of visible text, 17.6% of HTML). It found pricing. It looked for docs, an OpenAPI spec and an MCP server and found none.

Critical access needs attention

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.
1 / 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.
1 / 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
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts
03
Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 pts
04
Docs or API link from the homepageAgent-ready
Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
+3 pts
05
Semantic landmarks (main, single H1)Critical access
Wrap the content in <main> and keep one H1 so agents can find the primary content.
+3 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.triplewhale.com/
✓Responds in under 1.5s5/5
1041 ms to first byte
✓robots.txt present2/2
User-agent: * Disallow: /*/?gspk= Disallow: /?gspk=* Disallow: /*/*?*_page=* Dis…
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata6 of 7 passed · 20/24 pts›

✓Title tag 10–70 characters5/5
"Triple Whale" (12)
✓Meta description 50–160 characters5/5
"Say goodbye to scattered and inaccurate data. Triple Whale gives brands better data, one source of t…" (143)
✓Canonical URL set3/3
https://www.triplewhale.com
✕Exactly one H10/4
19 × <h1>: "The AI operating system built for modern ecommerce."
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width, initial-scale=1
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://cdn.prod.website-files.com/61bcbae3ae2e8ee49aa790b0/65c512f48e4a7760edda1262_f4fvFrame%202.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
4 social link(s)

Converts3 of 3 passed · 17/17 pts›

✓Clear call to action8/8
7 CTA(s), e.g. "Get started free"
✓Pricing page linked6/6
→ /pricing-old
✓HTML under 2 MB3/3
152 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready6 of 20 passed · 17/48 pts›

✕Structured data (JSON-LD)0/4
no JSON-LD
→ Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
✓Machine-readable pricing3/3
/pricing lists prices as text
✕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 homepage0/3
no docs / API link and no /docs
→ Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
✓Content readable without JavaScript3/3
27,381 chars of visible text, 17.6% of HTML
✕Semantic landmarks (main, single H1)0/3
no <main>, 19 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
123/123 images have alt
◐Form fields are labelled1/2
4/8 fields have a label, name or aria-label
→ Give every input a name and a label; an agent filling the form needs both.
◐Descriptive link text2/2
1/140 links say "click here" / "learn more"
→ Replace "learn more" and "click here" with what the link actually leads to.
✓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 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:37.945Z.

← Back to the board