geo-score

感谢 CCSub 赞助本项目！CCSub 是一个 AI API 中转平台：一把 API 密钥即可使用 Claude、GPT、Gemini 和 DeepSeek 模型，兼容 Claude Code、Codex、Cursor 及其他编码工具。通过此链接注册。

赞助商尚未接受 geo-score 的引用测量测试（第 2 和第 3 级）。这些测量需要使用各引擎自身支持搜索的 API，而中转平台可能无法原样传递网页搜索结果和引用。

  AIV READINESS  https://stripe.com
──────────────────────────────────────────────────────────────────────────
  72 / 100   Solid
  11 points to Leading

  Reachable 13/15
   ◐ Crawlers allowed in robots.txt   ███████████░░░░░░░  3/5
   ✓ Reachable to retrieval agents    ██████████████████  5/5
   ✓ Main content server-rendered     ██████████████████  5/5
  Understandable 17/22
   ◐ Sitemap discoverable and fresh   █████████░░░░░░░░░  2/4
   ✓ llms.txt present and structured  ██████████████████  5/5
   ✓ Organization + WebSite schema    ██████████████████  6/6
   ✗ BreadcrumbList on nested pages   ░░░░░░░░░░░░░░░░░░  0/3
   ✓ Page-type schema (Product, FAQ…) ██████████████████  4/4
  Content Citability 21/35
   ✓ Self-contained answer passages   ██████████████████  9/9
   ◐ Headings match how people ask    ████████░░░░░░░░░░  3/7
   ◐ Freshness signal present         █████████░░░░░░░░░  3/6
   ◐ Statistics carry a source        ████████░░░░░░░░░░  3/7
   ◐ Named, verifiable authorship     █████████░░░░░░░░░  3/6
  Brand Credibility 9/10
   ⊘ Third-party listings             ··················   —
   ⊘ Independent mentions             ··················   —
   ✓ Knowledge-graph entity           ██████████████████  4/4
   ✓ sameAs links resolve             ██████████████████  3/3
   ◐ Video and multimodal presence    ████████████░░░░░░  2/3
  Answer Fit 2/4
   ◐ Content shaped for extraction    █████████░░░░░░░░░  2/4
   ⊘ Covers the questions people ask  ··················   —
   ⊘ Chinese engine readiness         ··················   —
  ✓ full · ◐ partial · ✗ zero · ⊘ not measured (left the denominator)

  Biggest gaps
   +3 next tier (+3 to full)  Freshness signal present          needs: most pages do, and dateModified agrees with the visible date
   +3 next tier (+3 to full)  Named, verifiable authorship      needs: and the name links to a verifiable identity page
   +2 next tier (+2 to full)  Crawlers allowed in robots.txt    needs: mainstream retrieval user-agents explicitly allowed

  Scored 62 / 86 observable · 4 checks left the denominator · rubric v1.1 · took 91.5 s
  Needs off-site search or judgement: p3.listings, p3.mentions, p4.question-coverage
  Not observable this run: p4.cn-engines (not a Chinese-language site)

  Full rubric and what each tier means:
  https://github.com/jianruntech/geo-score/blob/v1.5.0/rubric/v1.1.md
  Score moved, or a check shows —? https://github.com/jianruntech/geo-score/blob/v1.5.0/guide/troubleshooting.md

_{geo_score.py stripe.com，记录于 2026-10-03，使用 geo-score 1.5.0 并通过 HTTPS 代理（页脚中的时间包含代理耗时）。使用 1.8.3 运行的示例，请参见屏幕截图。从 1.7.0 起，报告还会在检查项目后、分数之外打印三项观察结果（逐页列出 robots.txt 规则、服务器 HTML 中的链接、hreflang），这些内容不会影响分数；此记录早于这些功能。参见 cli/README.md。}

CLI — 级别 1 是一个无依赖的单文件程序，每份报告都会记录运行耗时 （elapsed_s）。级别 2 和级别 3 需要添加同一发布版本中的 cli/geo_watch.py。如果从 PyPI 安装了软件包， 可使用 uvx [email protected]（或在执行 pipx install geo-score==1.8.3 后使用 geo-score）代替下方的 python3 cli/geo_score.py，三个级别都适用。

python3 cli/geo_score.py example.com            # human-readable
python3 cli/geo_score.py example.com --explain  # with the evidence behind every check
python3 cli/geo_score.py example.com --json     # conforms to schema/report.v2.json
python3 cli/geo_score.py example.com --compare competitor.com   # side by side
python3 cli/geo_score.py example.com --badge aiv-badge.svg      # embeddable SVG
python3 cli/geo_score.py example.com --badge-json aiv-badge.json  # the same badge as shields.io endpoint JSON
python3 cli/geo_score.py example.com --share                    # one line to paste somewhere
python3 cli/geo_score.py diff before.json after.json             # what changed between two reports, check by check
python3 cli/geo_score.py example.com --baseline before.json --fail-on-drop   # CI: re-score the same pages, fail only on a drop

“Scored with geo-score”：可选的徽章（用于你自己的 README）。 --badge aiv-badge.svg 会生成一个 SVG，显示你的 分数和等级。将它与 README 一起提交，并链接到说明该数字含义的页面、本仓库或 公开排行榜：

[![AIV readiness, scored with geo-score](aiv-badge.svg)](https://github.com/jianruntech/geo-score)

这是可选项，不会带来任何影响：徽章或回链都不会改变分数，也不会决定网站是否或何时出现在 排行榜上。网站通过添加网站的方式加入排行榜，绝不以添加链接为交换条件。已提交的 SVG 会显示生成它的那次运行结果；--badge-json 会将同一徽章输出为 shields.io 端点 JSON，因此无需重新生成图片也能保持 最新（详情）。

资源：geo-score://rubric/v1.1。

提示词：audit_site（url）、check_citations（question、brand）、weekly_watch、compare_runs（from、to）、explain_check（check_id）。

粗体参数为必填项。提示是工具的 MCP 注释：客户端可以据此决定需要确认哪些内容；这些只是提示，并非保证。只有 ask 和 run 可能产生费用，且只能使用你提供给服务的提供商密钥。

可以向 Agent 提出的问题：

geo-score watch · Lumo · run 20260926T083000Z · api channel

6 questions × 2 engines × 2 = 24 planned · 23 answered · 1 failed · 0 skipped

Cited in 38% of answers to questions that do not name Lumo (6 of 16, 4 questions, 95% CI 12–62%) · mentioned in 38%
Questions that name Lumo (2, kept out of the headline): cited in 100% (7 of 7, 95% CI 65–100%) · mentioned in 100%
Your site was cited somewhere for 5 of 6 questions.

By engine
  engine          model             cited         95% CI   mentioned  named first (tracked)  avg rank
  chatgpt-api     gpt-6-luna        9/12 75%      42–100%  75%        9/12                   1.0
  perplexity-api  sonar             4/11 36%      8–75%    36%        0/11                   2.0       1 failed
  gemini-api      gemini-3.8-flash  not measured                                                       no_key: set GEMINI_API_KEY or GOOGLE_API_KEY

These rows, and the tables below, count every question, the 2 that name Lumo included.

Answer share your pages support: not measured; this run was saved before citation positions were recorded.

Sources listed and used in the answer: not measured; this run was saved before listed sources were recorded.

Repeat consistency of cited domains (per engine; descriptive, not read by diff)
  engine          questions measured  pairs  median Jaccard
  chatgpt-api     6/6                 6      1.00
  perplexity-api  5/6                 5      1.00
  gemini-api      not measured                               no_key

Least consistent questions (up to 3 per engine):
  id   question                         engine          answers that cite  Jaccard
  q02  ai video tool with no watermark  chatgpt-api     2                  0.50
  q01  best free ai video generator     perplexity-api  2                  0.50

- Repeat consistency: for each question an engine answered more than once in this run, the overlap of the domains two of its answers cite, shared domains over all domains of the two (Jaccard), for every two answers, averaged per question; the median over questions per engine. 1: every ask cited the same domains; 0: no domain in common. Domains are read as everywhere in this report, www dropped; the order of citations is not compared.
- Answers that cite nothing are left out: two empty lists are not agreement, and one empty list is not a 0. On an engine, a question with fewer than two answers that cite is not measured. Lowest: up to 3 questions per engine whose answers did not all cite the same domains, lowest first.
- Descriptive only: no interval and no test, never part of the cited rate, and watch diff does not read it. It describes asks minutes apart in one run, which share that day's index; it is not computed over pooled runs.

Share of voice
              cited  95% CI  mentioned  named first (tracked)  sentence share
  Lumo (you)  57%    26–86%  57%        9/23                   100%
  Pixa        52%    33–71%  100%       14/23                  100%

- Named first (tracked): answers that name that brand before any other brand in your config, out of the answers that name at least one of them. Brands your config does not list are not seen, so first among the brands you track may not be first in the answer. Two brands first named at the same place, one name inside the other, are neither first.
- Sentence share: in the answers that name a brand, the mean share of their sentences that name it, every sentence counted the same. A sentence ends at a line break, at 。！？, or at . ! ? before a space.
- Both read the answer as saved, which keeps its first 20,000 characters; a name that first appears after that is not seen.

Sources the engines cite most (not yours)
  domain        answers  share  owner
  pixa.example  12       52%    Pixa
  reddit.com    11       48%

Questions where a competitor is cited and you are not (1)
  id   question                    cited instead
  q03  cheapest text to video app  Pixa

Who is named for each question
  id   question                         answers  Lumo (you)             Pixa               no tracked brand named  searched yes/no/unknown  most cited
  q01  best free ai video generator     4        cited 3/4 · named 3/4  cited 2 · named 4  0/4                     2/0/2                    Lumo (you)
  q02  ai video tool with no watermark  4        cited 1/4 · named 1/4  cited 2 · named 4  0/4                     2/0/2                    Pixa
  q03  cheapest text to video app       4        cited 0/4 · named 0/4  cited 2 · named 4  0/4                     2/0/2                    Pixa
  q04  lumo vs pixa                     4        cited 4/4 · named 4/4  cited 2 · named 4  0/4                     2/0/2                    Lumo (you)
  q05  pixa alternatives                4        cited 2/4 · named 2/4  cited 2 · named 4  0/4                     2/0/2                    —
  q06  鹿末视频免费吗                   3        cited 3/3 · named 3/3  cited 2 · named 3  0/3                     2/0/1                    —

- An answer given without a web search cannot cite anything.
- "No tracked brand named" counts answers that name none of the brands in your config; they may name others.
- Perplexity and OpenRouter search on every call or do not say, so their answers count as unknown under searched.

By question type
  type         cited     95% CI   mentioned
  alternative  2/4 50%   15–85%   50%
  list         4/8 50%   22–78%   50%
  pricing      3/7 43%   0–100%   43%
  vs           4/4 100%  51–100%  100%

What the engines searched for (from 12 answers that show it)
  times  search
  2      best free ai video generator
  2      ai video tool with no watermark
  2      cheapest text to video app
  2      lumo vs pixa
  2      pixa alternatives
  2      鹿末视频免费吗

- Of 12 searches: 0 contain a year, 6 contain a ranking or comparison word.

Ledger
24 questions asked · 23 API requests · 14,620 in / 4,860 out tokens · 23 searches · $0.07 + 12 answers with no price (add prices to geo-score-watch.json)
1 failed after 24 HTTP requests in all; a request that timed out may still be billed.
Caps: at most 100 questions.

Read this before quoting the numbers
- API channel. Answers come from each provider's search-enabled API, which is not the consumer app. Compare runs with runs; never pool them with answers sampled by hand in the apps.
- The same question gets different answers from one ask to the next, and answers to one question move together. Rates carry a 95% interval: Wilson when each question was answered once, a bootstrap over questions when a question has several answers. diff pairs the questions both runs answered and calls a change a change only when an exact paired test (McNemar, or a sign-flip test when a question has several answers), Holm-corrected across engines, says so (p < 0.05).
- A question that names the brand invites an answer that cites it. Those questions are kept out of the headline rate and reported on a line of their own.
- Engines without a key, calls that failed and calls skipped by a cap count as not measured, never as zero.
- This measures citations. It does not predict traffic, rankings or revenue.
- This run was saved before questions were flagged at run time. Questions that name the brand were found when this report was made, from the saved question text and the run's brand name, aliases and domains.

第 3 级会保留固定的问题列表，将每个答案保存到 .geo-score/watch/runs/ （架构），并报告：

它不会告诉你什么。

• 它不是 ChatGPT 应用。 答案来自各服务提供商已启用网络搜索的 API。面向消费者的应用使用其他模型、提示词和个性化设置。请用 API 运行结果与 API 运行结果比较；不要与在应用中手动抽样的答案混在一起。
• 有些界面无法触及。 Google AI Overviews 和 AI Mode、TikTok、Reddit 或小红书等应用内的 AI 摘要、助手的记忆和账户设置、比国家提示更精细的地理位置，以及编码 Agent 选择了哪个库，都无法通过这些 API 触及。
• 引用表示出现，不代表质量。 引用率表示引擎提到了你并链接到你，而不代表它所说的内容属实，也不代表该页面值得引用；引擎也会引用误导性和自我宣传的页面。
• 单个答案只是个例。 每项比率都附带 95% 区间（当一个问题有多个答案时，按问题进行自助抽样，因为这些答案会共同变化）；只有当对两次运行都回答的问题进行精确配对检验，并在各引擎间进行 Holm 校正后，diff 确认结果显著（p < 0.05），才会将其称为变化。共同问题太少（少于 6 个，或不足以比较所涉及的引擎数量）时，报告会注明数据不足，无法判断。方法说明：guide/watch-methodology.md。
• 提到你的问题会单独处理。 “acme vs rival”或“is acme worth it”会把你的名称放进引擎的搜索中，因此几乎总会被引用。watch 会在运行时标记这些问题，将它们排除在总体比率之外，并在单独一行报告及其数量。你也可以在 queries.csv 中添加可选的 branded 列，手动修正标记。
• 未测量不等于零。 没有密钥的引擎、失败的调用和达到上限的调用都会报告为未测量，且不会拉低你的比率。
• 引用不等于流量。 这里的任何内容都无法预测访问量、排名或收入。 引擎。 在配置中固定你使用的模型，并在各次运行之间保持不变；diff 会标记模型发生变化的运行。OpenRouter 用一个密钥即可接入数百种模型。

上限和费用。 max_calls 是一次运行所提问题数量的精确上限，超出上限的计划将无法启动。每次调用前，系统都会将 budget_usd 与截至目前的支出加上该引擎已出现的最高单次调用费用进行比较，因此每个引擎最多可能超出一次调用的费用；设置预算后，除非传入 --allow-unpriced，否则会排除无法确定费用的引擎。每次运行都会记录请求、令牌、搜索和费用。配置、价格和所有命令详见：cli/README.md。

通过 Agent 使用。 第 2 级和第 3 级也提供 MCP 工具，Agent 只能收紧你的上限，不能放宽：参见 MCP 服务。

每周运行。 引用率变化缓慢且有噪声：请在每周同一天使用相同的问题和模型运行，并查看 diff，而非单次运行结果。 examples/ci/watch-weekly.yml 会按计划运行，使用来自仓库机密的密钥，并提交每次运行的结果，因此历史记录会保存在 git 中。运行文件包含你的问题和完整答案：如果内容涉密，请使用私有仓库。