affaan-m/ECC/docs/zh-CN/skills/seo/SKILL.md
seo
Use it for seo audit and marketing tasks; the detail page covers purpose, installation, and practical steps.
- Source repository stars
- 234,327
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-07-27
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
通过技术正确性、性能和内容相关性提升搜索可见性,而非依赖花哨手段。
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/seo"Inspect the Agent Skill "seo" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/zh-CN/skills/seo/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
使用场景
审计爬取能力、可索引性、规范标签或重定向时 优化标题标签、元描述和标题结构时 添加或验证结构化数据时 优化核心网页指标时 进行关键词研究并将关键词映射到URL时 规划内部链接或站点地图/robots文件变更时
审计爬取能力、可索引性、规范标签或重定向时优化标题标签、元描述和标题结构时添加或验证结构化数据时 - 02
工作原理
1. 先修复技术障碍,再进行内容优化。 2. 每个页面应有一个明确的主要搜索意图。 3. 优先采用长期质量信号,而非操纵性模式。 4. 移动优先假设至关重要,因为索引基于移动端。 5. 建议应针对具体页面且可执行。
先修复技术障碍,再进行内容优化。每个页面应有一个明确的主要搜索意图。优先采用长期质量信号,而非操纵性模式。 - 03
原则
1. 先修复技术障碍,再进行内容优化。 2. 每个页面应有一个明确的主要搜索意图。 3. 优先采用长期质量信号,而非操纵性模式。 4. 移动优先假设至关重要,因为索引基于移动端。 5. 建议应针对具体页面且可执行。
先修复技术障碍,再进行内容优化。每个页面应有一个明确的主要搜索意图。优先采用长期质量信号,而非操纵性模式。
Permission review
Static risk signals and limitations
Network access
The documentation includes network, browsing, or remote request actions.
"@context": "https://schema.org",Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 66/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 234,327 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/seo/SKILL.md
- Commit
- 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
SEO
通过技术正确性、性能和内容相关性提升搜索可见性,而非依赖花哨手段。
使用场景
在以下情况使用此技能:
- 审计爬取能力、可索引性、规范标签或重定向时
- 优化标题标签、元描述和标题结构时
- 添加或验证结构化数据时
- 优化核心网页指标时
- 进行关键词研究并将关键词映射到URL时
- 规划内部链接或站点地图/robots文件变更时
工作原理
原则
- 先修复技术障碍,再进行内容优化。
- 每个页面应有一个明确的主要搜索意图。
- 优先采用长期质量信号,而非操纵性模式。
- 移动优先假设至关重要,因为索引基于移动端。
- 建议应针对具体页面且可执行。
技术SEO检查清单
爬取能力
robots.txt应允许重要页面并屏蔽低价值内容- 无重要页面被意外设置为
noindex - 重要页面应在浅层点击深度内可达
- 避免超过两次跳转的重定向链
- 规范标签应自洽且无循环
可索引性
- 首选URL格式应保持一致
- 多语言页面需正确使用hreflang(如适用)
- 站点地图应反映预期的公开页面
- 无重复URL在缺乏规范控制的情况下竞争
性能
- LCP < 2.5秒
- INP < 200毫秒
- CLS < 0.1
- 常见修复:预加载首屏资源、减少渲染阻塞工作、预留布局空间、精简重型JS
结构化数据
- 首页:适当时使用组织或企业架构
- 编辑页面:
Article/BlogPosting - 产品页面:
Product和Offer - 内部页面:
BreadcrumbList - 问答部分:仅当内容完全匹配时使用
FAQPage
页面规则
标题标签
- 目标长度约50-60个字符
- 将主要关键词或概念置于靠前位置
- 标题应易于人类阅读,而非为搜索引擎堆砌
元描述
- 目标长度约120-160个字符
- 如实描述页面内容
- 自然包含主要主题
标题结构
- 一个清晰的
H1 H2和H3应反映实际内容层级- 不要仅为视觉样式跳过结构层级
关键词映射
- 定义搜索意图
- 收集实际的关键词变体
- 按意图匹配度、潜在价值和竞争程度排序
- 将主要关键词/主题映射到单个URL
- 检测并避免关键词自相残杀
内部链接
- 从权重高的页面链接到希望排名的页面
- 使用描述性锚文本
- 避免在可能使用更具体锚文本时使用通用锚文本
- 从新页面补充链接到相关现有页面
示例
标题公式
主要主题 - 特定修饰词 | 品牌
元描述公式
行动 + 主题 + 价值主张 + 一个支撑细节
JSON-LD示例
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Page Title Here",
"author": {
"@type": "Person",
"name": "Author Name"
},
"publisher": {
"@type": "Organization",
"name": "Brand Name"
}
}
审计输出格式
[HIGH] 产品页面上的重复标题标签
位置:src/routes/products/[slug].tsx
问题:动态标题会折叠为相同的默认字符串,这会削弱相关性并产生重复信号。
修复:使用产品名称和主要类别为每个产品生成唯一的标题。
反模式
| 反模式 | 修复方法 |
|---|---|
| 关键词堆砌 | 优先为用户写作 |
| 内容单薄的近似重复页面 | 合并或差异化处理 |
| 为不存在的内容添加架构 | 使架构与实际内容匹配 |
| 未检查实际页面就提供内容建议 | 先阅读真实页面 |
| 泛泛的“改进SEO”输出 | 将每条建议与具体页面或资源关联 |
相关技能
seo-specialistfrontend-patternsbrand-voicemarket-research
Alternatives
Compare before choosing
affaan-m/ECC
seo
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.
affaan-m/ECC
seo
Use it for seo audit and marketing tasks; the detail page covers purpose, installation, and practical steps.
coreyhaines31/marketingskills
site-architecture
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page
MoizIbnYousaf/marketing-cli
seo-audit
When the user wants to audit, review, or diagnose SEO issues, plan site architecture, or implement schema markup. Use when someone says 'SEO audit', 'technical SEO', 'site architecture', 'schema markup', 'internal linking', 'why isn't my site ranking', 'site health check', 'crawl issues', 'fix my SEO', 'my traffic dropped', 'rankings fell', or 'site not ranking'. Also trigger when someone wants to plan URL structure, design navigation, add structured data, or review any website for search perfor