meta-tags-optimizer
为最大化点击率(CTR)优化标题标签、元描述、Open Graph 与 Twitter 卡片,并提供 A/B 测试变体。标题优化/元描述/CTR
分类
SEO安装
下载并解压到你的 skills 目录
复制命令,发送给 OpenClaw 自动安装:
Meta Tags Optimizer
> 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.
When This Must Trigger
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.
What This Skill Does
Quick Start
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Create Meta Tags
Create meta tags for a page about [topic] targeting [keyword]Write title and meta description for this content: [content/URL]Optimize Existing Tags
Improve these meta tags for better CTR: [current tags]Social Media Tags
Create Open Graph and Twitter card tags for [page/URL]Skill Contract
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.Data Sources
> 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.
Instructions
When a user requests meta tag optimization:
### 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]
### 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
### 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**:htmlGenerate 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.
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.
## 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]Validation Checkpoints
Input Validation
Output Validation
Example
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 Taghtml**Length**: ~55 characters ✅
**Keyword**: "how to start a podcast" at front ✅
**Power Words**: "Complete", "Beginner's" ✅
### Meta Descriptionhtml**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](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/build/meta-tags-optimizer/references/meta-tag-code-templates.md)._
### A/B Test Variations
**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
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:
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.