Back to Details

anycap-ai-tool-seo

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

AnyCap AI Tool SEO

AnyCap AI工具SEO

Read this entire file before starting. It covers the full SEO planning and audit workflow for AI tool websites.
Plan and audit SEO for AI tool websites. Focus on product-led SEO where each page should help a searcher complete a task, evaluate options, or enter the product with high intent.
Map intent. Shape pages. Add evidence. Protect quality.
开始前请完整阅读本文件。 它涵盖了AI工具网站完整的SEO规划和审计工作流。
本指南用于AI工具网站的SEO规划与审计，重点聚焦产品驱动型SEO，这类SEO要求每个页面都能帮助搜索者完成任务、评估选项，或是以高意图进入产品流程。
匹配意图，打造页面，补充实证，保障质量。

Before You Start

开始之前

Read all three reference files before taking any action. They contain the working framework, page planning rules, and quality guardrails.
  1. Read this file for the overview and process
  2. Read the references in this order:
    • framework.md
    • page-planning.md
    • guardrails.md
  3. Then begin the workflow below
For detailed command syntax, flags, and output parsing, refer to the anycap-cli skill.
执行任何操作前请先阅读全部三份参考文件，它们包含了可用框架、页面规划规则和质量护栏。
  1. 先阅读本文件了解概览和流程
  2. 按以下顺序阅读参考文件：
    • framework.md
    • page-planning.md
    • guardrails.md
  3. 之后再开始执行下方的工作流
如需了解详细的命令语法、参数和输出解析，请参考anycap-cli技能。

Prerequisites

前提条件

  • anycap
    CLI installed and authenticated (
    anycap status
    to verify)
  • A local workspace for notes, saved search results, and page briefs
  • 已安装
    anycap
    CLI并完成认证（可执行
    anycap status
    验证）
  • 用于存放笔记、保存的搜索结果和页面概要的本地工作区

When to Use This Skill

何时使用本技能

  • AI tool website SEO planning
  • SaaS or product-led SEO audits
  • Search intent to page type mapping
  • Page brief creation for tool, comparison, alternatives, pricing, and tutorial pages
  • Technical SEO prioritization for new or growing tool websites
  • Citation, directory, or backlink planning
  • Programmatic SEO evaluation and rollout gating
  • AI工具网站SEO规划
  • SaaS或产品驱动型SEO审计
  • 搜索意图到页面类型的映射
  • 为工具、对比、替代方案、定价和教程页面创建页面概要
  • 为新的或处于增长期的工具网站确定技术SEO优先级
  • 引用、目录或反向链接规划
  • 程序化SEO评估和上线准入判断

SEO Planning Process

SEO规划流程

mermaid
graph LR
    A[Understand Site and ICP] --> B[Inspect Live SERP]
    B --> C[Choose Page Type]
    C --> D[Define Information Gain]
    D --> E[Check Technical and Trust Signals]
    E --> F[Prioritize and Deliver]
Work through the steps below in order. Skip only when you already have high-confidence answers.
mermaid
graph LR
    A[了解网站和ICP] --> B[检查实时SERP]
    B --> C[选择页面类型]
    C --> D[定义信息增益]
    D --> E[检查技术和信任信号]
    E --> F[优先级排序和交付]
按顺序执行以下步骤，仅当你已拥有高置信度的答案时才可跳过对应步骤。

1. Understand the site and the searcher

1. 了解网站和搜索者

  • Crawl the homepage, pricing page, docs/help center, and one representative tool or feature page.
  • Infer:
    • the core job-to-be-done
    • primary user, buyer, and learner
    • target geography and language
    • primary conversion event
  • Use the 6-field ICP template in framework.md.
  • If the user only provides a URL, infer first and ask follow-up questions only when the missing context would materially change the plan.
  • 爬取首页、定价页、文档/帮助中心，以及一个有代表性的工具或功能页面
  • 推断以下信息：
    • 核心待完成任务
    • 主要用户、购买者和学习者
    • 目标地域和语言
    • 核心转化事件
  • 使用framework.md中的6字段ICP模板
  • 如果用户仅提供了URL，先做推断，仅当缺失的信息会显著改变规划时再询问后续问题

2. Inspect the live SERP before recommending content

2. 推荐内容前先检查实时SERP

  • Do not decide the content format from the keyword alone.
  • Use 
    anycap search --query "<keyword>" --no-crawl --max-results 10
    to classify dominant page types, recurring modules, and SERP mix.
  • Treat search intent as a page-shape constraint, not just a label.
  • If the SERP is mixed, decide whether the keyword deserves one page with a dominant intent or multiple pages.
  • Use page-planning.md for page type mapping and module requirements.
  • 不要仅根据关键词决定内容格式
  • 使用
    anycap search --query "<keyword>" --no-crawl --max-results 10
    来分类主流页面类型、重复出现的模块和SERP构成
  • 将搜索意图视为页面形态的约束条件，而不仅仅是一个标签
  • 如果SERP构成混杂，判断该关键词应该对应一个满足主流意图的页面还是多个页面
  • 参考page-planning.md进行页面类型映射和模块要求确认

3. Evaluate page viability through four lenses

3. 通过四个维度评估页面可行性

  • Review every page or keyword cluster through:
    • Search-Fit Product: Can the user complete the task on the page or move naturally into the product?
    • Information Gain: What first-hand evidence, screenshots, data, tests, workflows, or examples make this page stronger than the current SERP?
    • Technical Readiness: Can search systems crawl, index, render, and understand the page?
    • Trust Distribution: What internal links, external mentions, backlinks, directory placements, or trust blocks support the page?
  • Use "Last-Click" only as a user-satisfaction heuristic. Do not present it as an official Google ranking factor. See guardrails.md.
  • 从以下四个维度审查每个页面或关键词簇：
    • 产品搜索适配度：用户能否在该页面完成任务，或是自然进入产品流程？
    • 信息增益：哪些一手实证、截图、数据、测试、工作流或示例能让这个页面比现有SERP中的页面更优质？
    • 技术就绪度：搜索系统能否爬取、索引、渲染并理解该页面？
    • 信任分布：哪些内链、外部提及、反向链接、目录位置或信任模块能为该页面提供支持？
  • 仅将“最后点击”作为用户满意度的启发式判断标准，不要将其作为谷歌官方排名因素展示，参考guardrails.md

4. Prioritize the plan

4. 对规划做优先级排序

  • Default prioritization:
    1. money pages with clear transactional or commercial intent
    2. comparison, alternatives, and pricing pages
    3. tutorials that support discovery, trust, and internal linking
    4. pSEO only after a small set of hard pages proves quality and indexation
  • Separate:
    • high-confidence rules
    • practitioner heuristics
    • assumptions that still need validation
  • 默认优先级排序：
    1. 有明确交易或商业意图的盈利页面
    2. 对比、替代方案和定价页面
    3. 有利于获客、建立信任和内部链接的教程
    4. 仅当少量核心页面验证了质量和收录效果后再推进pSEO
  • 区分以下内容：
    • 高置信度规则
    • 行业实践启发式判断
    • 仍需验证的假设

5. Deliver concrete outputs

5. 交付具体产出

  • Default deliverables:
    • ICP summary
    • keyword cluster -> intent -> page type table
    • priority page briefs
    • technical baseline checklist
    • citations / backlinks backlog
    • pSEO go / no-go decision with safeguards
    • 30 / 60 / 90 day sequencing
  • 默认交付物：
    • ICP摘要
    • 关键词簇 -> 意图 -> 页面类型对照表
    • 优先级页面概要
    • 技术基线检查清单
    • 引用/反向链接待办清单
    • 带保障措施的pSEO上线/不上线决策
    • 30/60/90天执行节奏规划

Human-in-the-Loop

人在回路机制

This skill benefits from light user input up front, but should otherwise run autonomously.
  • Ask for the site URL, target market, and conversion goal if they are not clear.
  • If the user already gave a concrete site or keyword set, do not over-clarify.
  • Once direction is clear, continue through SERP inspection, planning, and prioritization without repeated interruptions.
本技能前期需要少量用户输入，其余情况下可自主运行。
  • 如果网站URL、目标市场和转化目标不明确，可向用户询问
  • 如果用户已经提供了具体的站点或关键词集合，不要过度追问澄清
  • 一旦方向明确，就继续推进SERP检查、规划和优先级排序，不要反复中断

Core Principles

核心原则

Define the searcher before the keyword. A keyword only makes sense once you know who is searching, why, and what they need to finish.
Inspect the live SERP before choosing a page type. Do not recommend a tutorial, comparison, or tool page until you know what the current SERP rewards.
Treat page type as intent execution. A page is not just content; it is the shape through which the intent gets fulfilled.
Require evidence, not generic prose. Information gain should come from screenshots, examples, data, workflows, benchmarks, or other concrete proof.
Protect quality before scale. Do not recommend pSEO until high-value sample pages have proven useful, indexable, and maintainable.
Separate rules from heuristics. Be explicit about what is a hard constraint versus what is a useful but situational tactic.
先定义搜索者，再定义关键词。只有当你知道谁在搜索、为什么搜索、他们需要完成什么时，关键词才有意义。
选择页面类型前先检查实时SERP。在你知道当前SERP鼓励什么内容之前，不要推荐教程、对比或工具页面。
将页面类型视为意图的落地载体。页面不仅仅是内容，它是满足用户意图的形态。
要求实证，而非通用套话。信息增益应该来自截图、示例、数据、工作流、基准测试或其他具体证据。
规模化前先保障质量。在高价值样本页面被证明有用、可被收录且可维护之前，不要推荐pSEO。
区分规则和启发式判断。明确说明哪些是硬性约束，哪些是有用但需视情况使用的策略。

Quick Reference

快速参考

bash
undefined
bash
undefined

Inspect a target site

检查目标站点

anycap crawl https://example.com
anycap crawl https://example.com

Inspect the SERP shape for a keyword

检查某个关键词的SERP形态

anycap search --query "best ai headshot generator" --no-crawl --max-results 10
anycap search --query "best ai headshot generator" --no-crawl --max-results 10

Ask for a grounded summary when the SERP is unclear

当SERP不明确时获取有依据的总结

anycap search --prompt "What page types dominate the SERP for 'best ai headshot generator' and which content blocks recur?"

Save important search and crawl outputs locally when the task is large or when you expect to revisit evidence.
anycap search --prompt "What page types dominate the SERP for 'best ai headshot generator' and which content blocks recur?"

如果任务规模较大或是你需要后续回溯证据，请将重要的搜索和爬取输出保存在本地。

Guardrails

护栏规则

  • Do not promise rankings.
  • Do not recommend doorway pages, spun pages, or low-value mass AI pages.
  • Do not copy a competitor layout blindly; infer the SERP expectation, then add original evidence.
  • Treat numeric thresholds, directory filters, and DR/DA cutoffs as heuristics rather than fixed rules.
  • Flag compliance risk when recommending paid placements, sponsored links, or directory submissions.
  • When suggesting pSEO, require unique fields, update mechanisms, quality checks, and pruning rules.
  • 不要承诺排名
  • 不要推荐门页、伪原创页面或低价值批量AI生成页面
  • 不要盲目抄袭竞争对手布局；先推断SERP的预期，再补充原创实证
  • 将数值阈值、目录筛选条件和DR/DA cutoff视为启发式判断，而非固定规则
  • 推荐付费投放、赞助链接或目录提交时要标记合规风险
  • 建议使用pSEO时，要求设置唯一字段、更新机制、质量检查和裁剪规则

Resources

资源

  • framework.md -- core model, support levels, and default prioritization
  • page-planning.md -- intent mapping, page modules, and page brief outputs
  • guardrails.md -- quality boundaries, safety checks, and pSEO gating
  • framework.md -- 核心模型、支持级别和默认优先级规则
  • page-planning.md -- 意图映射、页面模块和页面概要输出规范
  • guardrails.md -- 质量边界、安全检查和pSEO准入规则