meta-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.
Best use case
meta-description is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using meta-description should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/description/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How meta-description Compares
| Feature / Agent | meta-description | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: 1. **Page type**: Homepage, landing, blog, product, etc. 2. **Primary keyword**: Target search query 3. **Language / script**: Apply length rule above 4. **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
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
meta-ads
When the user wants to set up, optimize, or manage Meta (Facebook/Instagram) Ads. Also use when the user mentions "Meta Ads," "Facebook Ads," "Instagram Ads," "Meta Pixel," "Conversions API," "Advantage+," "lookalike audience," or "Meta retargeting." For landing pages, use landing-page-generator.
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
growth-funnel
When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.