SEO On-Page: Meta Description
Guides optimization of the meta description 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.
Scope (On-Page SEO)
- Meta description: CTA; unique value; target keyword; unique per page
Length by Language
Google truncates by pixel width (920px desktop, ~680px mobile), not character count. Character limits are approximate—CJK chars are wider (2× Latin), so fewer fit in the same pixels.
| Script / Language |
Meta description (chars) |
Notes |
| Latin (English, Spanish, French, etc.) |
150–160 |
Desktop ~158; mobile ~120 |
| CJK (Chinese, Japanese, Korean) |
75–100 |
Full-width chars; 70–80 conservative; 90–100 on some locales/fonts; use pixel checker when available |
| Cyrillic (Russian, etc.) |
140–155 |
Slightly wider than Latin |
| Arabic, Hebrew |
70–90 |
RTL; variable width |
Pixel tools: Use a pixel-accurate meta tag checker for CJK—font and locale affect display; character counts vary by source (65–80 to 90–120 in practice).
Multilingual: Use locale-specific limits; localize, don't just translate. See localization-strategy, translation.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice and target keywords.
Identify:
- Page type: Homepage, landing, blog, product, etc.
- Primary keyword: Target search query
- Language / script: Apply length rule above
- CTA: Primary action (sign up, learn more, buy, etc.)
Best Practices
| Item |
Guideline |
| Length |
Per language (see table above); ~150 chars sweet spot for Latin; truncates beyond pixel limit |
| Unique |
One per page; no duplicate descriptions |
| Intent |
Answer "why should I click?"; match search intent |
| CTA |
Include clear call-to-action when relevant |
| Keyword |
Naturally include target keyword |
| Content |
Include author, date, price where relevant |
| Impact |
Does not affect ranking; well-written descriptions improve CTR 5–10% |
Output Format
- Recommended meta description (with character count for target language)
- Alternatives (if A/B testing)
GSC-Driven Optimization
For pages with low CTR despite good position, use google-search-console to identify opportunities. Optimize meta description for pages with CTR gap.
Related Skills
- google-search-console: CTR analysis, identify low-CTR pages for meta optimization
- title-tag: Title pairs with description 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; description summarizes content
- open-graph: og:description for social sharing (often mirrors or extends meta description)
- keyword-research: Keywords in content inform description
1---2name: meta-description3description: When the user wants to optimize the meta description or meta tag description. Also use when the user mentions "meta description," "meta desc," "page description," "SEO description," "search snippet," "SERP description," "description tag," "snippet for search," "meta description length," "rewrite meta description," or "description not showing." For title tag, use title-tag. For hreflang, robots, viewport, use page-metadata.4---5
6# SEO On-Page: Meta Description
7
8Guides optimization of the meta description tag for search engines and SERP display.
9
10**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.
11
12## Scope (On-Page SEO)
13
14- **Meta description**: CTA; unique value; target keyword; unique per page
15
16## Length by Language
17
18Google truncates by **pixel width** (~920px desktop, ~680px mobile), not character count. Character limits are approximate—CJK chars are wider (~2× Latin), so fewer fit in the same pixels.
19
20| Script / Language | Meta description (chars) | Notes |
21|-------------------|--------------------------|-------|
22| **Latin** (English, Spanish, French, etc.) | 150–160 | Desktop ~158; mobile ~120 |
23| **CJK** (Chinese, Japanese, Korean) | 75–100 | Full-width chars; 70–80 conservative; 90–100 on some locales/fonts; use pixel checker when available |
24| **Cyrillic** (Russian, etc.) | 140–155 | Slightly wider than Latin |
25| **Arabic, Hebrew** | 70–90 | RTL; variable width |
26
27**Pixel tools**: Use a pixel-accurate meta tag checker for CJK—font and locale affect display; character counts vary by source (65–80 to 90–120 in practice).
28
29**Multilingual**: Use locale-specific limits; localize, don't just translate. See **localization-strategy**, **translation**.
30
31## Initial Assessment
32
33**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice and target keywords.
34
35Identify:
361. **Page type**: Homepage, landing, blog, product, etc.
372. **Primary keyword**: Target search query
383. **Language / script**: Apply length rule above
394. **CTA**: Primary action (sign up, learn more, buy, etc.)
40
41## Best Practices
42
43| Item | Guideline |
44|------|-----------|
45| **Length** | Per language (see table above); ~150 chars sweet spot for Latin; truncates beyond pixel limit |
46| **Unique** | One per page; no duplicate descriptions |
47| **Intent** | Answer "why should I click?"; match search intent |
48| **CTA** | Include clear call-to-action when relevant |
49| **Keyword** | Naturally include target keyword |
50| **Content** | Include author, date, price where relevant |
51| **Impact** | Does not affect ranking; well-written descriptions improve CTR 5–10% |
52
53## Output Format
54
55- **Recommended meta description** (with character count for target language)
56- **Alternatives** (if A/B testing)
57
58## GSC-Driven Optimization
59
60For pages with low CTR despite good position, use google-search-console to identify opportunities. Optimize meta description for pages with CTR gap.
61
62## Related Skills
63
64- **google-search-console**: CTR analysis, identify low-CTR pages for meta optimization
65- **title-tag**: Title pairs with description in SERP
66- **localization-strategy, translation**: Multilingual metadata; locale-specific length
67- **serp-features**: SERP features; standard result appearance in context
68- **heading-structure**: H1 should align with title; description summarizes content
69- **open-graph**: og:description for social sharing (often mirrors or extends meta description)
70- **keyword-research**: Keywords in content inform description
kostja94