Title tag
Skill ulpi-io/plugin-marketplace/plugins/kostja94/skills/title-tag
A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh
npx -y skills add ulpi-io/plugin-marketplace --skill title-tagAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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."
SKILL.md
3.2 KB, 686 tokens by cl100k_base, as published. Nobody here has run it
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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for brand voice and target keywords.
Identify:
- Page type: Homepage, landing, blog, product, etc.
- Primary keyword: Target search query
- Language / script: Apply length rule above
- Brand: Optional brand append at end
Best Practices
| Item | Guideline |
|---|---|
| Length | Per language (see table above); Google truncates beyond ~600px |
| Keyword | Include primary keyword near the start |
| Unique | One unique title per page |
| Brand | Optional: append brand at end |
| Clear | Compelling; clearly describe page content |
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