Best fit
- 审计、规划并实施SEO改进,涵盖技术SEO、页面优化、结构化数据、核心网页指标和内容策略。当用户希望提升搜索可见性、进行SEO修复、使用架构标记、处理站点地图/robots文件或进行关键词映射时使用。
affaan-m/ECC
审计、规划并实施SEO改进,涵盖技术SEO、页面优化、结构化数据、核心网页指标和内容策略。当用户希望提升搜索可见性、进行SEO修复、使用架构标记、处理站点地图/robots文件或进行关键词映射时使用。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/seo"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
According to the pinned SKILL.md from affaan-m/ECC: 通过技术正确性、性能和内容相关性提升搜索可见性,而非依赖花哨手段。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/seo"Best fit
Bring this context
Expected outputs
Key source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
审计爬取能力、可索引性、规范标签或重定向时 优化标题标签、元描述和标题结构时 添加或验证结构化数据时 优化核心网页指标时 进行关键词研究并将关键词映射到URL时 规划内部链接或站点地图/robots文件变更时
1. 先修复技术障碍,再进行内容优化。 2. 每个页面应有一个明确的主要搜索意图。 3. 优先采用长期质量信号,而非操纵性模式。 4. 移动优先假设至关重要,因为索引基于移动端。 5. 建议应针对具体页面且可执行。
1. 先修复技术障碍,再进行内容优化。 2. 每个页面应有一个明确的主要搜索意图。 3. 优先采用长期质量信号,而非操纵性模式。 4. 移动优先假设至关重要,因为索引基于移动端。 5. 建议应针对具体页面且可执行。
robots.txt 应允许重要页面并屏蔽低价值内容 无重要页面被意外设置为 noindex 重要页面应在浅层点击深度内可达 避免超过两次跳转的重定向链 规范标签应自洽且无循环
robots.txt 应允许重要页面并屏蔽低价值内容 无重要页面被意外设置为 noindex 重要页面应在浅层点击深度内可达 避免超过两次跳转的重定向链 规范标签应自洽且无循环
SkillSignal prompt templates
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use seo to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned seo source to [task]. Pay particular attention to these source sections: “使用场景”, “工作原理”, “原则”, “技术SEO检查清单”, “爬取能力”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current seo result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
The task matches the purpose documented in the SKILL.md.
The source section “使用场景” has been checked.
The source section “工作原理” has been checked.
The source section “原则” has been checked.
The source section “技术SEO检查清单” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
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.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailテクニカル SEO、オンページ最適化、構造化データ、Core Web Vitals、およびコンテンツ戦略にわたる SEO 改善の監査、計画、実施。ユーザーが検索可視性の向上、SEO 修正、スキーママークアップ、サイトマップ/robots の作業、またはキーワードマッピングを希望する場合に使用します。
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailWhen 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
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
通过技术正确性、性能和内容相关性提升搜索可见性,而非依赖花哨手段。
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/seo". Inspect the command and pinned source before running it.
No dedicated Agent platform is declared in the pinned source record.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
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.
テクニカル SEO、オンページ最適化、構造化データ、Core Web Vitals、およびコンテンツ戦略にわたる SEO 改善の監査、計画、実施。ユーザーが検索可視性の向上、SEO 修正、スキーママークアップ、サイトマップ/robots の作業、またはキーワードマッピングを希望する場合に使用します。
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
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
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear ab
通过技术正确性、性能和内容相关性提升搜索可见性,而非依赖花哨手段。
在以下情况使用此技能:
robots.txt 应允许重要页面并屏蔽低价值内容noindexArticle / BlogPostingProduct 和 OfferBreadcrumbListFAQPageH1H2 和 H3 应反映实际内容层级主要主题 - 特定修饰词 | 品牌
行动 + 主题 + 价值主张 + 一个支撑细节
{
"@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