skillboardUpdated every 6 hours
skillboardWhen 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.
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.
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.
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:
| 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% |
For pages with low CTR despite good position, use google-search-console to identify opportunities. Optimize meta description for pages with CTR gap.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/description · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/description"
cp -r "skills/seo/on-page/description" ".claude/skills/description"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.