Are you the author? Sign in to claim
Check if your website is visible to AI search (ChatGPT, Perplexity, Claude, Google AI). Zero-dependency CLI: npx github:
Is your website visible to AI search? A tiny, dependency-free CLI that checks whether ChatGPT, Perplexity, Claude, and Google AI can crawl and understand your site, and tells you exactly what to fix.
npx github:epistemedeus/ai-readiness yoursite.com
No install, no signup, no dependencies. Node 18+.
Prefer a browser? Run the same check (no install) at samedaydesk.com/tools/ai-readiness.
The checker tells you what to fix. This kit gives you everything to fix it, ready to paste:
→ Get the AI Search Readiness Kit ($9) · Prefer a done-for-you audit of your site? See samedaydesk.com.
We ran this checker against the homepages of 136 well-known companies across 7 industries and published the full results. Open data, free to use with attribution.
data/ai-search-readiness-2026.csvAverage score by industry (lower = harder for AI search to read):
| Industry | Avg score | n |
|---|---|---|
| Marketing agencies | 92 | 24 |
| SaaS | 88 | 24 |
| Dev tools | 86 | 17 |
| E-commerce | 85 | 19 |
| AI startups | 83 | 25 |
| Fintech | 74 | 16 |
| Healthtech | 63 | 11 |
Notable findings: Healthtech is the least AI-search-ready industry (avg 63). Klarna scored an F (38); GitHub, Chime, Ramp, Gusto, Ro, Hims and Zocdoc each scored a D. Even some AI companies struggle. Perplexity scored a C and LlamaIndex a D. Most gaps are the same and entirely fixable: JavaScript-only homepages, missing JSON-LD structured data, and no sitemap.
Per-industry write-ups: SaaS · e-commerce · marketing agencies · AI startups · healthtech.
AI search is becoming how people find things, and AI answers are pulled from a small set of pages that are crawlable and well-structured. If GPTBot is blocked in your robots.txt, or your pages have no structured data, you can be invisible in AI answers no matter how good your site looks to humans. This tool checks the technical fundamentals that decide whether you're even eligible to be cited.
| Check | Why it matters |
|---|---|
| AI crawler access | Whether GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Bingbot are allowed in robots.txt. Blocked = invisible. |
| Structured data (JSON-LD) | AI engines use JSON-LD (Organization, FAQPage, Article) to classify and quote your content. |
| Title & meta description | Present and well-sized, so engines have a clean summary to work with. |
| Open Graph tags | Richer machine-readable context and clean link previews. |
| XML sitemap | Helps engines discover your pages; submit it in Bing Webmaster Tools (ChatGPT Search reads the Bing index). |
| llms.txt | Flagged as cheap hygiene only. Honest note: it has no proven effect on AI citations yet, so don't let anyone sell it to you as a ranking boost. |
You get a 0-100 score, a letter grade, and a concrete fix for every failing check.
$ npx github:epistemedeus/ai-readiness example.com
AI Readiness https://example.com/
Score 72/100 Grade B
PASS AI crawler access No AI crawler blocked.
FAIL Structured data (JSON-LD) None found.
fix: Add Organization + FAQPage + Article JSON-LD.
PASS Title & meta description title 41 chars, description 132 chars
WARN Open Graph tags 2 og: tags
fix: Add og:title, og:description, og:image, og:url.
PASS XML sitemap found
WARN llms.txt none (minor: no proven citation effect)
JSON output for scripting: npx github:epistemedeus/ai-readiness yoursite.com --json
Add the checker to any Model Context Protocol client (Claude Desktop, Cursor, Cline, etc.) so you can ask your AI assistant "is my site visible to AI search?" and get a scored report inline. Dependency-free, runs over stdio.
{
"mcpServers": {
"ai-readiness": {
"command": "npx",
"args": ["-y", "github:epistemedeus/ai-readiness", "mcp"]
}
}
}
It exposes two tools:
check_ai_readiness(url): returns the score, grade, and a specific fix for each gap.generate_ai_readiness_fixes(url): generates starter Organization + FAQPage JSON-LD (pre-filled from the site) and an AI-crawler-friendly robots.txt.If your client supports remote MCP servers (e.g. ChatGPT connectors, Claude.ai custom connectors), point it at the hosted endpoint, nothing to install:
{ "mcpServers": { "ai-readiness": { "url": "https://samedaydesk.com/mcp" } } }
Fail-fast on AI-search regressions by checking a URL on every deploy:
- uses: epistemedeus/ai-readiness@v1
with:
url: https://yoursite.com
This CLI checks the technical basics. The questions it can't answer from your markup: do ChatGPT, Perplexity, and Google AI actually cite you for the queries your buyers type? How do you compare to named competitors? What's the highest-ROI fix first?
That's the AI-Search Visibility Audit from SameDayDesk: real citation testing across engines, a competitor benchmark, and a prioritized fix list as a PDF and web report, delivered same day. → samedaydesk.com
Like how this one is built: dependency-free, stdio and remote (Streamable HTTP), published to the MCP registry, one clean tool? We build MCP servers for your API or product the same way. (Curious how? Read the guide: How to build a dependency-free MCP server.)
Custom MCP Server: $349, delivered fast. You get a working server (stdio + optional hosted remote), wired to your API, with the registry/manifest setup done. → get one built (or buy directly).
Free, in-depth guides on getting your site read and cited by AI search:
MIT © SameDayDesk
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots
Google's universal MCP server supporting PostgreSQL, MySQL, MongoDB, Redis, and 10+ databases
Official GitHub integration for repos, issues, PRs, and CI/CD workflows