Ready with a few material gaps

76/ 100

B
Grade: 63
Agent readiness
Board average 77 Scanned 17 hours ago

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

Task

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

12 fetches5 found1 partial6 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 producthunt.com over HTTPS in 339 ms and identified it from its title as “Product Hunt – The best new products in tech.”. Little of the page survives without JavaScript, so a fetch-only agent sees mostly an empty shell. It found docs. It looked for pricing, 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.
2 / 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
Pricing page linkedConverts
Link a pricing page from the homepage; buyers look for it first.
+6 pts
03
Meta description 50–160 charactersMetadata
Add a meta description between 50 and 160 characters.
+5 pts
04
Machine-readable pricingAgent-ready
Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.
+3 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.

Crawlable4 of 5 passed · 17/19 pts›

✓Served over HTTPS5/5
https://www.producthunt.com/
✓Responds in under 1.5s5/5
339 ms to first byte
✓robots.txt present2/2
User-agent: * Allow: /sitemaps_v3/* Disallow: /auth/* Disallow: /search* Disallo…
✕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 · 19/24 pts›

✓Title tag 10–70 characters5/5
"Product Hunt – The best new products in tech." (45)
✕Meta description 50–160 characters0/5
"Product Hunt is a curation of the best new products, every day. Discover the latest mobile apps, web…" (161)
→ Add a meta description between 50 and 160 characters.
✓Canonical URL set3/3
https://www.producthunt.com
✓Exactly one H14/4
1 × <h1>: "Top Products Launching Today"
✓Mobile viewport set3/3
width=device-width, initial-scale=1, minimum-scale=1
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://ph-static.imgix.net/ph-favicon-brand-500.ico

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)

Converts2 of 3 passed · 11/17 pts›

✓Clear call to action8/8
2 CTA(s), e.g. "Sign Up"
✕Pricing page linked0/6
no /pricing link
→ Link a pricing page from the homepage; buyers look for it first.
✓HTML under 2 MB3/3
1104 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready11 of 20 passed · 30/48 pts›

✓Structured data (JSON-LD)4/4
@type: Organization, WebPage, WebSite
✕Machine-readable pricing0/3
no /pricing page and no Offer JSON-LD
→ 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 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 JavaScript0/3
61,254 chars of visible text, 5.4% of HTML
→ Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
✓Images have alt text2/2
85/85 images have alt
✓Form fields are labelled2/2
1/1 fields have a label, name or aria-label
◐Descriptive link text2/2
1/256 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)1/2
found: /privacy
→ 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 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

Score history

76 17 hours ago
74 yesterday
76 yesterday
81 yesterday

Fixed something? Scan again.

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

← Back to the board