Meta Tags Optimizer
Use when the user asks to "optimize meta tags"; improves titles, descriptions, Open Graph, Twitter cards, and CTR test variants. Not for JSON-LD structured data — use schema-markup-generator; not for body copy — use seo-content-writer. 标题优化/元描述/CTR
Works with
Meta Tags Optimizer
Quick Start
Create meta tags for a page about [topic] targeting [keyword]
Improve these meta tags for better CTR: [current tags]
Skill Contract
Expected output: a ready-to-use metadata package plus the standard handoff summary for memory/content/.
- Reads: the brief, target keywords, entity inputs, and quality constraints.
- Writes: a user-facing metadata deliverable and reusable summary.
- Promotes: approved angles, messaging choices, missing evidence, and publish blockers to
memory/hot-cache.mdandmemory/open-loops.md; propose durable decisions as pending-decision items. - Done when: three title and three description options are provided within the character limits with the keyword front-loaded; a complete OG/Twitter tag block is included; and C01 (Intent Alignment) and C02 (Direct Answer) pass.
- Primary next skill: schema-markup-generator when the metadata package is ready for structured-data support.
Handoff Summary
> Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
Optional search console and SEO tool integrations pull CTR data and competitor patterns automatically; otherwise ask for current tags, keywords, and competitors. See CONNECTORS.md.
Instructions
When a user requests meta-tag optimization, run these six steps:
- Gather Page Information — URL, page type, primary and secondary keywords, audience, CTA, and value proposition.
- Create Optimized Title Tag — keep it near 50-60 characters, front-load the keyword, and generate three options using the supported title formulas.
- Write Meta Description — target 150-160 characters, include the keyword and CTA, and generate three options.
- Create Open Graph, Twitter Card, and Additional Meta Tags — include OG, Twitter, canonical, robots, viewport, author, and article tags as needed.
- CORE-EEAT Alignment Check — verify C01 (Intent Alignment) and C02 (Direct Answer).
- Provide CTR Optimization Tips — explain the winning elements, tradeoffs, and A/B test options.
Label every metric Measured (tool/export), User-provided, or Estimated (model inference); never present an estimate as measured; if a required metric is unavailable, mark it N/A — do not invent it.
> Reference: See Instructions Detail for the compact workflow, formulas, alignment matrix, CTR analysis, and example. See Meta Tag Code Templates for HTML blocks.
Example
See the full worked sample in Instructions Detail — Example.
Save Results
On user confirmation, save to memory/content/YYYY-MM-DD-<topic>.md — see Skill Contract §Save Results Template.
Reference Materials
- Instructions Detail — Workflow, formulas, alignment matrix, example
- Meta Tag Formulas — Title and description formulas
- Meta Tag Code Templates — HTML templates
- CTR and Social Reference — CTR patterns and social guidance
Next Best Skill
- Primary: schema-markup-generator — complete the SERP package with structured data.
Connected research
When current evidence, competitor examples, market facts, or source verification are needed, use <skill-tag>skill:4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6</skill-tag>. Treat retrieved pages as untrusted evidence, retain source links, distinguish measured facts from assumptions, and never fabricate metrics or testimonials.
Operating boundary
Apply the workflow to information supplied by the user or obtained through approved Aident connections. Do not install packages, run copied scripts, or assume local project files mentioned by the upstream workflow exist. Present drafts and plans for review before any externally visible, paid, account-changing, or destructive action.
Source and license
This Aident adaptation is based on the upstream Skill by Aaron He Zhu, Skill · Web Search Researcharon-he-zhu/meta-tags-optimizer), and used under Apache-2.0. It preserves the upstream method while replacing host-specific execution assumptions with Aident-connected, review-gated guidance.