
CrazySEO
io.github.bolidee由 GitHub 帳號 bolidee 發布v0.1.2更新於 Oct 27, 2026
Audit whether ChatGPT, Gemini and Perplexity recommend a site. Readiness checks need no keys.
概覽
CrazySEO 稽核 ChatGPT、Gemini 與 Perplexity 是否會推薦某個網站,並檢查網站的 AI 搜尋就緒度。
- 可以做什麼
- 對網站執行 11 項 AI 就緒度稽核(HTTPS、robots.txt 中的 AI 爬蟲、schema.org、中繼資訊、圖片替代文字、網站地圖、失效內部連結)
- 規劃免金鑰的能見度稽核:擷取網站資訊並產生買家會問的問題
- 把助理自行蒐集的回答計分為能見度、競品排行與引用缺口
- 以盲測方式向已設定的引擎查詢多引擎能見度,並保留原始提問與回答
- 列出在落敗問題上被引用的來源
- 回報目前安裝可查詢哪些引擎
- 適用情境
- 適合 SEO、GEO/AEO 或行銷工作,想了解買家詢問推薦時 AI 助理是否會提到某個品牌,以及被引用的替代來源有哪些。就緒度稽核不需金鑰,也可作為部署前檢查網站能否被 AI 爬取的快速手段。
- 執行需求
- 以 stdio 在本機執行,通常透過 npx crazyseo mcp 啟動,需要 Node.js。就緒度檢查與免金鑰的規劃、計分工具不需要任何憑證。跨引擎能見度至少需要 OPENAI_API_KEY、GOOGLE_API_KEY 或 PERPLEXITY_API_KEY 其中之一,皆為選用,金鑰越多涵蓋的引擎越多。需要能連線到受稽核網站與模型服務商。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 CrazySEO,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
CrazySEO
Find out whether ChatGPT, Gemini and Perplexity recommend your site — and why they don't.
An open-source GEO / AEO auditor and MCP server. No account. No card. Your keys.
[crazyseo readiness audit of stripe.com, scoring 82 out of 100 across 11 technical checks]
Your customers have stopped googling. They ask an assistant "best CRM for small law firms?" and buy whatever it names. If it doesn't name you, you don't exist — and no analytics tool will tell you, because there is no click to measure.
This audits it directly: it asks the questions your buyers ask, records the answers word for word, and shows you which sources the models cite instead of you.
Why another one
Most tools in this space ask the model "what do you think of Acme?" — which tells you nothing, because naming the brand in the prompt guarantees it shows up in the answer.
This asks blind. Your brand never appears in the question, so the answer you get back is the answer a real buyer gets. That is the whole difference between a number you can act on and a number that flatters you.
Three more things a prompt wrapper can't do:
- Verbatim receipts. Every result carries the exact prompt and the model's raw answer, so you can paste it into ChatGPT yourself and reproduce it.
- Honest coverage. If an engine fails or rate-limits, the report says so. It never quietly drops an engine and calls the remaining average your score. If a site can't be reached, it refuses to score it rather than inventing a number.
- A real readiness audit. 11 checks against your actual site — not a prompt.
Quick start — no API keys needed
The readiness audit runs against any site with zero configuration and zero cost:
Nothing to install, no signup, no key. Or run it from source:
(That's real output — stripe.com, unmodified.)
11 scored checks, all first-party fetches: HTTPS · AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended…) unblocked in robots.txt · schema.org markup · title + meta · readable without JavaScript · canonical · Open Graph · single-H1 structure · image alt-text coverage · sitemap referenced · broken internal links (sampled).
Plus llms.txt, shown but deliberately unscored: Google's own AI-optimization guidance says it has no effect in Google Search, so it can't fairly cost anyone points — but some agents do read it, so it's still worth seeing.
Exits non-zero when checks fail, so you can gate a deploy on it:
Machine-readable output for pipelines:
The visibility audit — bring your own keys
To measure what the engines actually say, add whichever keys you have. Any one is enough; more engines means more coverage.
It reads your site, infers what you sell, generates the questions your buyers would actually ask, and asks all of them — blind — across every engine you configured.
(Real output, trimmed for length. Note the last line: when an engine fails, the report says so instead of quietly averaging the rest and calling it your score.)
Runs on your own keys — a full audit is typically a few cents.
Use it from your agent
It ships as an MCP server, so Claude, ChatGPT or any MCP-capable agent can run it directly:
It's also packaged as a Claude Code plugin, which wires up the MCP server and the skill below in one step:
Then just ask:
"Is my site visible in AI search? What's cited instead of me?"
You don't need an API key to get the interesting part. audit_plan and
audit_score let the assistant you're already talking to be the engine: it
fetches your site, writes the buyer questions, answers them with its own web
search, and hands the results back for scoring. Ask "is my site visible in AI
search?" and you get a real citation gap with no signup, no key, no billing.
The tool still does the arithmetic, and still refuses a question that names your
brand — that guard is what makes the number worth having. It measures visibility
in that assistant, which the report says plainly. For the cross-engine
picture, use audit with your own keys.
There's also a SKILL.md so agents know how to interpret the
numbers — that readiness isn't visibility, that 0% is a normal starting point,
and that partial engine coverage must be reported as partial.
Use it as a library
How this stays free
Everything here is free forever, self-hosted, AGPL — full capability, no feature locks, no telemetry, no account, no upsell in the output.
There is no paid tier today, and this README won't pretend otherwise. If one ever appears it will be for the single thing self-hosting genuinely can't give you — scheduled re-runs, stored history and alerts, the infrastructure to watch a number move over months without running anything yourself. The auditing itself stays here, complete, under AGPL.
Which is also the answer to "what stops this going closed later": the licence. Anyone offering it as a hosted service has to open their version too, including whoever wrote it.
Contributing
Issues and PRs welcome. The checks are deliberately conservative: every one has to be something an assistant or its crawler actually depends on, and verifiable by hand. If a check can't be justified that way, it doesn't belong here.
CONTRIBUTING.md covers the setup, the bar a new check has to clear, and what an engine adapter needs to get right.
License
AGPL-3.0. Use it, fork it, run it commercially, embed it in your own tooling. If you offer it to others as a hosted service, that service must be open too.
來源:README.md,提交 5e31309
工具
0版本歷史
1- v0.1.2最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分

