ClawHub

title-tag

v1.4.0

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

⭐ 0· 85·0 current·0 all-time
byKostja Zhang@kostja94

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for kostja94/title-tag.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "title-tag" (kostja94/title-tag) from ClawHub.
Skill page: https://clawhub.ai/kostja94/title-tag
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install title-tag

ClawHub CLI

Package manager switcher

npx clawhub@latest install title-tag
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (title tag optimization) align with the SKILL.md content. The skill is instruction-only, requires no binaries, env vars, or installs — consistent with a text-guidance SEO helper.
ℹ
Instruction Scope
Instructions are focused on title-tag guidance and best practices. They do instruct the agent to read project context files if present (.claude/project-context.md or .cursor/project-context.md) to gather brand voice and keywords — this is reasonable for SEO work but means the skill will access repository/project files when available. The SKILL.md mentions Google Search Console and pixel checkers but does not include steps that require network credentials or external endpoints.
✓
Install Mechanism
No install spec and no code files; the skill is instruction-only so nothing is written to disk or downloaded. Low install risk.
✓
Credentials
The skill requests no environment variables, secrets, or credentials. There are no disproportionate credential requirements for the stated functionality.
✓
Persistence & Privilege
always is false and the skill does not request system-wide changes or persistent installation. It does not modify other skills or agent configs per the provided metadata.
Assessment
This is an instruction-only SEO helper and appears coherent with its purpose. It may read project context files (.claude/project-context.md or .cursor/project-context.md) if they exist to adapt voice/keywords — review those files for any sensitive content you don't want the agent to access. The skill references Google Search Console for CTR-driven optimizations but does not itself request GSC credentials; only provide external API keys or console access if you explicitly connect a separate GSC integration. Overall this skill is low-risk, but as with any assistant extension, avoid placing secrets in project-context files the skill may read.

Like a lobster shell, security has layers — review code before you run it.

latestvk975de5zame7zph8ad9vx53gt1848wz7
85downloads
0stars
1versions
Updated 3w ago
v1.4.0
MIT-0
Kostja Zhang@kostja94
latest
Download

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

Comments

Loading comments...