title-tag

$npx mdskill add kostja94/marketing-skills/title-tag

Optimizes HTML title tags for better search engine visibility and user experience

  • Identifies optimal title tag length based on language and platform characteristics.
  • Uses natural language processing to understand user intent related to title optimization.
  • Decides the best practices for title tag structure, including keyword placement and uniqueness per page.
  • Delivers optimized title tags directly into the HTML code or suggests them for manual implementation.

SKILL.md

.github/skills/title-tagView on GitHub ↗
---
name: title-tag
description: 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.
metadata:
  version: 1.4.0
---

# 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 / Language | Title (chars) | Notes |
|-------------------|---------------|-------|
| **Latin** (English, Spanish, French, etc.) | 50–60 | ~55 recommended |
| **CJK** (Chinese, Japanese, Korean) | 25–35 | Full-width chars; 25–30 desktop; 20–28 mobile; use pixel checker when available |
| **Cyrillic** (Russian, etc.) | 50–55 | Slightly wider than Latin |
| **Arabic, Hebrew** | 30–40 | RTL; 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

| Item | Guideline |
|------|-----------|
| **Length** | Per language (see table above); Google truncates beyond ~600px |
| **Front-load** | Main phrase first; branding at end |
| **Keyword** | Include primary keyword near the start |
| **Unique** | One unique title per page |
| **Clarity** | Match search intent; avoid keyword stuffing |
| **Engagement** | Numbers, power words, questions can boost CTR ~36% |
| **H1 alignment** | H1 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen 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.
about-page-generatorWhen 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.
affiliate-marketingWhen 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.
affiliate-page-generatorWhen 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.
ai-traffic-trackingWhen 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.
alternatives-page-generatorWhen 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.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.