BetaList
← board · betalist.com · #75 of 80
Mostly invisible to buyers and agents
- D
- 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 betalist.com do and how do I use it? A fetch-only agent finds out.
12 fetches5 found7 missing
- /robots.txt⋯/sitemap.xml
- /llms.txt⋯/llms-full.txt
- /pricing
- /docs
- /openapi.json
- mcp.json⋯MCP initialize
- /privacy · /terms
every path the scanner fetched · replayed deterministically, no LLM
Evaluator notes
A fetch-only agent reached betalist.com over HTTPS in 695 ms and identified it from its title as “Discover and get early access to tomorrow's startups | BetaList”. 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.
- ✓4 / 4 passedAgents can reach the site
Crawler access and bot defenses.
- ~0 / 2 passedCore content is available
Useful content remains accessible without a fragile browser-only path.
- ✓2 / 2 passedNavigation fails safely
Redirects and missing pages give agents a recoverable path.
- ~2 / 3 passedControls are understandable
Forms and interactive controls expose usable names and structure.
Fix these gaps first
Critical access gaps come first, then the biggest remaining points.
- 01Clear call to actionConverts
Put one primary CTA (Get started, Start free, Book a demo) above the fold.
+8 pts - 02OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts - 03Pricing page linkedConverts
Link a pricing page from the homepage; buyers look for it first.
+6 pts - 04Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 pts - 05Links to X or LinkedInShareable
Link your X and LinkedIn so visitors can follow and verify you.
+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://betalist.com/
- ✓Responds in under 1.5s5/5
695 ms to first byte
- ✓robots.txt present2/2
# See https://www.robotstxt.org/robotstxt.html for documentation on how to use t…
- ✕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 · 22/24 pts›
- ✓Title tag 10–70 characters5/5
"Discover and get early access to tomorrow's startups | BetaList" (63)
- ✓Meta description 50–160 characters5/5
"BetaList provides an overview of upcoming internet startups. Discover and get early access to the fu…" (105)
- ✓Canonical URL set3/3
https://betalist.com/
- ✓Exactly one H14/4
1 × <h1>: "Discover tomorrow's startups, today."
- ✓Mobile viewport set3/3
width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no
- ✕Language declared0/2
no lang attribute
→ Set lang on the <html> element.
- ✓Favicon declared2/2
/assets/favicon-fb6ee938.png
Shareable2 of 3 passed · 11/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 LinkedIn0/3
no X / LinkedIn links found
→ Link your X and LinkedIn so visitors can follow and verify you.
Converts1 of 3 passed · 3/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 linked0/6
no /pricing link
→ Link a pricing page from the homepage; buyers look for it first.
- ✓HTML under 2 MB3/3
220 KB of HTML
Measured1 of 1 passed · 6/6 pts›
- ✓Analytics installed6/6
detected: googletagmanager.com
Agent-ready8 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 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 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 homepage3/3
homepage links to docs / API
- ✕Content readable without JavaScript0/3
6,224 chars of visible text, 2.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
no <main>, 1 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
- ✕Images have alt text0/2
0/55 images have alt
→ Add alt text to images; it is the only thing a text agent can read from them.
- ✓Form fields are labelled2/2
57/57 fields have a label, name or aria-label
- ✓Descriptive link text2/2
0/93 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 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:55.358Z.