Is your site findable by Google AND by ChatGPT/Perplexity?
findable: SEO + AEO + GEO auditor for the AI search era (CLI, MCP, edge API). Scores summarise findable's own checks; they do not measure Google rankings or AI citations.
Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
findable: SEO + AEO + GEO auditor for the AI search era (CLI, MCP, edge API). Scores summarise findable's own checks; they do not measure Google rankings or AI citations.
Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API
Live demo: https://findable.page · Learn: https://findable.page/learn · The build story

AI answer engines now sit between your page and your reader. They tend to quote short, structured, attributed passages. A page can rank well on Google and still not be cited in a ChatGPT or Perplexity answer.
findable checks the signals answer engines are documented or commonly reported to use: whether a machine can lift a clean answer out of the page (AEO), and whether the page carries trust signals a generative engine may use to cite it (GEO), alongside classic SEO. It is written in Go with no account and no quota. Scoring a local HTML file is fully offline; URL, crawl and site checks make network requests, and the hosted API exists if you prefer not to run it yourself.
One overall score from 0 to 100, built from three families:
That is 160 page checks in the Go engine. The edge API runs a port with the same 160. Seven more site checks are opt-in (-site) and unscored: robots.txt present, the page allowed for *, GPTBot, ClaudeBot, PerplexityBot and Google-Extended, and /llms.txt present. Every failing check names what to fix.
go install github.com/findable-page/findable/cmd/findable@latest # Go 1.26+
Homebrew: planned for first release; use go install.
Then:
findable https://example.com
findable ./page.html # local file, no server needed
It prints the four scores and the failing checks, and saves a report file in -o (default .).
findable [-o dir] [-format csv|json|sarif] [-fail-under N] [-q] [-k keyphrase]
[-site] [-crawl] [-sitemap url] [-limit N] [-serve :port] [-mcp] [-allow-private] <url or file>
findable -q -format sarif -fail-under 70 https://example.com
findable -sitemap https://example.com/sitemap.xml -limit 50
findable -site -crawl -limit 10 https://example.com
Add to Claude Desktop, Cursor or Windsurf:
{ "mcpServers": { "findable": { "command": "findable", "args": ["-mcp"] } } }
No Go toolchain? Build the MCP server from source: (cd mcp && bun install && bun run build), then use { "command": "node", "args": ["/path/to/findable/mcp/dist/index.js"] }.
Tools: audit_page (URL or file), audit_html_content (raw HTML, no network), crawl_site, generate_csv_report. Prompt: seo_audit_prompt.
Hosted at https://findable.page (source: findable-page/findable-page), or run your own local server with findable -serve 127.0.0.1:8080.
curl -s -X POST https://findable.page/api/scan \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","keyphrase":"example","site":true}'
/api/scan only fetches public hosts: ports 80 and 443, 5 redirects, 10 seconds, 5 MB, rate limited. See SECURITY.md.
permissions:
security-events: write
steps:
- uses: findable-page/[email protected]
with:
url: https://example.com
fail-under: 70
args: -site
The action builds the CLI, uploads failing checks to code scanning as SARIF, then fails the job below fail-under.
git clone https://github.com/findable-page/findable && cd findable
(cd mcp && bun install)
make test
See CONTRIBUTING.md and CHANGELOG.md. testdata/ holds sample pages.
MIT
Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Findable läuft lokal über stdio.
Zuletzt geprüft: 2026-10-27. Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API