title-tag
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO On-Page: Title Tag
站内SEO:Title Tag
Guides optimization of the HTML title tag for search engines and SERP display.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
指导针对搜索引擎和SERP展示的HTML title tag优化。
调用规则:首次使用时,如果适用,可以先用1-2句话介绍该技能的覆盖范围和重要性,再提供核心输出。后续调用或用户要求跳过介绍时,直接输出核心内容即可。
Scope (On-Page SEO)
适用范围(站内SEO)
- Title tag: Primary search snippet; primary keyword near start; unique per page
- Title tag:搜索结果片段的核心元素;主关键词尽量靠前;每个页面唯一
Length by Language
不同语言的长度要求
Google truncates by pixel width (~580–600px desktop), not character count. Character limits are approximate—CJK chars are wider (~2× Latin), so fewer fit in the same pixels.
| Script / Language | Title (chars) | Notes |
|---|---|---|
| Latin (English, Spanish, French, etc.) | 50–60 | ~55 recommended |
| CJK (Chinese, Japanese, Korean) | 25–35 | Full-width chars; 25–30 desktop; 20–28 mobile; use pixel checker when available |
| Cyrillic (Russian, etc.) | 50–55 | Slightly wider than Latin |
| Arabic, Hebrew | 30–40 | RTL; variable width |
Pixel tools: Use a pixel-accurate checker for CJK—font and locale affect display.
Multilingual: Use locale-specific limits; don't translate then truncate. See localization-strategy, translation.
Google 按照像素宽度(桌面端约580–600px)截断标题,而非字符数。字符限制为近似值——CJK字符宽度约为拉丁字符的2倍,因此相同像素下可容纳的字符数更少。
| 书写系统/语言 | 标题长度(字符数) | 备注 |
|---|---|---|
| 拉丁字符(英语、西班牙语、法语等) | 50–60 | 推荐约55个字符 |
| CJK(中文、日文、韩文) | 25–35 | 全角字符;桌面端25–30个;移动端20–28个;如有可能请使用像素检测工具 |
| 西里尔字符(俄语等) | 50–55 | 宽度略大于拉丁字符 |
| 阿拉伯语、希伯来语 | 30–40 | 从右到左书写;宽度不固定 |
像素工具:针对CJK字符请使用像素级精准的检测工具,字体和地区会影响展示效果。
多语言场景:使用对应地区的长度限制;不要先翻译再截断。参考 localization-strategy、translation。
Initial Assessment
初始评估
Check for product marketing context first: If or exists, read it for brand voice and target keywords.
.claude/product-marketing-context.md.cursor/product-marketing-context.mdIdentify:
- Page type: Homepage, landing, blog, product, etc.
- Primary keyword: Target search query
- Language / script: Apply length rule above
- Brand: Optional brand append at end
首先确认产品营销上下文:如果存在或文件,请先读取文件内容,明确品牌调性和目标关键词。
.claude/product-marketing-context.md.cursor/product-marketing-context.md识别以下要素:
- 页面类型:首页、落地页、博客、产品页等
- 主关键词:目标搜索查询词
- 语言/书写系统:应用上文的长度规则
- 品牌:可选择在标题末尾附加品牌名
Best Practices
最佳实践
| Item | Guideline |
|---|---|
| Length | Per language (see table above); Google truncates beyond ~600px |
| Keyword | Include primary keyword near the start |
| Unique | One unique title per page |
| Brand | Optional: append brand at end |
| Clear | Compelling; clearly describe page content |
| 项 | 规范 |
|---|---|
| 长度 | 符合对应语言要求(见上表);超过约600px会被Google截断 |
| 关键词 | 主关键词尽量放在开头 |
| 唯一性 | 每个页面对应唯一的标题 |
| 品牌 | 可选:末尾附加品牌名 |
| 清晰度 | 有吸引力;清晰描述页面内容 |
Output Format
输出格式
- Recommended title (with character count for target language)
- Alternatives (if A/B testing)
- 推荐标题(附带目标语言对应的字符数统计)
- 备选标题(如需A/B测试)
GSC-Driven Optimization
基于GSC的优化
For pages with low CTR despite good position, use google-search-console to identify opportunities. Compare actual CTR vs expected by position; optimize title for pages with CTR gap.
对于排名良好但CTR较低的页面,可以使用google-search-console寻找优化机会。对比实际CTR和对应排名的预期CTR,针对存在CTR差距的页面优化标题。
Related Skills
相关技能
- google-search-console: CTR analysis, identify low-CTR pages for title optimization
- meta-description: Meta description pairs with title in SERP
- localization-strategy, translation: Multilingual metadata; locale-specific length
- serp-features: SERP features; standard result appearance in context
- heading-structure: H1 should align with title tag
- open-graph: og:title for social sharing (often mirrors title)
- schema-markup: Structured data complements metadata
- google-search-console:CTR分析,识别CTR偏低的页面以便进行标题优化
- meta-description:SERP中meta description与标题配对展示
- localization-strategy, translation:多语言元数据;对应地区的长度要求
- serp-features:SERP特性;标准搜索结果的上下文展示效果
- heading-structure:H1标签应与title tag保持一致
- open-graph:用于社交分享的og:title(通常与title tag一致)
- schema-markup:结构化数据可补充元数据效果