Claude Skill

title-tag

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," "d

LLM Mart · 0 points · 4 views 0 listing impressions 0 install-command copies
Download kostja94-marketing-skills-skills_seo_on-page_title-8dd89c5.zip · 1 KB

Install

skills CLI npx skills add https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/title
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install kostja94-marketing-skills@llmmart
Git git clone https://github.com/kostja94/marketing-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole kostja94/marketing-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

SEO On-Page: Title Tag

Owns writing and review rules for the HTML <title> element. page-metadata owns discovery, implementation, and release verification.

Inputs

Read root contextus.md when present. Confirm page type, unique page job, primary search intent, locale, current title and H1, verified differentiators, sibling-page titles, and whether a template automatically appends the brand.

Rules

  • Write a descriptive, concise, page-specific title that accurately represents the page.
  • Put the primary search concept early when natural; do not keyword-stuff.
  • Treat about 60 Latin characters for the title body as a default warning, not a hard limit. Pixel width, script, device, and query context affect display.
  • A delimiter plus brand suffix such as | Brand is outside that title-body target. It may be truncated or rewritten; include it only when useful and never duplicate a template suffix.
  • For CJK, RTL, or other scripts, review rendered width and natural language instead of applying a translated character formula.
  • Title and H1 must serve the same page intent and promise, but need not use identical wording. Example: title AI Image Generator; H1 Generate Images with AI.
  • Include only claims supported by the page. Do not add a year, number, superlative, or feature merely for click appeal.
  • Apply the Swap Test: if the title fits a sibling page unchanged, add a verified page-specific fact or sharpen its task.
  • Google may generate a different title link from the <title>, main visual title, headings, prominent text, anchors, og:title, or other signals. Optimize consistency of page identity, not control of the exact displayed string.

Cannibalization

When multiple URLs target the same primary intent, report the affected URLs, overlap, and evidence. Do not merge pages, reassign keywords, change page roles, or alter information architecture.

Output

  • Recommended title, with the title body and optional brand suffix shown separately.
  • A length or width warning when relevant, never a mechanical pass/fail.
  • Brief rationale tied to intent and unique page facts.
  • H1 semantic-alignment result; actual H1 edits route to heading-structure.
  • Cannibalization warning when applicable.

Primary reference

Related Skills

  • page-metadata, meta-description, heading-structure
  • localization-strategy, translation, google-search-console
Files (marketing-skills)
  • SKILL.md 2.8 KB
    ---
    name: title-tag
    description: When the user wants to write, audit, or optimize an HTML title tag, SEO title, page title, SERP title, browser-tab title, duplicate title, or title rewrite issue. For a sitewide metadata lifecycle including implementation and production validation, use page-metadata.
    metadata:
      version: 2.0.0
    ---
    
    # SEO On-Page: Title Tag
    
    Owns writing and review rules for the HTML `<title>` element. **page-metadata** owns discovery, implementation, and release verification.
    
    ## Inputs
    
    Read root `contextus.md` when present. Confirm page type, unique page job, primary search intent, locale, current title and H1, verified differentiators, sibling-page titles, and whether a template automatically appends the brand.
    
    ## Rules
    
    - Write a descriptive, concise, page-specific title that accurately represents the page.
    - Put the primary search concept early when natural; do not keyword-stuff.
    - Treat about 60 Latin characters for the title body as a default warning, not a hard limit. Pixel width, script, device, and query context affect display.
    - A delimiter plus brand suffix such as `| Brand` is outside that title-body target. It may be truncated or rewritten; include it only when useful and never duplicate a template suffix.
    - For CJK, RTL, or other scripts, review rendered width and natural language instead of applying a translated character formula.
    - Title and H1 must serve the same page intent and promise, but need not use identical wording. Example: title `AI Image Generator`; H1 `Generate Images with AI`.
    - Include only claims supported by the page. Do not add a year, number, superlative, or feature merely for click appeal.
    - Apply the **Swap Test**: if the title fits a sibling page unchanged, add a verified page-specific fact or sharpen its task.
    - Google may generate a different title link from the `<title>`, main visual title, headings, prominent text, anchors, `og:title`, or other signals. Optimize consistency of page identity, not control of the exact displayed string.
    
    ## Cannibalization
    
    When multiple URLs target the same primary intent, report the affected URLs, overlap, and evidence. Do not merge pages, reassign keywords, change page roles, or alter information architecture.
    
    ## Output
    
    - Recommended title, with the title body and optional brand suffix shown separately.
    - A length or width warning when relevant, never a mechanical pass/fail.
    - Brief rationale tied to intent and unique page facts.
    - H1 semantic-alignment result; actual H1 edits route to **heading-structure**.
    - Cannibalization warning when applicable.
    
    ## Primary reference
    
    - [Google: influencing title links](https://developers.google.com/search/docs/appearance/title-link)
    
    ## Related Skills
    
    - **page-metadata**, **meta-description**, **heading-structure**
    - **localization-strategy**, **translation**, **google-search-console**
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.