Mostly invisible to buyers and agents

55/ 100

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

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

Task

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

12 fetches4 found1 partial7 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 lennysnewsletter.com over HTTPS in 124 ms and identified it from its title as “Lenny's Newsletter | Substack”. The copy is readable without JavaScript (66,475 chars of visible text, 60.9% of HTML). It looked for pricing, docs, 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.
3 / 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
Meta description 50–160 charactersMetadata
Add a meta description between 50 and 160 characters.
+5 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.

Crawlable5 of 5 passed · 19/19 pts›

✓Served over HTTPS5/5
https://www.lennysnewsletter.com/
✓Responds in under 1.5s5/5
124 ms to first byte
✓robots.txt present2/2
User-agent: BLEXBot Disallow: / User-agent: Twitterbot Disallow: User-agent: * D…
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata6 of 7 passed · 19/24 pts›

✓Title tag 10–70 characters5/5
"Lenny's Newsletter | Substack" (29)
✕Meta description 50–160 characters0/5
"Deeply researched product, growth, and career advice for product leaders, founders, and ambitious bu…" (194)
→ Add a meta description between 50 and 160 characters.
✓Canonical URL set3/3
https://www.lennysnewsletter.com/
✓Exactly one H14/4
1 × <h1>: "Lenny's Newsletter"
✓Mobile viewport set3/3
width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0, viewport-fit=cover
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
https://substackcdn.com/image/fetch/$s_!6RbS!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F5d6af901-7717-4d79-b49e-8bc28427148c%2Ffavicon.ico

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

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready7 of 20 passed · 16/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 homepage0/3
no docs / API link and no /docs
→ Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
✓Content readable without JavaScript3/3
66,475 chars of visible text, 60.9% 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
1/1 images have alt
✓Form fields are labelled2/2
1/1 fields have a label, name or aria-label
✓Descriptive link text2/2
0/3 links say "click here" / "learn more"
✓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 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 Lenny's Newsletter? Grounded LLM checks plus ecosystem presence, folded into the score.

✕Category share of voice0/6
not in the shortlist; assistants name: For, Jasper
Publish comparison and use-case content so AI assistants have grounds to recommend lennysnewsletter.com for its category.
✓Brand name discoverability3/3
Lenny's Newsletter is a popular Substack publication and podcast by Lenny Rachitsky that provides deeply researched advice on product, growt
✕Wikipedia / Wikidata presence0/2
no matching article
A neutral Wikipedia or Wikidata entry anchors your brand for every assistant.
✕SDK package on npm0/1
no package found
Ship an npm/PyPI SDK so agents can integrate without scraping.
✕Listed in the MCP registry0/1
not listed
Publish your MCP server to registry.modelcontextprotocol.io so agents can find it.

Lenny's Newsletter demonstrates strong brand name discoverability as a popular Substack and podcast. However, it fails to appear in AI assistant shortlists and lacks presence on Wikipedia, Wikidata, npm, or the MCP registry.

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

The report is free. Visibility is the bid.

Lenny's Newsletter sits at #28 of 33. $1 moves it above Indie Hackers.

Bid $1 →

Fixed something? Scan again.

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

← Back to the board