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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.