Back to Details

search-console-readiness

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

search-console-readiness

search-console-readiness

Search engines tell you what they indexed. Nothing in the repository can. This skill prepares everything on your side and gives the owner a short, accurate checklist for the parts only they can do.
搜索引擎会告诉你哪些内容已被索引。仓库本身无法提供这些信息。此 skill 会准备好你这一侧需要的一切，并为所有者提供一份简短、准确的清单，列出只有他们才能完成的部分。

Activate when

何时启用

  • The production URL is decided and live, or launch is imminent, and the owner wants to be findable.
  • seo-readiness
    is clean (or nearly), so submitting a broken sitemap is not the outcome.
  • Not before the canonical host is final, and not on staging.
  • production URL 已确定并上线，或发布迫在眉睫，且所有者希望网站能够被搜索到。
  • seo-readiness
    检查结果已通过（或基本通过），以免最终提交的是损坏的 sitemap。
  • 不得在 canonical host 最终确定之前使用，也不得在 staging 上使用。

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. 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
.
此 skill 是自包含的。它的 companions（在 metadata 中声明）是本 skill 可能需要调用其方法来完成自身承诺工作的其他 skill。companion 的使用可以是条件性的：声明某个 companion 并不意味着一定会运行它。当某个 companion 的 lane 适用时，如果该 skill 已安装，则使用它；如果未安装，则遵循 references/companion-methods.md 中的简短条目执行，并在报告中说明哪些 lane 以 inline 方式按较低深度运行。绝不能默默跳过任何适用的 lane。此处仅出于升级处理、转介、文档记录或可选的后续深入跟进而提及的 skill 不属于 dependencies：应报告 hand-off，并如实完成当前工作。
Companions：
seo-readiness
。

Inspect

检查

  1. Preconditions: 
    seo-readiness
    results (no HIGH); the production origin is final; the canonical host, HTTPS, and 
    www
    /apex redirect policy are settled; the sitemap lists canonical live URLs and is declared in 
    robots.txt
    .
  2. Verification method available: DNS TXT (preferred, covers all subdomains), HTML file upload, meta tag, or existing analytics/tag-manager ownership. Check what the project already has (a leftover 
    google-site-verification
    file or meta tag from a template/previous owner may belong to someone else).
  3. Bing / other engines (Webmaster Tools import, IndexNow) if relevant.
  4. What the owner must do themselves and cannot be done by the agent: sign in, claim the property, add DNS records, submit the sitemap, request indexing for key URLs.
  5. What only Search Console shows: indexed vs. not, coverage reasons, crawl errors, mobile usability, structured-data errors, manual actions.
  1. 前提条件： 
    seo-readiness
    的结果（无 HIGH）；production origin 已最终确定；canonical host、HTTPS 以及 
    www
    /apex 重定向策略均已确定；sitemap 列出 canonical 的线上 URL，并在 
    robots.txt
    中声明。
  2. 可用的验证方式： DNS TXT（首选，可覆盖所有子域名）、HTML 文件上传、meta tag，或通过已有的 analytics/tag-manager 所有权进行验证。检查项目当前已有的内容（模板或前任所有者遗留的 
    google-site-verification
    文件或 meta tag 可能属于其他人）。
  3. Bing / 其他搜索引擎： 如相关，检查 Webmaster Tools 导入和 IndexNow。
  4. 必须由所有者亲自完成、Agent 无法代为完成的事项： 登录、认领网站资源、添加 DNS 记录、提交 sitemap、请求关键 URL 的索引。
  5. 只有 Search Console 才能显示的信息： 已索引与未索引状态、coverage 原因、crawl errors、mobile usability、structured-data errors、manual actions。

Evidence that counts

有效证据

Label each claim OBSERVED, SOURCE-INDICATED, DECLARED, INFERRED, UNKNOWN, or REVIEW REQUIRED. UNKNOWN is never a pass and never a failure.
  • Everything about indexing status is UNKNOWN without console data supplied by the owner (DECLARED).
  • A verification tag in the repo proves nothing about ownership.
将每项结论标记为 OBSERVED、SOURCE-INDICATED、DECLARED、INFERRED、UNKNOWN 或 REVIEW REQUIRED。UNKNOWN 既不算通过，也不算失败。
  • 未提供所有者提供的 console 数据时，有关索引状态的一切均为 UNKNOWN（DECLARED）。
  • 仓库中的 verification tag 不能证明任何所有权关系。

May change

可以更改的内容

Add a verification meta tag or file only when the owner provides the token (never invent tokens); ensure 
robots.txt
declares the sitemap; add IndexNow key files if requested. Prepare a short written checklist in the reply. Do not sign in to accounts, add DNS records, or click submit on the owner's behalf.
只有在所有者提供 token 时，才能添加 verification meta tag 或文件（绝不虚构 token）；确保 
robots.txt
声明 sitemap；如有要求，添加 IndexNow key 文件。在回复中准备一份简短的书面清单。不得登录账户、添加 DNS 记录，或代所有者点击提交。

Must not claim

不得声称

"Indexed", "submitted", "verified", "will appear in Google within X days", or any ranking outcome.
“已索引”、“已提交”、“已验证”、“将在 X 天内出现在 Google 中”或任何排名结果。

Verify

验证

Confirm the verification file or tag is reachable at the production URL and matches the owner's token; confirm the sitemap URL to submit returns 200 XML with the expected host. After the owner submits, ask them to paste coverage results and interpret those as DECLARED evidence.
确认 verification file 或 tag 可在 production URL 访问，且与所有者的 token 匹配；确认待提交的 sitemap URL 返回状态码为 200 的 XML 响应，且 host 符合预期。所有者提交后，请其粘贴 coverage 结果，并将其解释为 DECLARED 证据。

Escalate

升级处理

Domain ownership questions, migrations, penalties, or mass "Crawled, not indexed" statuses: technical SEO review beyond this pass.
域名所有权问题、迁移、处罚或大量出现“Crawled, not indexed”状态：需要开展超出本轮范围的技术 SEO 审查。

No change is valid when

以下情况无需进行更改

The site is intentionally private, still on staging, or already verified with a submitted sitemap. Say so and stop.
网站有意保持私有、仍处于 staging，或已完成验证并提交了 sitemap。说明情况并停止。