CrazySEO

io.github.d08m由 GitHub 帳號 d08m 發布v0.1.3更新於 Oct 24, 2026

Audit whether ChatGPT, Gemini and Perplexity recommend a site. Readiness checks need no keys.

概覽

AI 產生的概覽

稽核 ChatGPT、Gemini 與 Perplexity 是否推薦某個網站,並對網站本身做免金鑰的 AI 就緒度檢查。

可以做什麼
  • 對網站執行 11 項 AI 就緒度稽核(HTTPS、爬蟲規則、結構化資料、標題與描述、圖片替代文字、網站地圖、失效內部連結)
  • 產生網站事實與不提及品牌的買家問題,並為助理自行蒐集的答案評分
  • 以已設定的引擎進行盲測式多引擎可見度查詢,保留逐字回答
  • 列出在落敗問題上被引用的第三方來源
  • 顯示目前安裝可查詢哪些引擎
適用情境
想知道 AI 助理在買家提出品類問題時是否會提到某個品牌,或在部署前後快速做一次技術就緒度檢查時適用。免金鑰模式可先讓目前的助理充當引擎做初步評估。
執行需求
透過 npx 以 stdio 在本機執行(需要 Node.js)。就緒度檢查與計畫/評分工具不需金鑰。多引擎可見度與引用落差工具需要 GOOGLE_API_KEY、OPENAI_API_KEY 或 PERPLEXITY_API_KEY 其中至少一個;需要連線到受稽核網站與模型 API 的網路。
安裝前請注意
選用的 API 金鑰從環境變數讀取,費用計入你自己的服務商帳戶,完整稽核據稱約數美分。就緒度檢查會直接抓取目標網站。結果完整度取決於設定的引擎數量,免金鑰模式只衡量目前助理內的可見度。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 CrazySEO,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

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.

[CI] [License: AGPL v3] [MCP]


[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:

bash
npx crazyseo readiness yourbrand.com

Nothing to install, no signup, no key. Or run it from source:

bash
git clone https://github.com/d08m/crazyseo && cd crazyseonpm install && npm run buildnode dist/cli.js readiness yourbrand.com
AI-READINESS  stripe.com                                    82/100
  ✓ Served over HTTPS  ✓ AI crawlers allowed  ✓ Structured data (schema.org)  ✓ llms.txt published (bonus)  ✓ Title + meta description  ✓ Readable without JavaScript  ✓ Canonical URL set  ✓ Social preview tags (Open Graph)  ✗ Single, clear H1      2 H1 tags — ambiguous which is the main topic  ✗ Images have alt text      27 of 31 images missing alt text  ✓ Sitemap referenced  ✓ No broken internal links
  → 2 issues to fix

(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:

yaml
- run: npx crazyseo readiness ${{ env.SITE }}

Machine-readable output for pipelines:

bash
npx crazyseo readiness yourbrand.com --json > report.json

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.

bash
export OPENAI_API_KEY=...      # optionalexport GOOGLE_API_KEY=...      # optionalexport PERPLEXITY_API_KEY=...  # optional
npx crazyseo audit yourbrand.com

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.

VISIBILITY  lymexa.com                       0 of 8 answers  ·  0%  Lymexa — premium pickleball paddles and recovery gear brand, USA
  "What are the best premium pickleball paddles for advanced players?"    Gemini      ✗ not named  JOOLA, CRBN, Selkirk, Six Zero    Perplexity  ✗ not named  JOOLA, Selkirk, CRBN, Gearbox
  "Which high-performance pickleball paddle brands are manufactured in the USA?"    Gemini      ✗ not named  Engage, Paddletek, Selkirk, Thompson Pickleball    Perplexity  ✗ not named  Engage, Paddletek, Selkirk, GAMMA
  RECOMMENDED INSTEAD    Selkirk                      4× named    Therabody                    4× named    Hyperice                     4× named
  CITATION GAP — cited on the questions you lost    reddit.com                   7×  Community discussion AI trusts for real opinions    youtube.com                  6×  Video content AI pulls into answers    pickleheads.com              4×  Third-party source AI cites instead of you
  ! ChatGPT did not respond — this score covers the rest only.

(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:

bash
claude mcp add --transport stdio crazyseo -- npx -y crazyseo mcp

It's also packaged as a Claude Code plugin, which wires up the MCP server and the skill below in one step:

bash
/plugin marketplace add d08m/crazyseo/plugin install crazyseo@crazyseo

Then just ask:

"Is my site visible in AI search? What's cited instead of me?"

toolwhat it doeskeys
readiness_check11-point AI-readiness auditnone
audit_plansite facts + buyer questions to ask, for a keyless auditnone
audit_scorescores what the agent found: visibility, leaderboard, citation gapnone
audit_visibilityblind multi-engine visibility + verbatim answersBYO
citation_gapsources cited on the questions you loseBYO
engine_statuswhich engines this install can querynone

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

ts
import { checkReadiness } from 'crazyseo';
const report = await checkReadiness('example.com');console.log(report.score, report.checks);

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.


Built because "am I in the answer?" deserves a real measurement, not a vibe.

來源:README.md,提交 5e31309

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.3最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分