Title tag skill

When the user wants to optimize the title tag, page title, or SERP title.

by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗

Use now

Files of Title tag

kostja94/main1 file shown
SKILL.md
Show the full text75 lines

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

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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.

  • 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
1---
2name: title-tag
3description: 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.
4metadata:
5 version: 1.4.0
6---
7 
8# SEO On-Page: Title Tag
9 
10Guides optimization of the HTML title tag for search engines and SERP display.
11 
12**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.
13 
14## Scope (On-Page SEO)
15 
16- **Title tag**: Primary search snippet; primary keyword near start; unique per page
17 
18## Length by Language
19 
20Google 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.
21 
22| Script / Language | Title (chars) | Notes |
23|-------------------|---------------|-------|
24| **Latin** (English, Spanish, French, etc.) | 50–60 | ~55 recommended |
25| **CJK** (Chinese, Japanese, Korean) | 25–35 | Full-width chars; 25–30 desktop; 20–28 mobile; use pixel checker when available |
26| **Cyrillic** (Russian, etc.) | 50–55 | Slightly wider than Latin |
27| **Arabic, Hebrew** | 30–40 | RTL; variable width |
28 
29**Pixel tools**: Use a pixel-accurate checker for CJK—font and locale affect display.
30 
31**Multilingual**: Use locale-specific limits; don't translate then truncate. See **localization-strategy**, **translation**.
32 
33## Initial Assessment
34 
35**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
36 
37Identify:
381. **Page type**: Homepage, landing, blog, product, etc.
392. **Primary keyword**: Target search query
403. **Language / script**: Apply length rule above
414. **Brand**: Optional brand append at end
42 
43## Best Practices
44 
45| Item | Guideline |
46|------|-----------|
47| **Length** | Per language (see table above); Google truncates beyond ~600px |
48| **Front-load** | Main phrase first; branding at end |
49| **Keyword** | Include primary keyword near the start |
50| **Unique** | One unique title per page |
51| **Clarity** | Match search intent; avoid keyword stuffing |
52| **Engagement** | Numbers, power words, questions can boost CTR ~36% |
53| **H1 alignment** | H1 should align with title; Google may rewrite titles if they mismatch content or intent |
54 
55**Example**: Bad: "SEO Tips for Small Business" → Better: "11 SEO Tips That Actually Work (2026)"
56 
57## Output Format
58 
59- **Recommended title** (with character count for target language)
60- **Alternatives** (if A/B testing)
61 
62## GSC-Driven Optimization
63 
64For 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.
65 
66## Related Skills
67 
68- **google-search-console**: CTR analysis, identify low-CTR pages for title optimization
69- **meta-description**: Meta description pairs with title in SERP
70- **localization-strategy, translation**: Multilingual metadata; locale-specific length
71- **serp-features**: SERP features; standard result appearance in context
72- **heading-structure**: H1 should align with title tag
73- **open-graph**: og:title for social sharing (often mirrors title)
74- **schema-markup**: Structured data complements metadata
75 

Discussion

Alternatives

Agentic Browsing ReadinessAudit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).Marketing · MITBacklink Profile AnalysisBacklink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.Marketing · MIT/setup-cmsConnect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report. · MITBacklink checkBacklink profile for any domain — referring domains, authority, anchors, new/lost links, and a side-by-side vs a competitor. Use when asked "check my backlinks", "backlink profile of X", "who links to them", or "link gap vs competitor".Marketing · MIT