Reach & AI Readiness
20% of overallWhen developers (and their AI assistants) go looking, do they find you — and what they need?
What it measures
Three groups of signals: (1) AI readiness — is there an llms.txt, AI-friendly pages, and a hosted MCP server? (2) External mentions — Reddit, Hacker News, dependents on the package registries, Stack Overflow tag activity. (3) Dev-focused content — what fraction of the blog and YouTube channel is for developers vs. marketing.
Why it matters
AI assistants are now a primary discovery surface. An llms.txt + hosted MCP means ChatGPT, Claude, and Cursor can answer real questions about your product instead of hallucinating from old blog posts. External mentions are the word-of-mouth proxy that doesn't show up in your own analytics.
Sub-metrics
| Metric | What we read | Weight | Source |
|---|---|---|---|
| llms.txt | Presence, sections, links, llms-full.txt, size | 35% of AI-readiness | Live HTTP probe of common paths |
| AI-friendly pages | Markdown/JSON variants of docs pages | 20% of AI-readiness | Docs crawl |
| Hosted MCP server | POST initialize to mcp.<domain>, /mcp, /sse, etc. | 45% of AI-readiness | JSON-RPC probe (accepts auth-protected 401) |
| External mentions | Reddit + Hacker News search hits | 45% of external | Reddit + HN search API |
| Package dependents | Count of public packages that depend on yours | 40% of external | npm / PyPI / etc. |
| Stack Overflow | Tag question volume + recency | 15% of external | Stack Exchange API |
| Dev content ratio | % of blog posts and YouTube videos classified as developer content | 15% of pillar | Firecrawl + LLM classifier |
How it's weighted
External mentions carry the most weight, with AI readiness close behind — a hosted MCP server is the single strongest signal inside that bucket. Dev-focused content nudges the score up when the blog and YouTube channel are clearly for developers rather than buyers.
Best practices
- Publish /llms.txt at the root of your docs site. Add /llms-full.txt with the long form.
- Host an MCP server at mcp.yourdomain.com — even a docs-search MCP is a strong signal.
- Open-source one MCP server in your GitHub org so the community can ship their own variants.
- Keep the blog dev-heavy. Marketing posts dilute the signal — split them onto a separate /company feed if you must.
- Claim and watch your Stack Overflow tag. Answer the first few questions yourself to set a quality bar.
- Make sure your package's README links to docs, repo, and Discord — that's what dependents will see.