Usable, with real friction

63/ 100

C
Grade: 48
Agent readiness
Board average 77 Scanned 17 hours ago

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

Task

What does gumroad.com 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 gumroad.com over HTTPS in 34 ms and identified it from its title as “Earn your first dollar online with Gumroad”. Little of the page survives without JavaScript, so a fetch-only agent sees mostly an empty shell. It found pricing and docs. It looked for 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.
0 / 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
Clear call to actionConverts
Put one primary CTA (Get started, Start free, Book a demo) above the fold.
+8 pts
02
OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts
03
Analytics installedMeasured
Install analytics (PostHog, Plausible, GA4) before spending on traffic.
+6 pts
04
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts
05
Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 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://gumroad.com/
✓Responds in under 1.5s5/5
34 ms to first byte
✓robots.txt present2/2
User-agent: * Disallow: /purchases/ Sitemap: https://public-files.gumroad.com/si…
✕sitemap.xml present0/2
no /sitemap.xml
→ Generate a sitemap and reference it from robots.txt.
✓Homepage is indexable5/5
HTTP 200

Metadata6 of 7 passed · 20/24 pts›

✓Title tag 10–70 characters5/5
"Earn your first dollar online with Gumroad" (42)
✓Meta description 50–160 characters5/5
"Start selling what you know, see what sticks, and get paid. Simple and effective." (81)
✓Canonical URL set3/3
https://gumroad.com/about
✕Exactly one H10/4
3 × <h1>: "Go from 0 to $1"
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
initial-scale = 1.0, width = device-width
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://assets.gumroad.com/images/pink-icon.png

Shareable2 of 3 passed · 11/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✕Twitter/X card type set0/3
no twitter:card
→ Add <meta name="twitter:card" content="summary_large_image">.
✓Links to X or LinkedIn3/3
1 social link(s)

Converts2 of 3 passed · 9/17 pts›

✕Clear call to action0/8
no sign-up / get-started / demo CTA found
→ Put one primary CTA (Get started, Start free, Book a demo) above the fold.
✓Pricing page linked6/6
→ /pricing
✓HTML under 2 MB3/3
126 KB of HTML

Measured0 of 1 passed · 0/6 pts›

✕Analytics installed0/6
no analytics tag detected
→ Install analytics (PostHog, Plausible, GA4) before spending on traffic.

Agent-ready11 of 20 passed · 23/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 present1/1
/llms.txt → 200, 1832+ 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 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
/docs responds
✕Content readable without JavaScript0/3
9,653 chars of visible text, 7.5% of HTML
→ Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
✕Semantic landmarks (main, single H1)0/3
<main> present, 3 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
129/129 images have alt
✓Form fields are labelled2/2
2/2 fields have a label, name or aria-label
✓Descriptive link text2/2
0/140 links say "click here" / "learn more"
✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
✓Trust pages (privacy, terms, security)2/2
found: /privacy, /terms
✕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
1832+ chars, has H1, has links
✕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

Score history

63 17 hours ago
63 yesterday
58 yesterday

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T08:20:05.811Z.

← Back to the board