Meta Description Optimizer

Meta description

by kostja94 · MIT license · ★ 1,006 on GitHub

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…

---
name: meta-description
description: 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.
metadata:
  version: 1.4.0
---

# 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

Overview

Guides optimization of the meta description tag for search engines and SERP display.

What you get

Recommended meta description(with character count for target language)
Alternatives(if A/B testing)

Manual install (npx, ZIP)

Claude Codenpx skills add kostja94/marketing-skills --skill meta-description -g -a claude-code

Claude Code (degit)npx degit kostja94/marketing-skills/skills/seo/on-page/description#main ~/.claude/skills/meta-description

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.8 KB

Read SKILL.md here

kostja94/main1 file shown

SKILL.md3.8 KB

Browse every file on GitHub↗

SKILL.md

Show the full text73 lines

meta-description/SKILL.md73 lines · 3.8 KB

PreviewCode

Outline

RawView on GitHub

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

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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.

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	---
2	name: meta-description
3	description: 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	metadata:
5	version: 1.4.0
6	---
7
8	# SEO On-Page: Meta Description
9
10	Guides optimization of the meta description tag for search engines and SERP display.
11
12	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.
13
14	## Scope (On-Page SEO)
15
16	- Meta description: CTA; unique value; target keyword; unique per page
17
18	## Length by Language
19
20	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.
21
22	\| Script / Language \| Meta description (chars) \| Notes \|
23	\|-------------------\|--------------------------\|-------\|
24	\| Latin (English, Spanish, French, etc.) \| 150–160 \| Desktop ~158; mobile ~120 \|
25	\| CJK (Chinese, Japanese, Korean) \| 75–100 \| Full-width chars; 70–80 conservative; 90–100 on some locales/fonts; use pixel checker when available \|
26	\| Cyrillic (Russian, etc.) \| 140–155 \| Slightly wider than Latin \|
27	\| Arabic, Hebrew \| 70–90 \| RTL; variable width \|
28
29	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).
30
31	Multilingual: Use locale-specific limits; localize, don't just translate. See localization-strategy, translation.
32
33	## Initial Assessment
34
35	Project context: Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
36
37	Identify:
38	1. Page type: Homepage, landing, blog, product, etc.
39	2. Primary keyword: Target search query
40	3. Language / script: Apply length rule above
41	4. CTA: Primary action (sign up, learn more, buy, etc.)
42
43	## Best Practices
44
45	\| Item \| Guideline \|
46	\|------\|-----------\|
47	\| Length \| Per language (see table above); ~150 chars sweet spot for Latin; truncates beyond pixel limit \|
48	\| Unique \| One per page; no duplicate descriptions \|
49	\| Intent \| Answer "why should I click?"; match search intent \|
50	\| CTA \| Include clear call-to-action when relevant \|
51	\| Keyword \| Naturally include target keyword \|
52	\| Content \| Include author, date, price where relevant \|
53	\| Impact \| Does not affect ranking; well-written descriptions improve CTR 5–10% \|
54
55	## Output Format
56
57	- Recommended meta description (with character count for target language)
58	- Alternatives (if A/B testing)
59
60	## GSC-Driven Optimization
61
62	For pages with low CTR despite good position, use google-search-console to identify opportunities. Optimize meta description for pages with CTR gap.
63
64	## Related Skills
65
66	- google-search-console: CTR analysis, identify low-CTR pages for meta optimization
67	- title-tag: Title pairs with description in SERP
68	- localization-strategy, translation: Multilingual metadata; locale-specific length
69	- serp-features: SERP features; standard result appearance in context
70	- heading-structure: H1 should align with title; description summarizes content
71	- open-graph: og:description for social sharing (often mirrors or extends meta description)
72	- keyword-research: Keywords in content inform description
73