agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/meta-description/SKILL.md

meta-description

Skill0 starsChanged 3 months agoMITView 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 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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Pixel tools: Use a pixel-accurate meta tag checker for CJK—font and locale affect display.

    line 29
  2. Distinctive:

    Multilingual: Use locale-specific limits.

    line 31
  3. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice and target …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 / LanguageMeta description (chars)Notes
Latin (English, Spanish, French, etc.)150–160Desktop ~158; mobile ~120
CJK (Chinese, Japanese, Korean)75–100Full-width chars; 70–80 conservative; 90–100 on some locales/fonts; use pixel checker when available
Cyrillic (Russian, etc.)140–155Slightly wider than Latin
Arabic, Hebrew70–90RTL; 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

ItemGuideline
LengthPer language (see table above); ~150 chars sweet spot for Latin; truncates beyond pixel limit
UniqueOne per page; no duplicate descriptions
IntentAnswer "why should I click?"; match search intent
CTAInclude clear call-to-action when relevant
KeywordNaturally include target keyword
ContentInclude author, date, price where relevant
ImpactDoes 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.