Schema Markup Expert
Powerful skill for user, wants, optimize, schema. Includes structured workflows, validation checks, and reusable patterns for business marketing.
Schema Markup Expert
A Claude Code skill for implementing structured data and schema.org markup that helps search engines understand your content and enables rich results in Google, Bing, and other search engines. Covers JSON-LD implementation, testing, validation, and advanced schema patterns.
When to Use This Skill
Choose Schema Markup Expert when:
- You want to add structured data to your website for rich search results
- You need to implement JSON-LD schema for specific content types
- You're auditing existing schema markup for errors or missing opportunities
- You want to enable features like FAQ dropdowns, star ratings, or breadcrumbs in search results
- You're implementing schema for e-commerce, local business, or article content
Consider alternatives when:
- You need broader SEO strategy (use an SEO optimizer skill)
- You want content optimization for rankings (use a content SEO skill)
- You need programmatic page generation (use a programmatic SEO skill)
Quick Start
# Install the skill claude install schema-markup-expert # Generate schema for a product page claude "Generate Product schema markup for a SaaS pricing page with 3 tiers: Starter ($29), Pro ($79), Enterprise (custom)" # Add FAQ schema claude "Create FAQPage schema for these 5 questions about our API: [list questions]" # Audit existing schema claude "Audit the schema markup on our website. Here's the current JSON-LD: [paste]"
Core Concepts
Common Schema Types
| Schema Type | Rich Result | Use Case |
|---|---|---|
| FAQPage | Expandable Q&A in search results | FAQ sections, knowledge base articles |
| HowTo | Step-by-step instructions with images | Tutorials, guides, documentation |
| Product | Price, availability, ratings | E-commerce, SaaS pricing pages |
| Article | Author, date, headline in search | Blog posts, news articles |
| BreadcrumbList | Navigation path in search results | Any page with hierarchical navigation |
| Organization | Knowledge panel, logo, social links | Homepage, about page |
| LocalBusiness | Map pack, hours, contact info | Physical businesses, local services |
| SoftwareApplication | App info, ratings, pricing | Software product pages |
JSON-LD Implementation
{ "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "Your App Name", "applicationCategory": "DeveloperApplication", "operatingSystem": "Web", "offers": { "@type": "Offer", "price": "29.00", "priceCurrency": "USD", "priceValidUntil": "2026-12-31" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "ratingCount": "1247" } }
Schema Nesting and Relationships
| Pattern | Description | Example |
|---|---|---|
| Direct Nesting | Schema within schema | Organization → Address |
| @id References | Link schemas across pages | Product @id referenced by Review |
| ItemList | Ordered collection of items | Top 10 lists, search results |
| Breadcrumb | Hierarchical page path | Home > Category > Subcategory > Page |
Configuration
| Parameter | Type | Default | Description |
|---|---|---|---|
format | string | "json_ld" | Output format: json_ld, microdata, rdfa |
validate | boolean | true | Validate output against Google's requirements |
include_recommended | boolean | true | Include Google's recommended (not just required) fields |
framework | string | "nextjs" | Frontend framework for integration guidance |
multi_entity | boolean | false | Support multiple schema types on one page |
Best Practices
-
Use JSON-LD exclusively — Google recommends JSON-LD over microdata and RDFa. Place it in the
<head>or at the end of<body>. It's easier to implement, maintain, and debug than inline markup. -
Only mark up visible content — Schema should describe content that users can see on the page. Marking up content that isn't visible to users violates Google's guidelines and can result in manual penalties.
-
Test before deploying — Use Google's Rich Results Test and Schema Markup Validator before pushing to production. Invalid schema can prevent rich results entirely and is worse than no schema at all.
-
Start with high-impact types — FAQPage and BreadcrumbList have the highest ROI for most sites. FAQ dropdowns increase SERP real estate significantly, and breadcrumbs improve click-through rates.
-
Keep schema up to date — Prices, ratings, and availability change. Implement schema dynamically from your database rather than hardcoding values. Stale schema data (wrong prices, expired offers) violates Google's policies.
Common Issues
Rich results not appearing — Google doesn't guarantee rich results even with valid schema. Ensure your page also follows content quality guidelines, has sufficient authority, and the schema type is supported in your region. Use Search Console's Enhancements report to check for issues.
Schema validation errors — The most common errors are missing required fields, incorrect data types (string instead of number), and invalid enum values. Run your schema through Google's Rich Results Test and fix all errors before deploying.
Duplicate schema across pages — Each page should have unique schema that describes that specific page's content. Don't copy-paste the same Organization schema with the same @id on every page — use it only on the homepage or about page.
Reviews
No reviews yet. Be the first to review this template!
Similar Templates
Full-Stack Code Reviewer
Comprehensive code review skill that checks for security vulnerabilities, performance issues, accessibility, and best practices across frontend and backend code.
Test Suite Generator
Generates comprehensive test suites with unit tests, integration tests, and edge cases. Supports Jest, Vitest, Pytest, and Go testing.
Pro Architecture Workspace
Battle-tested skill for architectural, decision, making, framework. Includes structured workflows, validation checks, and reusable patterns for development.