schema-markup
Schema.org markup implementation patterns for rich results. Use when adding structured data to content for enhanced SERP appearances.
When & Why to Use This Skill
This Claude skill provides comprehensive Schema.org markup implementation patterns designed to enhance website visibility and search engine performance. It streamlines the process of adding structured data, enabling websites to achieve rich results, improve click-through rates (CTR), and ensure technical SEO compliance through standardized JSON-LD templates.
Use Cases
- 1. Rich Result Optimization: Generate precise JSON-LD code for Articles, FAQs, and How-To guides to secure prominent, high-engagement positions in search engine results.
- 2. Technical SEO Auditing: Validate and refine existing structured data implementations to ensure they meet the latest Schema.org standards and Google's technical requirements.
- 3. Content Strategy Planning: Utilize standardized patterns to plan schema implementation for new content types, ensuring maximum search engine discoverability from the start.
- 4. SERP Real Estate Expansion: Implement specific schema types like FAQPage to increase the visual footprint and user interaction directly on the search engine result pages.
| plugin | seo |
|---|---|
| updated | 2026-01-20 |
| name | schema-markup |
| description | Schema.org markup implementation patterns for rich results. Use when adding structured data to content for enhanced SERP appearances. |
plugin: seo updated: 2026-01-20
Schema Markup
When to Use
- Adding structured data to content
- Implementing rich results
- Validating existing schema
- Planning schema strategy
Common Schema Types
Article/BlogPosting
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title (max 110 chars)",
"image": ["https://example.com/image.jpg"],
"author": {
"@type": "Person",
"name": "Author Name"
},
"publisher": {
"@type": "Organization",
"name": "Publisher Name",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.jpg"
}
},
"datePublished": "2025-01-01",
"dateModified": "2025-01-15"
}
FAQPage
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Question text?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Answer text."
}
}
]
}
HowTo
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to do something",
"step": [
{
"@type": "HowToStep",
"name": "Step 1 title",
"text": "Step 1 description"
},
{
"@type": "HowToStep",
"name": "Step 2 title",
"text": "Step 2 description"
}
]
}
Implementation Checklist
- Use JSON-LD format (preferred by Google)
- Place in
<head>or end of<body> - Include all required properties
- Validate with Google Rich Results Test
- Test with Schema.org validator
- Check Search Console for errors
Best Practices
- Be specific: Use most specific type (BlogPosting over Article)
- Be accurate: Only mark up visible content
- Be complete: Include all required properties
- Test thoroughly: Use validation tools
- Monitor: Check Search Console regularly