Usable, with real friction

69/ 100

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

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

Task

What does judge.me 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 judge.me over HTTPS in 73 ms and identified it from its title as “Judge.me | #1 Product Reviews App for Shopify”. 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.
2 / 2 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
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts
04
Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 pts
05
Content readable without JavaScriptCritical access
Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
+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://judge.me/
✓Responds in under 1.5s5/5
73 ms to first byte
✓robots.txt present2/2
# See http://www.robotstxt.org/robotstxt.html for documentation on how to use th…
✓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
"Judge.me | #1 Product Reviews App for Shopify" (45)
✓Meta description 50–160 characters5/5
"Judge.me helps you collect, showcase, and share product and store reviews with high-converting widge…" (149)
✓Canonical URL set3/3
https://judge.me/
✕Exactly one H10/4
2 × <h1>: "The #1 reviews app for Shopify"
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://framerusercontent.com/images/u8LnenhR3qeY7enlkhKgmaatK40.jpg

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
8 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
1602 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready9 of 19 passed · 19/46 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 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 JavaScript0/3
62,732 chars of visible text, 3.8% 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, 2 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
217/217 images have alt
—Form fields are labelledn/a
✓Descriptive link text2/2
0/368 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 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:39.588Z.

← Back to the board