agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/title-tag/SKILL.md

title-tag

Skill0 starsChanged 3 months agoMITView 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 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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 29
  2. Distinctive:

    Multilingual: Use locale-specific limits.

    line 31
  3. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice and target …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.