discoverability-all

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

discoverability-all

Owns launch family B (checks 9–18): titles, descriptions, canonicals, robots.txt, sitemap.xml, social metadata, favicon/icons, indexing sanity, staging/localhost references, and public URL consistency.

The signals in this family contradict each other far more often than they are missing: a localhost canonical on a page the sitemap advertises, a

noindex

page listed in the sitemap, robots blocking what the sitemap lists, a staging host in an Open Graph URL. Existence checks miss all of that. This skill reviews the relationships once, then hands specialists a shared picture so none of them re-crawls the site.

负责 launch family B（检查项 9–18）：标题、描述、canonical、robots.txt、sitemap.xml、社交媒体 metadata、favicon/icons、索引状态合理性、staging/localhost 引用，以及公开 URL 的一致性。

这一检查组中的各项信号彼此矛盾的情况，远比单纯缺失更常见：例如 sitemap 所宣传的页面使用 localhost canonical；sitemap 中列出了 noindex 页面；robots 屏蔽了 sitemap 中列出的内容；Open Graph URL 中包含 staging host。仅检查是否存在会漏掉上述所有问题。此 skill 会一次性审查这些关系，然后将共享的整体情况交给各专项 skill，避免它们重复抓取站点。

Activate when

何时启用

The site is public and should be discoverable or shareable, or a launch/rebrand/domain move is near.
```
launch-all
```
routes here.
Not when the product is private or intentionally unindexed. In that case confirm it is consistently noindex (meta or header, no sitemap, robots not advertising private paths) and stop.

站点是公开的，且应当可被发现或分享，或者即将上线、品牌重塑或迁移域名。
```
launch-all
```
会路由到这里。
产品为私有或有意设置为 unindexed 时不要使用。在这种情况下，确认其是否始终一致地设置为 noindex（通过 meta 或 header 设置、不包含在 sitemap 中，且 robots 未公开任何私有路径），然后停止。

Working alone

独立工作时

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. The lanes this bundle can activate are companions because it promises to run them when they apply: consider them all, activate only the ones that fit. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions:

seo-readiness

social-sharing

launch-identity

deployment-cleanup

search-console-readiness

structured-data

multilingual-readiness

link-integrity

此 skill 是自包含的。它在 metadata 中声明的 companions，是它为履行自身承诺而可能需要借助其方法的 skills。companion 的使用可以是条件性的：声明某个 companion 并不意味着一定会运行它。当某个 companion 的检查范围适用时，如果已安装该 skill，就使用它；如果未安装，则遵循 references/companion-methods.md 中对应的简短条目，并在报告中说明哪些检查范围是以较低深度内联执行的。绝不静默跳过任何适用的检查范围。由于本 bundle 承诺在适用时运行这些 companions，因此这些检查范围均属于 companions：应将它们全部纳入考虑，但只激活符合当前需求的那些。此处仅因升级、转交、文档记录或可选的深入后续处理而提及的 skills 不属于依赖项：应报告转交情况，并如实完成剩余工作。

Companions：

seo-readiness

、

social-sharing

、

launch-identity

、

deployment-cleanup

、

search-console-readiness

、

structured-data

、

multilingual-readiness

、

link-integrity

。

Route

路由

Intent and host. Establish: should this be indexed? What is the production origin (scheme + host,
```
www
```
or not)? Which routes are public, which are private (account, dashboard, admin, checkout, preview)? Read
```
.readyvibe/context.md
```
, deployment config, and env templates. If the production URL is unknown, ask once; otherwise use the declared one.
Shared sweep. Run once and reuse the output (paths are relative to this skill's folder; add
```
--render
```
for client-rendered apps):
bash
```
node scripts/inspect-metadata.mjs --url <site> --render --private-path /dashboard
node scripts/check-links.mjs      --url <site> --render
```
Serve a build locally if needed. Without a server, use
```
--dir <build output>
```
and mark server-dependent items UNKNOWN.
Select specialists from the findings, not the table:

Findings show	Specialist
titles, descriptions, canonicals, robots, sitemap, noindex, URL agreement (9–13, 16, 18)	`seo-readiness`
missing/incorrect Open Graph or Twitter tags, share image (14)	`social-sharing`
starter favicon, missing icons, product-name mismatch in titles (15)	`launch-identity`
localhost/staging/preview hosts anywhere shipped (17)	`deployment-cleanup`
the owner wants Search Console/Bing verification steps	`search-console-readiness`
a real article, product, organization, or FAQ page and JSON-LD exists or would help	`structured-data`
more than one language	`multilingual-readiness` (hreflang, per-language canonicals)
broken sitemap or canonical targets	`link-integrity`

Skip

structured-data

and

search-console-readiness

unless there is a concrete reason. Do not add JSON-LD to a page whose content is not what the schema claims.

意图与 host。 确定：是否应被索引？production origin 是什么（scheme + host，是否使用
```
www
```
）？哪些 routes 是公开的，哪些是私有的（account、dashboard、admin、checkout、preview）？读取
```
.readyvibe/context.md
```
、deployment config 和 env templates。如果 production URL 未知，则询问一次；否则使用已声明的 URL。
共享扫描。 运行一次并复用输出（路径相对于此 skill 的目录；对于客户端渲染的应用，添加
```
--render
```
）：
bash
```
node scripts/inspect-metadata.mjs --url <site> --render --private-path /dashboard
node scripts/check-links.mjs      --url <site> --render
```
如有必要，在本地启动构建产物的服务。没有服务器时，使用
```
--dir <build output>
```
，并将依赖服务器的项目标记为 UNKNOWN。
根据检查结果选择专项 skill，而不是根据表格选择：

检查结果表明	专项 skill
标题、描述、canonical、robots、sitemap、noindex 或 URL 不一致（9–13、16、18）	`seo-readiness`
Open Graph 或 Twitter 标签缺失或错误，或分享图片有问题（14）	`social-sharing`
仍使用初始 favicon、icons 缺失，或标题中的产品名称不匹配（15）	`launch-identity`
交付内容中的任何位置出现 localhost/staging/preview host（17）	`deployment-cleanup`
所有者需要 Search Console/Bing 验证步骤	`search-console-readiness`
存在实际的 article、product、organization 或 FAQ 页面，且已有 JSON-LD 或添加后会有帮助	`structured-data`
站点包含多种语言	`multilingual-readiness` （hreflang、各语言的 canonical）
sitemap 损坏或 canonical 目标失效	`link-integrity`

除非有明确原因，否则跳过

structured-data

和

search-console-readiness

。不要向页面内容与 schema 声明不符的页面添加 JSON-LD。

Evidence discipline

证据规范

Label each claim OBSERVED, SOURCE-INDICATED, DECLARED, INFERRED, UNKNOWN, or REVIEW REQUIRED. UNKNOWN is never a pass and never a failure.

A sitemap that exists is not a sitemap that is safe and correct. Correctness means: canonical, public, live, non-redirecting, not blocked, not noindex.
Source with a canonical tag is not proof of the rendered canonical (a framework may override it). Read rendered HTML.
Indexing intent is a fact about the owner's plan: DECLARED or asked, never guessed from the framework.
Never claim a page "will be indexed" or "will rank". Indexing needs search-engine data.

将每项论断标记为 OBSERVED、SOURCE-INDICATED、DECLARED、INFERRED、UNKNOWN 或 REVIEW REQUIRED。UNKNOWN 既不表示通过，也不表示失败。

sitemap 存在，并不代表它安全且正确。正确意味着：具有 canonical、公开、线上可访问、不发生重定向、未被屏蔽且不是 noindex。
源代码中存在 canonical 标签，不能证明渲染后的 canonical 也如此（框架可能会覆盖它）。应读取渲染后的 HTML。
索引意图是所有者计划中的事实：应标记为 DECLARED 或通过询问确认，绝不能根据框架进行猜测。
绝不能声称页面“will be indexed”或“will rank”。索引情况需要搜索引擎数据支持。

May change

可以更改

Metadata tags and site config that generate them,

robots.txt

sitemap.xml

(or its generator), favicon/icon files and links, canonical values (only once the production origin is known). Specialists define their own limits.

Metadata 标签及生成这些标签的站点配置、

robots.txt

、

sitemap.xml

（或其生成器）、favicon/icon 文件及其链接、canonical 值（仅在 production origin 已知后）。各专项 skill 自行界定其修改范围。

Must not claim

绝不能声称

"SEO-optimized", "will rank", "will be indexed", "Google-approved", or a score. Report agreements and contradictions found, and fixes verified.

“SEO-optimized”、“will rank”、“will be indexed”、“Google-approved”，也不要给出评分。应报告发现的一致之处与矛盾之处，以及已验证的修复。

Verify

验证

Re-run the sweep after changes. Success means the relationships hold: every sitemap URL is canonical, public, returns 200, is not noindex and not blocked; every canonical target resolves; the production host is the same everywhere; no localhost/staging strings remain. For a deployed site, spot-check the live URL, not just local output.

更改后重新运行扫描。成功意味着各项关系均成立：每个 sitemap URL 都是自身的 canonical、公开、返回 200、未设置 noindex 且未被屏蔽；每个 canonical 目标均可正常解析；production host 处处一致；不残留任何 localhost/staging 字符串。对于已部署的站点，应抽查线上 URL，而不只是本地输出。

Escalate

升级处理

Production origin unknown or about to change: ask before writing any absolute URL.
A private route that is reachable (not just listed) is a security finding: hand to
```
web-security
```
.
Multi-domain, multi-language, or migration setups with redirects: REVIEW REQUIRED for the redirect map.

production origin 未知或即将更改：写入任何绝对 URL 之前先询问。
可实际访问（而不只是被列出）的私有 route 属于安全问题：转交
```
web-security
```
。
涉及重定向的 multi-domain、multi-language 或 migration 配置：redirect map 标记为 REVIEW REQUIRED。

No change is valid when

以下情况无需进行更改

The site is intentionally private and consistently noindex; or a single-page site legitimately has no sitemap; or the findings are explained by context (a

noindex

/dashboard

is correct). Do not add a sitemap or structured data just to satisfy a checklist.

站点有意设为私有且始终一致地设置为 noindex；或单页站点确实不需要 sitemap；或检查结果可由上下文解释（

/dashboard

上的 noindex 是正确的）。不要只是为了满足检查清单而添加 sitemap 或 structured data。