Back to Details

seo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

seo

seo

seo
is a local CLI, MCP server, and report engine using crawl, Search Console, Google Analytics or Clicky, optional Bing evidence, and optional research providers. Reports keep observations, estimates, findings, caveats, costs, and provenance separate. Storage stays local; requested crawls and provider operations still make direct network requests. Discover reports at runtime instead of memorising them.
seo
是一款本地CLI、MCP服务器及报告引擎，可结合爬取数据、Search Console、Google Analytics或Clicky数据，还可选择接入Bing实证数据及研究供应商数据。报告将观察结果、估算值、发现、注意事项、成本及来源区分存储。数据存储于本地；爬取请求及供应商操作仍会发起直接网络请求。无需记忆报告内容，可在运行时发现可用报告。

Discover, describe, run

发现、描述、运行

With the MCP server (preferred):
  1. seo_list_reports
    returns report ids and purposes, optionally by category.
  2. seo_describe_report
    returns one report's usage, schema, reading order, limits, verification, and related ids.
  3. seo_run_report
    runs bounded 
    params
    . Read 
    structuredContent
    , not display text.
The same catalog exists without MCP:
bash
seo reports list --json
seo reports describe <report-id> --json
seo reports run <report-id> --params '<json>' --json
Describe a report before its first run. Follow 
readOrder
, 
doNotClaim
, and 
related
; reuse its schema and do not guess parameters. When 
fixableChecks
exists, fetch guidance only for failed or warning ids in 
topActions
with 
seo_describe_report
using 
id
and 
check
(CLI: 
seo reports describe <report-id> --check <check-id>
).
推荐使用MCP服务器：
  1. seo_list_reports
    返回报告ID及用途，可按分类筛选。
  2. seo_describe_report
    返回单个报告的使用方法、schema、阅读顺序、限制条件、验证方式及相关报告ID。
  3. seo_run_report
    运行带有限定参数的报告。请读取
    structuredContent
    ，而非显示文本。
无需MCP服务器也可使用相同的报告目录：
bash
seo reports list --json
seo reports describe <report-id> --json
seo reports run <report-id> --params '<json>' --json
首次运行报告前请先查看其描述。遵循
readOrder
、
doNotClaim
及
related
规则；复用报告的schema，请勿猜测参数。当存在
fixableChecks
时，仅针对
topActions
中失败或警告的ID，通过
seo_describe_report
并传入
id
和
check
获取指导（CLI命令：
seo reports describe <report-id> --check <check-id>
）。

Setup and selection

设置与选择

Use 
setup-check
or 
seo doctor
when auth is unknown. Select profiles with 
--project <id>
and list them with 
seo projects list --json
. Without one, pass 
--site sc-domain:example.com
or 
--url https://example.com
. Crawl audits need no Google connection. Agent commands use 
--json
, which never prompts.
当认证状态未知时，使用
setup-check
或
seo doctor
命令。通过
--project <id>
选择配置文件，使用
seo projects list --json
列出所有配置文件。若未指定配置文件，可传入
--site sc-domain:example.com
或
--url https://example.com
。爬取审计无需连接Google。Agent命令需使用
--json
参数，该参数不会触发交互提示。

Common jobs

常见任务

Run the first report, read it, then decide. Do not run a whole chain blindly.
JobReports
Page not indexed or missing from Google
index-coverage
, 
index-monitor
(URL Inspection), 
audit-page
, 
redirect-trace
Traffic or clicks dropped
search-performance-overview
, 
traffic-anomaly
, 
update-correlation
, 
segment-impact
, 
decaying-pages
, 
link-recovery
Audit a whole site
site-crawl
with 
health: true
, 
report
command (main report), full 
site-crawl
only if needed, 
top-fixes
, 
ai-search-scorecard
More clicks from existing pages
quick-wins
, 
ctr-underperformers
, 
striking-distance
, 
second-page
, 
internal-links
AI agent readiness for a content site
agent-readiness
, 
ai-readiness
, 
entity-readiness
, 
llms-txt-audit
AI search visibility and eligibility
ai-readiness
, 
geo-gaps
, 
ai-mention-research
, 
ai-prompt-observations
, 
ai-referrals
, 
seo-to-ai-query
Plan content from real demand
query-clusters
, 
page-opportunities
, 
content-optimization
, 
cannibalisation
Research keywords and current results
keyword-research
, 
keyword-metrics
, 
saved-keywords
, 
serp-results
Turn a topic into a keyword and competitor shortlist
competitive-opportunities
, then inspect the decision-critical pages or links
Research local demand and page patterns
local-search-demand
, then 
serp-results
or 
rank-tracking
for a fixed market when needed
Find search competitors and plausible gaps
serp-competitors
, 
domain-overview
, 
ranking-pages
, 
ranked-keywords
, 
competitor-keyword-gap
Research programmatic SEO patterns
pseo-patterns
for observed queries and declared term, pair, or matrix sets; 
pseo-opportunities
, 
ranking-pages
, or 
competitor-keyword-gap
for deeper research; then 
pseo-audit
for existing templates
Catch regressions over time
technical-watch
, 
crawl-diff
, 
index-watch
, 
measure-change
after a fix ships
Track exact keyword positions
rank-tracking
for a saved set and fixed market/device; 
serp-results
for one current query
Review Bing traffic, crawl, query, and page insights
bing-webmaster-overview
, then 
site-crawl
when live page evidence is needed
Review backlink context and linked targets
domain-rating
, 
link-evidence
, then verify selected results, referring URLs, and flagged targets directly
Review real crawler requests in a server log
server-log-analysis
, then verify important errors against the original log and server configuration
Client-ready reporting
monthly-report
, 
narrative-report
, 
monthly-action-plan
Turn crawl findings into tickets
top-fixes
, 
affected-urls
, 
explain-crawl-issue
Without provider API access, describe 
ranked-keywords
, 
ranking-pages
, 
serp-competitors
, or 
competitor-keyword-gap
and pass one to four local ranked-keyword exports through 
researchFiles
. Read 
evidence.imports
before using the rows. If headings are unfamiliar, use the report schema's explicit 
columns
map rather than guessing. File dates, hashes, included fields, column mappings, filtered historical rows, rejected rows, and caps define the evidence boundary.
Use 
seo report
first for a broad performance question with a known project. For a large or unfamiliar URL, run sitemap health before a full crawl.
先运行首个报告并阅读，再做决策。请勿盲目运行整个报告链。
任务对应报告
页面未被Google索引或缺失
index-coverage
、
index-monitor
（URL检测）、
audit-page
、
redirect-trace
流量或点击量下降
search-performance-overview
、
traffic-anomaly
、
update-correlation
、
segment-impact
、
decaying-pages
、
link-recovery
整站审计启用
health: true
参数的
site-crawl
、
report
命令（主报告），仅在需要时运行完整
site-crawl
、
top-fixes
、
ai-search-scorecard
现有页面获取更多点击
quick-wins
、
ctr-underperformers
、
striking-distance
、
second-page
、
internal-links
内容站点的AI Agent就绪性检测
agent-readiness
、
ai-readiness
、
entity-readiness
、
llms-txt-audit
AI搜索可见性与资格检测
ai-readiness
、
geo-gaps
、
ai-mention-research
、
ai-prompt-observations
、
ai-referrals
、
seo-to-ai-query
根据真实需求规划内容
query-clusters
、
page-opportunities
、
content-optimization
、
cannibalisation
关键词研究与当前结果分析
keyword-research
、
keyword-metrics
、
saved-keywords
、
serp-results
将主题转化为关键词及竞品短名单
competitive-opportunities
，随后检查决策关键页面或链接
本地需求与页面模式研究
local-search-demand
，必要时针对固定市场运行
serp-results
或
rank-tracking
寻找搜索竞品及潜在缺口
serp-competitors
、
domain-overview
、
ranking-pages
、
ranked-keywords
、
competitor-keyword-gap
程序化SEO模式研究
pseo-patterns
用于分析观测到的查询及已声明的术语、配对或矩阵集合；
pseo-opportunities
、
ranking-pages
或
competitor-keyword-gap
用于深度研究；随后使用
pseo-audit
检测现有模板
及时发现回归问题
technical-watch
、
crawl-diff
、
index-watch
，修复完成后运行
measure-change
追踪精确关键词排名针对已保存的关键词集合及固定市场/设备运行
rank-tracking
；针对单个当前查询运行
serp-results
查看Bing流量、爬取、查询及页面洞察
bing-webmaster-overview
，需要实时页面实证时运行
site-crawl
查看反向链接上下文及链接目标
domain-rating
、
link-evidence
，随后直接验证选定结果、引用URL及标记目标
分析服务器日志中的真实爬虫请求
server-log-analysis
，随后对照原始日志及服务器配置验证重要错误
面向客户的报告
monthly-report
、
narrative-report
、
monthly-action-plan
将爬取发现转化为工单
top-fixes
、
affected-urls
、
explain-crawl-issue
若无法访问供应商API，可查看
ranked-keywords
、
ranking-pages
、
serp-competitors
或
competitor-keyword-gap
的描述，并通过
researchFiles
传入1至4份本地导出的排名关键词文件。使用数据行前请阅读
evidence.imports
。若表头不熟悉，请使用报告schema中明确的
columns
映射，请勿猜测。文件日期、哈希值、包含字段、列映射、过滤后的历史行、被拒绝的行及上限值定义了实证范围。
针对已知项目的广泛性能问题，优先使用
seo report
命令。对于大型或不熟悉的URL，在完整爬取前先运行站点地图健康检测。

Create a client HTML report

创建客户端HTML报告

For a polished or branded report, create one standalone HTML file from structured data. Built-in 
--format html
is a predictable fallback. Start with compact JSON and request 
--full
only when deeper evidence is needed. Follow supplied brand direction and design for the findings. Use responsive, accessible, print-friendly HTML, embedded CSS, 
noindex,nofollow
, and no remote scripts or assets.
Show site, period, generated date, provider labels, data status, priorities, limitations, and verification. Preserve partial, capped, sampled, missing, and skipped states. Keep observations separate from interpretation and providers separate from each other. Never invent scores, forecasts, causes, or missing values. Omit secrets and unnecessary raw rows. Save locally and report the path.
For a large site, run 
site-crawl
with 
health: true
and an explicit 
sitemapUrl
when known. Read 
config.strategy
, 
access
, failures, limits, and sitemap completeness. Full crawl second only for page content, metadata, canonicals, links, structured data, or rendered HTML.
Requests use 
SEO-Skill/<version> (+https://seoskill.dev)
. For 
access.blockedRequests
, show provider evidence and the identity. Ask for a temporary exception scoped by audit IP, host or paths, and blocking rule. Never recommend a User-Agent-only bypass.
如需生成精美或品牌化报告，可从结构化数据创建单个独立HTML文件。内置的
--format html
参数是可靠的备选方案。先从紧凑JSON开始，仅在需要深度实证时请求
--full
参数。遵循给定的品牌方向及设计呈现发现内容。使用响应式、可访问、适合打印的HTML，内嵌CSS，设置
noindex,nofollow
，且不使用远程脚本或资源。
显示站点信息、周期、生成日期、供应商标签、数据状态、优先级、限制条件及验证方式。保留部分、上限、抽样、缺失及跳过的状态。将观察结果与解读分离，将不同供应商的数据分离。切勿编造分数、预测、原因或缺失值。省略机密信息及不必要的原始数据行。本地保存并报告文件路径。
对于大型站点，运行
site-crawl
时启用
health: true
参数，若已知站点地图URL则传入明确的
sitemapUrl
。查看
config.strategy
、
access
、失败情况、限制条件及站点地图完整性。仅在需要页面内容、元数据、规范链接、链接、结构化数据或渲染后的HTML时，才进行完整爬取。
请求使用
SEO-Skill/<version> (+https://seoskill.dev)
标识。对于
access.blockedRequests
，需展示供应商实证及身份信息。请求按审计IP、主机或路径、拦截规则设置临时例外。切勿仅通过修改User-Agent绕过拦截。

Evidence rules

实证规则

  • Check 
    dataStatus
    , selection counts, 
    caveats
    , and 
    warnings
    before summarising any report. Name skipped or incomplete evidence first.
  • Partial, capped, filtered, or sampled sources never support a zero or an all-clear. Grouped Search Console totals undercount because anonymised query rows are withheld.
  • Values marked heuristic are prioritisation aids, not forecasts. Never promise clicks, rankings, indexing, or AI citations from any report.
  • Quote 
    principle
    and 
    evidenceRef
    when explaining a recommendation, and give the user the report's verification step alongside any suggested change.
  • If a report returns no rows, say so plainly.
  • Intentional controls such as 
    noindex
    , canonicals, and robots rules are observations until the user confirms they are unintended.
  • Provider traffic, volume, difficulty, visibility, intent, authority, and ranking history are estimates. Keep them separate from Search Console, connected analytics, crawl, and live result evidence.
  • 在总结任何报告前，请检查
    dataStatus
    、选择计数、
    caveats
    及
    warnings
    。首先说明跳过或不完整的实证内容。
  • 部分、上限、过滤或抽样的数据源无法支持“无问题”的结论。分组后的Search Console总数会被低估，因为匿名查询行被隐藏。
  • 标记为heuristic的值仅用于优先级辅助，而非预测。切勿承诺任何报告可带来点击量、排名提升、索引收录或AI引用。
  • 解释建议时请引用
    principle
    及
    evidenceRef
    ，并向用户提供报告的验证步骤及建议的修改方案。
  • 若报告未返回任何数据行，请直接说明。
  • noindex
    、规范链接及robots规则等有意设置的控制项，在用户确认其为无意设置前，均视为观察结果。
  • 供应商提供的流量、数量、难度、可见性、意图、权威性及排名历史均为估算值。请将其与Search Console、关联分析、爬取及实时结果实证区分开。

Beyond the report catalog

报告目录之外

Use 
seo help all
for direct provider and administration commands. Bing setup uses 
seo providers bing
; link evidence uses 
seo links --project <id> --json
, 
seo links --provider ahrefs --target <domain> --json
, 
seo links --provider dataforseo --target <domain> --json
, or a local file. IndexNow writes externally: validate with 
seo indexnow submit --dry-run --json
and remove dry run only when authorised. Receipt does not prove crawling or indexing. Prefer registered reports.
Use 
refresh: true
or 
--refresh
only when fresh data is requested. Sitemap health always bypasses page-body cache and never writes page responses.
使用
seo help all
查看直接调用供应商及管理的命令。Bing设置使用
seo providers bing
；链接实证使用
seo links --project <id> --json
、
seo links --provider ahrefs --target <domain> --json
、
seo links --provider dataforseo --target <domain> --json
或本地文件。IndexNow会向外部提交数据：使用
seo indexnow submit --dry-run --json
验证，仅在获得授权后移除dry-run参数。提交回执不代表爬取或索引成功。优先使用已注册的报告。
仅在请求新鲜数据时使用
refresh: true
或
--refresh
参数。站点地图健康检测始终绕过页面内容缓存，且不会写入页面响应。