title-tag
Guides optimization of the HTML title tag for search engines and SERP display.
Works with
0
total installs
0
this week
309
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
309
stars
Installation Guide
How to use title-tag on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
title-tag
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches title-tag from kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate title-tag. Access via /title-tag in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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
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:
- 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.
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
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
google-search-console
40kostja94/marketing-skills
grill-me
340mattpocock/skills
premortem
193parcadei/continuous-claude-v3
deslop
111cursor/plugins
framer-motion
89pproenca/dot-skills
write-a-prd
85mattpocock/skills
Reviews
- SShikha Mishra★★★★★Dec 24, 2024
title-tag reduced setup friction for our internal harness; good balance of opinion and flexibility.
- AAmelia Sharma★★★★★Dec 20, 2024
Useful defaults in title-tag — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- MMaya Jain★★★★★Dec 8, 2024
title-tag reduced setup friction for our internal harness; good balance of opinion and flexibility.
- MMaya Liu★★★★★Dec 8, 2024
title-tag is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAanya Thompson★★★★★Dec 8, 2024
title-tag reduced setup friction for our internal harness; good balance of opinion and flexibility.
- IIsabella Chen★★★★★Dec 4, 2024
Registry listing for title-tag matched our evaluation — installs cleanly and behaves as described in the markdown.
- MMaya Zhang★★★★★Nov 27, 2024
I recommend title-tag for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- NNia Malhotra★★★★★Nov 27, 2024
I recommend title-tag for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- IIsabella Thompson★★★★★Nov 23, 2024
Useful defaults in title-tag — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- RRahul Santra★★★★★Nov 15, 2024
I recommend title-tag for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 63
Discussion
Comments — not star reviews- No comments yet — start the thread.