メニュー
Optimize title tags, meta descriptions, Open Graph, Twitter cards for maximum CTR with A/B variations. 标题优化/元描述/CTR
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rome-os/rome-apps --skill meta-tags-optimizerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use for creative/product/design work before implementation. Guides the guardian from rough idea to approved design spec.
Senior engineer code review workflow — whole-picture understanding, mandatory beyond-the-diff verification, architecture-level review (SSOT, Occam's razor), SOLID, security, performance, and code quality, with P0-P3 severity classification.
Fetch GitHub pull request diffs with gh CLI, including large-PR fallback strategies.
| name | meta-tags-optimizer |
| description | Optimize title tags, meta descriptions, Open Graph, Twitter cards for maximum CTR with A/B variations. 标题优化/元描述/CTR |
| version | 6.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations. |
| homepage | https://github.com/aaron-he-zhu/seo-geo-claude-skills |
| metadata | {"author":"aaron-he-zhu","version":"6.0.0","geo-relevance":"low","tags":["seo","meta-tags","title-tag","meta-description","open-graph","twitter-card","ctr-optimization","social-sharing","标题优化","元描述","メタタグ","메타태그","meta-tags-seo"],"triggers":["optimize title tag","write meta description","improve CTR","Open Graph tags","social media preview","title optimization","meta tags","Twitter cards","my title tag needs work","low click-through rate","fix my meta tags","OG tags not showing","social preview looks wrong","my click rate is low","how to write a good title tag","how to improve click-through rate","what is a good meta description","Yoast SEO title tool","RankMath title optimizer","标题标签优化","元描述优化","OG标签","点击率提升","社交预览","TDK优化","标题不好","点击率太低","社交分享预览不对","标题怎么写","TDK怎么写","メタタグ最適化","タイトルタグ","CTR改善","메타 태그 최적화","제목 태그","클릭률 개선","optimizar meta tags","mejorar CTR","etiquetas Open Graph","otimizar meta tags","meta discription","tittle tag"]} |
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This build skill follows the shared Skill Contract and State Model.
This skill creates compelling, optimized meta tags that improve click-through rates from search results and enhance social media sharing. It covers title tags, meta descriptions, and social meta tags.
System role: Build layer skill. It turns briefs and signals into assets that other skills can review, publish, and monitor.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs a shippable asset or transformation that should feed directly into quality review, deployment, or monitoring.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Create meta tags for a page about [topic] targeting [keyword]
Write title and meta description for this content: [content/URL]
Improve these meta tags for better CTR: [current tags]
Create Open Graph and Twitter card tags for [page/URL]
Expected output: a ready-to-use asset or implementation-ready transformation plus a short handoff summary ready for memory/content/.
memory/content/.CLAUDE.md, memory/decisions.md, and memory/open-loops.md.Next Best Skill below when the asset is ready for review or deployment.See CONNECTORS.md for tool category placeholders.
With ~~search console + ~~SEO tool connected: Automatically pull current meta tags, CTR data by query, competitor title/description patterns, SERP preview data, and impression/click metrics to identify optimization opportunities.
With manual data only: Ask the user to provide:
Proceed with the full workflow using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
When a user requests meta tag optimization:
Gather Page Information
### Page Analysis
**Page URL**: [URL]
**Page Type**: [blog/product/landing/service/homepage]
**Primary Keyword**: [keyword]
**Secondary Keywords**: [keywords]
**Target Audience**: [audience]
**Primary CTA**: [action you want users to take]
**Unique Value Prop**: [what makes this page special]
Create Optimized Title Tag
### Title Tag Optimization
**Requirements**:
- Length: 50-60 characters (displays fully in SERP)
- Include primary keyword (preferably near front)
- Make it compelling and click-worthy
- Match search intent
- Include brand name if appropriate
**Title Tag Formula Options**:
1. **Keyword | Benefit | Brand**
"[Primary Keyword]: [Benefit] | [Brand Name]"
2. **Number + Keyword + Promise**
"[Number] [Keyword] That [Promise/Result]"
3. **How-to Format**
"How to [Keyword]: [Benefit/Result]"
4. **Question Format**
"What is [Keyword]? [Brief Answer/Hook]"
5. **Year + Keyword**
"[Keyword] in [Year]: [Hook/Update]"
**Generated Title Options**:
| Option | Title | Length | Power Words | Keyword Position |
|--------|-------|--------|-------------|------------------|
| 1 | [Title] | [X] chars | [words] | [Front/Middle] |
| 2 | [Title] | [X] chars | [words] | [Front/Middle] |
| 3 | [Title] | [X] chars | [words] | [Front/Middle] |
**Recommended**: Option [X]
**Reasoning**: [Why this option is best]
**Title Tag Code**:
```html
<title>[Selected Title]</title>
Write Meta Description
### Meta Description Optimization
**Requirements**:
- Length: 150-160 characters (displays fully in SERP)
- Include primary keyword naturally
- Include clear call-to-action
- Match page content accurately
- Create urgency or curiosity
- Avoid duplicate descriptions
**Meta Description Formula**:
[What the page offers] + [Benefit to user] + [Call-to-action]
**Power Elements to Include**:
- Numbers and statistics
- Current year
- Emotional triggers
- Action verbs
- Unique value proposition
**Generated Description Options**:
| Option | Description | Length | CTA | Emotional Trigger |
|--------|-------------|--------|-----|-------------------|
| 1 | [Description] | [X] chars | [CTA] | [Trigger] |
| 2 | [Description] | [X] chars | [CTA] | [Trigger] |
| 3 | [Description] | [X] chars | [CTA] | [Trigger] |
**Recommended**: Option [X]
**Reasoning**: [Why this option is best]
**Meta Description Code**:
```html
<meta name="description" content="[Selected Description]">
Create Open Graph, Twitter Card, and Additional Meta Tags
Generate OG tags (og:type, og:url, og:title, og:description, og:image), Twitter Card tags, canonical URL, robots, viewport, author, and article-specific tags. Then combine into a complete meta tag block.
Reference: See references/meta-tag-code-templates.md for OG type selection guide, Twitter card type selection, all HTML code templates, and the complete meta tag block template.
CORE-EEAT Alignment Check
Verify meta tags align with content quality standards. Reference: CORE-EEAT Benchmark
### CORE-EEAT Meta Tag Alignment
| Check | Status | Notes |
|-------|--------|-------|
| **C01 Intent Alignment**: Title promise matches actual content delivery | ✅/⚠️/❌ | [Does the title accurately represent what the page delivers?] |
| **C02 Direct Answer**: Meta description reflects the core answer available in first 150 words | ✅/⚠️/❌ | [Does the description preview the direct answer?] |
**If C01 fails**: Title is misleading — rewrite to match actual content.
**If C02 fails**: Content may need restructuring to front-load the answer, or description should better reflect available content.
Provide CTR Optimization Tips
## CTR Optimization Analysis
### Power Words Used
- [Word 1] - Creates [emotion/action]
- [Word 2] - Creates [emotion/action]
### CTR Boosting Elements
| Element | Present | Impact |
|---------|---------|--------|
| Numbers | Yes/No | +20-30% CTR |
| Current Year | Yes/No | +15-20% CTR |
| Power Words | Yes/No | +10-15% CTR |
| Question | Yes/No | +10-15% CTR |
| Brackets | Yes/No | +10% CTR |
### A/B Test Suggestions
Test these variations:
**Version A** (Current):
- Title: [Title]
- Description: [Description]
**Version B** (Test):
- Title: [Alternative title]
- Description: [Alternative description]
- Hypothesis: [Why this might perform better]
User: "Create meta tags for a blog post about 'how to start a podcast in [current year]'"
Output:
## Meta Tags: How to Start a Podcast ([current year])
### Title Tag
```html
<title>How to Start a Podcast in [current year]: Complete Beginner's Guide</title>
Length: ~55 characters ✅ Keyword: "how to start a podcast" at front ✅ Power Words: "Complete", "Beginner's" ✅
<meta name="description" content="Learn how to start a podcast in [current year] with our step-by-step guide. Covers equipment, hosting, recording, and launching your first episode. Start podcasting today!">
Length: ~163 characters ✅ Keyword: Included naturally ✅ CTA: "Start podcasting today!" ✅
Complete meta tag block (with OG, Twitter, Article tags) generated using template from references/meta-tag-code-templates.md.
Title Variation B: "Start a Podcast in [current year]: Step-by-Step Guide (+ Free Checklist)"
Title Variation C: "How to Start a Podcast: [current year] Guide [Equipment + Software + Tips]"
Description Variation B: "Want to start a podcast in [current year]? This guide covers everything: equipment ($100 budget option), best hosting platforms, recording tips, and how to get your first 1,000 listeners."
## Tips for Success
1. **Front-load keywords** - Put important terms at the beginning
2. **Match intent** - Description should preview what page delivers
3. **Be specific** - Vague descriptions get ignored
4. **Test variations** - Small changes can significantly impact CTR
5. **Update regularly** - Add current year, refresh messaging
6. **Check competitors** - See what's working in your SERP
### Save Results
After delivering content or optimization output to the user, ask:
> "Save these results for future sessions?"
If yes, write a dated summary to `memory/content/YYYY-MM-DD-<topic>.md` containing:
- One-line description of what was created
- Target keyword and content type
- Open loops or items needing review
- Source data references
**Gate check recommended**: Run content-quality-auditor before publishing (PostToolUse hook will remind automatically).
If any findings should influence ongoing strategy, recommend promoting key conclusions to `memory/hot-cache.md`.
## Reference Materials
- [Meta Tag Formulas](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/build/meta-tags-optimizer/references/meta-tag-formulas.md) — Proven title and description formulas
- [CTR and Social Reference](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/build/meta-tags-optimizer/references/ctr-and-social-reference.md) — Page-type templates, CTR data, OG best practices
## Next Best Skill
- **Primary**: [schema-markup-generator](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/build/schema-markup-generator/SKILL.md) — complete the SERP packaging with structured data.