Mostly invisible to buyers and agents

55/ 100

D
Grade: 26
Agent readiness
Board average 73 Scanned 2 hours ago

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

Task

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

12 fetches3 found9 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 indiehackers.com over HTTPS in 639 ms and identified it from its title as “Indie Hackers: Work Together to Build Profitable Online Businesses”. 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.
0 / 2 passed
~
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
1 / 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
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
Pricing page linkedConverts
Link a pricing page from the homepage; buyers look for it first.
+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://www.indiehackers.com/
✓Responds in under 1.5s5/5
639 ms to first byte
✕robots.txt present0/2
no /robots.txt (or non-200)
→ Serve /robots.txt with at least a Sitemap: line.
✓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
"Indie Hackers: Work Together to Build Profitable Online Businesses" (66)
✓Meta description 50–160 characters5/5
"Connect with developers sharing the strategies and revenue numbers behind their companies and side p…" (108)
✓Canonical URL set3/3
https://www.indiehackers.com
✕Exactly one H10/4
no <h1>
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width, initial-scale=1
✓Language declared2/2
<html lang="en-US">
✓Favicon declared2/2
/images/favicons/favicon--16x16.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
2 social link(s)

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
309 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready5 of 19 passed · 12/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 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 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
no robots.txt (nothing 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
12,134 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
no <main>, 0 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
90/90 images have alt
◐Form fields are labelled1/2
1/2 fields have a label, name or aria-label
→ Give every input a name and a label; an agent filling the form needs both.
✓Descriptive link text2/2
0/383 links say "click here" / "learn more"
✕Agent-friendly 404s0/2
a nonexistent path returned HTTP 200
→ Return a real 404 for paths that do not exist; a 200 app shell makes every wrong guess look like a page.
—Trust pages (privacy, terms, security)n/a
✕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

AI visibility

Do AI assistants actually recommend Indie Hackers? Grounded LLM checks plus ecosystem presence, folded into the score.

✕Category share of voice0/6
not in the shortlist; assistants name: Here, Circle, This, It, Mighty, Networks
Publish comparison and use-case content so AI assistants have grounds to recommend indiehackers.com for its category.
✓Brand name discoverability3/3
Indie Hackers (indiehackers.com) is an online community and platform where independent entrepreneurs share their experiences, challenges, an
✕Wikipedia / Wikidata presence0/2
no matching article
A neutral Wikipedia or Wikidata entry anchors your brand for every assistant.
✓SDK package on npm1/1
npm: indiehackers-cli
✕Listed in the MCP registry0/1
not listed
Publish your MCP server to registry.modelcontextprotocol.io so agents can find it.

Indie Hackers shows limited visibility to AI assistants, failing to appear in category shortlists, have a Wikipedia presence, or be listed in the MCP registry. However, its brand name is discoverable, and an npm SDK package exists.

AI-analyzed 2 hours ago · cached 7 days · grounded via web search

The report is free. Visibility is the bid.

Indie Hackers sits at #27 of 33. $1 moves it above Typefully.

Bid $1 →

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-25T11:39:37.163Z.

← Back to the board