SEO Title Tag Optimizer

Title tag

by kostja94 · MIT license · ★ 1,006 on GitHub

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…

---
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

Overview

Guides optimization of the HTML title tag for search engines and SERP display.

What you get

Recommended title(with character count for target language)
Alternatives(if A/B testing)

Manual install (npx, ZIP)

Claude Codenpx skills add kostja94/marketing-skills --skill title-tag -g -a claude-code

Claude Code (degit)npx degit kostja94/marketing-skills/skills/seo/on-page/title#main ~/.claude/skills/title-tag

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.7 KB

Read SKILL.md here

kostja94/main1 file shown

SKILL.md3.7 KB

Browse every file on GitHub↗

SKILL.md

Show the full text75 lines

title-tag/SKILL.md75 lines · 3.7 KB

PreviewCode

Outline

RawView on GitHub

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:

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
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	---
2	name: title-tag
3	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.
4	metadata:
5	version: 1.4.0
6	---
7
8	# SEO On-Page: Title Tag
9
10	Guides 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
20	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.
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
37	Identify:
38	1. Page type: Homepage, landing, blog, product, etc.
39	2. Primary keyword: Target search query
40	3. Language / script: Apply length rule above
41	4. 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
64	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.
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