Skill detail
serp-markup-builder
Builds document-head SEO assets: title tags, meta descriptions, Open Graph/Twitter cards, and validated JSON-LD schema for FAQ, HowTo, Article, Product, or LocalBusiness rich results.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
---
name: serp-markup-builder
slug: serp-markup-builder
displayName: "SERP Markup Builder · 标题优化"
summary: "标题优化/元描述/Schema标记/结构化数据"
description: 'Use when the user asks to "optimize meta tags", "write title tags / meta descriptions", "add Open Graph or Twitter cards", or "generate schema / JSON-LD" for FAQ, HowTo, Article, Product, or LocalBusiness rich-result candidates. Produces title/description options, an OG+Twitter block, and validated JSON-LD for the document head. Not for body copy — use content-writer; not for crawl/index technical issues — use technical-seo-checker. 标题优化/元描述/Schema标记/结构化数据'
version: "20.1.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use when building anything in the document head for a page — title tags, meta descriptions, Open Graph and Twitter Card tags, canonical/robots meta, and JSON-LD Schema.org structured data for rich-result and answer-engine eligibility."
argument-hint: "[meta|schema] <page URL or content>"
allowed-tools: WebFetch
metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "seo-geo", "phase": "implement", "geo-relevance": "high", "hermes": {"tags": ["marketing", "seo-geo", "implement"], "category": "seo-geo"}, "openclaw": {"emoji": "🔍", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---
# SERP Markup Builder
Builds everything that lives in a page's `<head>` and shapes its search + answer-engine presence: title/meta/social tags (mode `meta`) and Schema.org JSON-LD (mode `schema`). Both modes operate on the same document head and write to `memory/content/`.
## Mode Selector
Pick the mode from the request; run both in sequence when the user wants the full SERP package.
| Mode | Trigger | Output | CORE-EEAT lens |
|------|---------|--------|----------------|
| `meta` | "optimize meta tags", "title tag", "meta description", "Open Graph", "Twitter card", "improve CTR" | 3 titles + 3 descriptions (within char limits), OG/Twitter/canonical/robots block, CTR analysis | C01 Intent Alignment, C02 Direct Answer |
| `schema` | "generate schema", "JSON-LD", "structured data", "FAQ/HowTo/Product/LocalBusiness markup", "rich snippet" | valid JSON-LD for the chosen type(s), placement + validation steps, rich-result eligibility read | O05 Schema Markup |
Default when unstated: infer from the noun in the request (title/description/OG → `meta`; JSON-LD/rich result → `schema`). If both are named, run `meta` then `schema`. This skill computes no framework score and runs no vetoes — only the `content-quality-auditor` gate does that.
**Scope guard** — this skill does NOT: write body copy or on-page content (→ [content-writer](../content-writer/SKILL.md)); diagnose crawl, index, canonicalization conflicts, or Core Web Vitals (→ [technical-seo-checker](../../tune/technical-seo-checker/SKILL.md)); or produce the publish-readiness verdict/score (→ [content-quality-auditor](../../tune/content-quality-auditor/SKILL.md)).
## Quick Start
```text
[meta] Optimize meta tags for a page about [topic] targeting [keyword]
[meta] Improve these meta tags for better CTR: [current tags]
[schema] Generate schema markup for this [content type]: [content/URL]
[schema] Create FAQ schema for these questions and answers: [Q&A list]
[schema] Create Product / LocalBusiness schema for [name] with [details]
```
Output expectation: `meta` returns three title and three description options plus a paste-ready OG/Twitter block; `schema` returns a validated JSON-LD block with placement and a validation checklist.
## Skill Contract
**Expected output**: a ready-to-paste document-head asset (metadata package and/or JSON-LD) plus the standard handoff summary ready for `memory/content/`.
- **Reads**: the brief, target keywords, page type/intent, entity inputs, current tags/markup, and quality constraints.
- **Writes**: a user-facing head-markup deliverable plus a rRead the full source on GitHub (opens external page)