SEO结构化数据
meshcode-ai2026-10-25查看 1054复制 1986
检测、验证并生成 Schema.org 结构化数据为 JSON-LD——组织/产品/FAQ/文章/本地商家模板,针对 schema.org + 富媒体搜索结果要求进行验证。当用户说“schema”、“结构化数据”、“富媒体搜索结果”、“JSON-LD”或“标记”时使用。当用户询问富媒体搜索结果、搜索中的星级评分,或希望 Google 更好地理解其页面结构时也使用。
📘如何使用这个技能
- 1复制技能内容·点击上方「Copy SKILL.md」复制全部内容,或 Download 下载到本地
- 2打开你的 AI 客户端·支持 Claude Code、Trae、Cursor、ChatGPT、DeepSeek、Kimi 等任意 AI 助手
- 3粘贴为系统提示/知识文件·Claude Code:放入 .claude/skills/ 目录;普通对话:作为首条消息发送并说「请严格按这份技能文档执行」
- 4直接提出你的需求·AI 会按技能定义的工作流、格式和约束来处理,无需再解释背景
💡 提示:技能生效后,每次对话只需一句需求,AI 会按 SKILL.md 的流程执行。
SKILL.md1773 chars
--- name: seo-schema description: Detect, validate, and generate Schema.org structured data as JSON-LD — organization/product/FAQ/article/local-business templates, validation against schema.org + rich-result requirements. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup". Also use when the user asks about rich results, star ratings in search, or wants Google to better understand their page structure. license: MIT metadata: source: "AgriciDaniel/claude-seo@v2.3.1 (MIT)" category: seo --- # Schema.org (JSON-LD First) ## Detection Scan page source for `<script type="application/ld+json">`. Mark microdata/RDFa as legacy. Cross-check found types against page intent — a product page with no `Product` is a gap. ## Validation - Parses as JSON; `@context: https://schema.org`; `@type` valid - Check required + recommended properties per type. Rich-result eligibility follows the Google Search Gallery — **state that only some types produce rich results**, and don't build expectations around types that don't - Unify entities under one `@id`; link Organization ↔ WebSite ↔ breadcrumb to each other via `@id` references ## Core Generation Templates Organization (`sameAs` with Wikidata/LinkedIn/YouTube — GEO entity crossover), WebSite, BreadcrumbList, Article (+author), Product (+offers, aggregateRating), FAQPage, LocalBusiness (→`seo-local`), HowTo, VideoObject. ## Rules - No markup of hidden content; no fake reviews/ratings (penalty) - Complete required fields before optional ones — partial implementation is riskier than none - FAQPage only for Q&A actually displayed on the page ## Output Found-vs-missing table, validation errors with line numbers, paste-ready JSON-LD blocks, expected rich-result impact per type.