skillZs
LIVE SKILL TAGS
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
REAL INSTALL DATA
← back to all skills
kostja94/marketing-skills864 installs

title-tag

When the user wants to optimize the title tag, page title, or SERP title. Also use when the user mentions "title tag," "meta title," "page title," "SEO title," "SERP title," "browser tab title," "title optimization," "headline for search," "title too long," "title tag length," "duplicate title tags," or "optimize title for CTR." For meta description, use meta-description. For structured data, use schema-markup.

How do I install this agent skill?

npx skills add https://github.com/kostja94/marketing-skills --skill title-tag
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a standard SEO optimization guide for title tags and meta titles. It provides character length recommendations for various scripts and best practices for search engine visibility. No malicious patterns or security risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

SEO On-Page: Title Tag

Guides optimization of the HTML title 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)

  • Title tag: Primary search snippet; primary keyword near start; unique per page

Length by Language

Google truncates by pixel width (~580–600px desktop), not character count. Character limits are approximate—CJK chars are wider (~2× Latin), so fewer fit in the same pixels.

Script / LanguageTitle (chars)Notes
Latin (English, Spanish, French, etc.)50–60~55 recommended
CJK (Chinese, Japanese, Korean)25–35Full-width chars; 25–30 desktop; 20–28 mobile; use pixel checker when available
Cyrillic (Russian, etc.)50–55Slightly wider than Latin
Arabic, Hebrew30–40RTL; variable width

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

Multilingual: Use locale-specific limits; don't translate then truncate. 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. Brand: Optional brand append at end

Best Practices

ItemGuideline
LengthPer language (see table above); Google truncates beyond ~600px
Front-loadMain phrase first; branding at end
KeywordInclude primary keyword near the start
UniqueOne unique title per page
ClarityMatch search intent; avoid keyword stuffing
EngagementNumbers, power words, questions can boost CTR ~36%
H1 alignmentH1 should align with title; Google may rewrite titles if they mismatch content or intent

Example: Bad: "SEO Tips for Small Business" → Better: "11 SEO Tips That Actually Work (2026)"

Output Format

  • Recommended title (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. Compare actual CTR vs expected by position; optimize title for pages with CTR gap.

Related Skills

  • google-search-console: CTR analysis, identify low-CTR pages for title optimization
  • meta-description: Meta description pairs with title 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 tag
  • open-graph: og:title for social sharing (often mirrors title)
  • schema-markup: Structured data complements metadata

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/kostja94/marketing-skills/title-tag">View title-tag on skillZs</a>