Ready with a few material gaps

82/ 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 uneed.best do and how do I use it? A fetch-only agent finds out.

12 fetches8 found4 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 uneed.best over HTTPS, though the response was slow and identified it from its title as “Daily Product Launches: Discover the Best New Tools | Uneed”. The copy is readable without JavaScript (152,465 chars of visible text, 17.0% of HTML). 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.
3 / 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.
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
Responds in under 1.5sCritical access
Cache the homepage at the edge; aim for under 500 ms.
+5 pts
03
Machine-readable pricingAgent-ready
Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.
+3 pts
04
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
05
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

Audit the checks behind the score

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

Crawlable4 of 5 passed · 14/19 pts›

✓Served over HTTPS5/5
https://www.uneed.best/
✕Responds in under 1.5s0/5
2695 ms to first byte
→ Cache the homepage at the edge; aim for under 500 ms.
✓robots.txt present2/2
# START nuxt-robots (indexable) User-agent: * Disallow: /*?*sortBy= Disallow: /*…
✓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
"Daily Product Launches: Discover the Best New Tools | Uneed" (59)
✓Meta description 50–160 characters5/5
"Uneed is a launch platform where makers launch their products every day. Discover, upvote and review…" (139)
✓Canonical URL set3/3
https://www.uneed.best/
✓Exactly one H14/4
1 × <h1>: "Best products launching today"
✓Mobile viewport set3/3
width=device-width,initial-scale=1,maximum-scale=5,viewport-fit=cover
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
/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
1 social link(s)

Converts3 of 3 passed · 17/17 pts›

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

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: Mixpanel

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

✓Structured data (JSON-LD)4/4
@type: Organization, WebSite
✕Machine-readable pricing0/3
/pricing exists but no price found in its HTML
→ Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.
✓llms.txt present1/1
/llms.txt → 200, 4000+ chars
✓llms-full.txt present1/1
/llms-full.txt → 200
✓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
152,465 chars of visible text, 17.0% of HTML
✕Semantic landmarks (main, single H1)0/3
no <main>, 1 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
41/41 images have alt
—Form fields are labelledn/a
✓Descriptive link text2/2
0/150 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, description
✓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:48:52.964Z.

← Back to the board