Schema Markup & Structured Data
Generate Schema Markup for SEO
Creating proper schema.org markup is complex and errors can hurt SEO. This skill provides a structured approach to design valid JSON-LD that qualifies for Google rich results while avoiding common mistakes.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「Schema Markup & Structured Data」を使用しています。 Create FAQ schema for a support page with 5 questions and answers about our product returns policy
期待される結果:
Eligibility Index: 88/100 (Strong Candidate)
Schema Strategy: FAQPage is appropriate since questions and answers are visible. Score reflects high content-schema alignment, Google-supported type, complete required properties, valid JSON-LD, and low spam risk.
JSON-LD Implementation: [valid FAQPage schema with question/answer pairs]
Validation Checklist: Valid JSON-LD, passes Rich Results Test, matches visible content, meets Google eligibility rules
「Schema Markup & Structured Data」を使用しています。 Add product schema to an e-commerce product page
期待される結果:
Eligibility Assessment Required. Before implementing, I need to know: What content is visible on the page? Which rich result are you targeting? Is this content templated or editorial?
Note: Product schema requires price, availability, and offers to be visible on the page. Schema must match visible content exactly.
セキュリティ監査
安全Prompt-only skill with no executable code. Risk score: 0. Static analysis found no suspicious patterns. The skill is a pure prompt template that guides AI to help with schema markup creation and validation. Contains appropriate safety measures including a Schema Eligibility & Impact Index to prevent invalid markup.
品質スコア
作れるもの
New Schema Implementation
Add schema markup to a new landing page, blog post, or product page with proper eligibility assessment
Schema Audit and Fixes
Review existing schema for errors, warnings, or policy violations and provide corrective recommendations
Multi-Entity Page Strategy
Design schema for pages with multiple related entities using @graph for proper entity relationships
これらのプロンプトを試す
Create JSON-LD schema markup for a [page_type] page about [topic]. The page contains [visible_content]. What schema type should I use and what is the eligibility score?
Audit this JSON-LD schema [paste schema] for errors or policy violations. Identify what needs to be fixed and provide corrected markup.
Evaluate whether a [schema_type] schema qualifies for Google rich results. What are the eligibility requirements and does this content meet them?
Design schema markup for a page with [entities]. How should I use @graph to represent the relationships between [primary_entity] and [secondary_entities]?
ベストプラクティス
- Always calculate the Schema Eligibility & Impact Index before implementing to ensure markup is justified
- Use Google Rich Results Test to validate schema before deployment
- Match schema exactly to visible content - never add markup for content not shown on the page
回避
- Adding schema for content that is not visible to users
- Using unsupported schema types that have no Google eligibility
- Creating misleading or exaggerated claims in schema to game rich results