seo
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO
SEO
Improve search visibility through technical correctness, performance, and content relevance, not gimmicks.
通过技术正确性、性能和内容相关性提升搜索可见度,而非投机取巧。
When to Use
何时使用
Use this skill when:
- auditing crawlability, indexability, canonicals, or redirects
- improving title tags, meta descriptions, and heading structure
- adding or validating structured data
- improving Core Web Vitals
- doing keyword research and mapping keywords to URLs
- planning internal linking or sitemap / robots changes
在以下场景使用该技能:
- 审计可抓取性、可索引性、规范标签或重定向
- 优化标题标签、元描述和标题结构
- 添加或验证结构化数据
- 优化Core Web Vitals
- 开展关键词研究并将关键词映射到对应URL
- 规划内链或站点地图/robots调整
How It Works
工作原理
Principles
原则
- Fix technical blockers before content optimization.
- One page should have one clear primary search intent.
- Prefer long-term quality signals over manipulative patterns.
- Mobile-first assumptions matter because indexing is mobile-first.
- Recommendations should be page-specific and implementable.
- 内容优化前先修复技术阻碍。
- 单个页面应具备一个清晰的核心搜索意图。
- 优先打造长期质量信号,而非投机作弊手段。
- 遵循移动优先假设,因为索引是移动优先的。
- 建议需针对具体页面且可落地执行。
Technical SEO checklist
技术SEO检查清单
Crawlability
可抓取性
- should allow important pages and block low-value surfaces
robots.txt - no important page should be unintentionally
noindex - important pages should be reachable within a shallow click depth
- avoid redirect chains longer than two hops
- canonical tags should be self-consistent and non-looping
- 应允许重要页面抓取,屏蔽低价值页面
robots.txt - 重要页面不得被意外设置为
noindex - 重要页面应可以通过较浅的点击深度访问
- 避免超过两次跳转的重定向链
- 规范标签应自洽且无循环
Indexability
可索引性
- preferred URL format should be consistent
- multilingual pages need correct hreflang if used
- sitemaps should reflect the intended public surface
- no duplicate URLs should compete without canonical control
- 首选URL格式应保持一致
- 多语言页面如需使用hreflang则需配置正确
- 站点地图应匹配预期对外展示的页面范围
- 无规范标签控制的情况下,不得有重复URL相互竞争
Performance
性能
- LCP < 2.5s
- INP < 200ms
- CLS < 0.1
- common fixes: preload hero assets, reduce render-blocking work, reserve layout space, trim heavy JS
- LCP < 2.5s
- INP < 200ms
- CLS < 0.1
- 通用修复方案:预加载核心资源、减少阻塞渲染的任务、预留布局空间、精简冗余JS
Structured data
结构化数据
- homepage: organization or business schema where appropriate
- editorial pages: /
ArticleBlogPosting - product pages: and
ProductOffer - interior pages:
BreadcrumbList - Q&A sections: only when the content truly matches
FAQPage
- 首页:酌情使用组织或企业schema
- 编辑类页面:/
ArticleBlogPosting - 产品页:和
ProductOffer - 内页:
BreadcrumbList - 问答板块:仅当内容完全匹配时使用
FAQPage
On-page rules
页面内规则
Title tags
标题标签
- aim for roughly 50-60 characters
- put the primary keyword or concept near the front
- make the title legible to humans, not stuffed for bots
- 长度尽量控制在50-60字符左右
- 将核心关键词或概念放在靠前位置
- 标题对人类可读,不要为了机器人堆砌关键词
Meta descriptions
元描述
- aim for roughly 120-160 characters
- describe the page honestly
- include the main topic naturally
- 长度尽量控制在120-160字符左右
- 如实描述页面内容
- 自然融入核心主题
Heading structure
标题结构
- one clear
H1 - and
H2should reflect actual content hierarchyH3 - do not skip structure just for visual styling
- 一个清晰的
H1 - 和
H2应反映实际的内容层级H3 - 不要为了视觉样式跳过层级结构
Keyword mapping
关键词映射
- define the search intent
- gather realistic keyword variants
- prioritize by intent match, likely value, and competition
- map one primary keyword/theme to one URL
- detect and avoid cannibalization
- 定义搜索意图
- 收集符合实际的关键词变体
- 按意图匹配度、预期价值和竞争度排序
- 为单个URL映射一个核心关键词/主题
- 检测并避免内容冲突
Internal linking
内链
- link from strong pages to pages you want to rank
- use descriptive anchor text
- avoid generic anchors when a more specific one is possible
- backfill links from new pages to relevant existing ones
- 从权重高的页面链接到你想要提升排名的页面
- 使用描述性锚文本
- 有更具体的锚文本可用时避免使用通用锚文本
- 从新页面添加指向相关旧页面的反向链接
Examples
示例
Title formula
标题公式
text
Primary Topic - Specific Modifier | Brandtext
Primary Topic - Specific Modifier | BrandMeta description formula
元描述公式
text
Action + topic + value proposition + one supporting detailtext
Action + topic + value proposition + one supporting detailJSON-LD example
JSON-LD示例
json
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Page Title Here",
"author": {
"@type": "Person",
"name": "Author Name"
},
"publisher": {
"@type": "Organization",
"name": "Brand Name"
}
}json
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Page Title Here",
"author": {
"@type": "Person",
"name": "Author Name"
},
"publisher": {
"@type": "Organization",
"name": "Brand Name"
}
}Audit output shape
审计输出格式
text
[HIGH] Duplicate title tags on product pages
Location: src/routes/products/[slug].tsx
Issue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.
Fix: Generate a unique title per product using the product name and primary category.text
[HIGH] Duplicate title tags on product pages
Location: src/routes/products/[slug].tsx
Issue: Dynamic titles collapse to the same default string, which weakens relevance and creates duplicate signals.
Fix: Generate a unique title per product using the product name and primary category.Anti-Patterns
反模式
| Anti-pattern | Fix |
|---|---|
| keyword stuffing | write for users first |
| thin near-duplicate pages | consolidate or differentiate them |
| schema for content that is not actually present | match schema to reality |
| content advice without checking the actual page | read the real page first |
| generic “improve SEO” outputs | tie every recommendation to a page or asset |
| 反模式 | 修复方案 |
|---|---|
| 关键词堆砌 | 优先为用户写作 |
| 薄价值近似重复页面 | 合并或差异化处理 |
| 为实际不存在的内容添加schema | schema与实际内容保持一致 |
| 未检查实际页面就给出内容建议 | 先阅读真实页面内容 |
| 通用的“提升SEO”输出 | 每条建议都关联到具体页面或资源 |
Related Skills
相关技能
seo-specialistfrontend-patternsbrand-voicemarket-research
seo-specialistfrontend-patternsbrand-voicemarket-research