Schema Markup Analysis & Generation
When to Use
- Use when detecting, validating, or generating Schema.org structured data.
- Use when the user asks about JSON-LD, rich results, or markup opportunities.
- Use when schema validation is the main task, rather than a broader SEO audit.
Detection
- Scan page source for JSON-LD
<script type="application/ld+json">
- Check for Microdata (
itemscope, itemprop)
- Check for RDFa (
typeof, property)
- Always recommend JSON-LD as primary format (Google's stated preference)
Validation
- Check required properties per schema type
- Validate against Google's supported rich result types
- Test for common errors:
- Missing @context
- Invalid @type
- Wrong data types
- Placeholder text
- Relative URLs (should be absolute)
- Invalid date formats
- Flag deprecated types (see below)
Schema Type Status (as of Feb 2026)
Read references/schema-types.md for the full list. Key rules:
ACTIVE (recommend freely):
Organization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting
VIDEO & SPECIALIZED (recommend freely):
BroadcastEvent, Clip, SeekToAction, SoftwareSourceCode
See schema/templates.json for ready-to-use JSON-LD templates for these types.
JSON-LD and JavaScript rendering: Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.
RESTRICTED (only for specific sites):
- FAQ: ONLY for government and healthcare authority sites (restricted Aug 2023)
DEPRECATED (never recommend):
- HowTo: Rich results removed September 2023
- SpecialAnnouncement: Deprecated July 31, 2025
- CourseInfo, EstimatedSalary, LearningVideo: Retired June 2025
- ClaimReview: Retired from rich results June 2025
- VehicleListing: Retired from rich results June 2025
- Practice Problem: Retired from rich results late 2025
- Dataset: Retired from rich results late 2025
- Book Actions: Deprecated then reversed, still functional as of Feb 2026 (historical note)
Generation
When generating schema for a page:
- Identify page type from content analysis
- Select appropriate schema type(s)
- Generate valid JSON-LD with all required + recommended properties
- Include only truthful, verifiable data. Use placeholders clearly marked for user to fill
- Validate output before presenting
Common Schema Templates
Organization
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "[Company Name]",
"url": "[Website URL]",
"logo": "[Logo URL]",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "[Phone]",
"contactType": "customer service"
},
"sameAs": [
"[Facebook URL]",
"[LinkedIn URL]",
"[Twitter URL]"
]
}
LocalBusiness
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "[Business Name]",
"address": {
"@type": "PostalAddress",
"streetAddress": "[Street]",
"addressLocality": "[City]",
"addressRegion": "[State]",
"postalCode": "[ZIP]",
"addressCountry": "US"
},
"telephone": "[Phone]",
"openingHours": "Mo-Fr 09:00-17:00",
"geo": {
"@type": "GeoCoordinates",
"latitude": "[Lat]",
"longitude": "[Long]"
}
}
Article/BlogPosting
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "[Title]",
"author": {
"@type": "Person",
"name": "[Author Name]"
},
"datePublished": "[YYYY-MM-DD]",
"dateModified": "[YYYY-MM-DD]",
"image": "[Image URL]",
"publisher": {
"@type": "Organization",
"name": "[Publisher]",
"logo": {
"@type": "ImageObject",
"url": "[Logo URL]"
}
}
}
Output
SCHEMA-REPORT.md: detection and validation results
generated-schema.json: ready-to-use JSON-LD snippets
Validation Results
| Schema |
Type |
Status |
Issues |
| ... |
... |
✅/⚠️/❌ |
... |
Recommendations
- Missing schema opportunities
- Validation fixes needed
- Generated code for implementation
Error Handling
| Scenario |
Action |
| URL unreachable |
Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |
| No schema markup found |
Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |
| Invalid JSON-LD syntax |
Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |
| Deprecated schema type detected |
Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: seo-schema3description: >4 Detect, validate, and generate Schema.org structured data. JSON-LD format5 preferred. Use when user says "schema", "structured data", "rich results",6 "JSON-LD", or "markup".7risk: critical8source: "https://github.com/AgriciDaniel/claude-seo"9date_added: "2026-03-21"10user-invokable: true11argument-hint: "[url]"12allowed-tools:13 - Read14 - Grep15 - Glob16 - Bash17 - WebFetch18 - Write19metadata:20 source: https://skillmd.com/skills/agricidaniel/seo-schema21---2223# Schema Markup Analysis & Generation2425## When to Use26- Use when detecting, validating, or generating Schema.org structured data.27- Use when the user asks about JSON-LD, rich results, or markup opportunities.28- Use when schema validation is the main task, rather than a broader SEO audit.2930## Detection31321. Scan page source for JSON-LD `<script type="application/ld+json">`332. Check for Microdata (`itemscope`, `itemprop`)343. Check for RDFa (`typeof`, `property`)354. Always recommend JSON-LD as primary format (Google's stated preference)3637## Validation3839- Check required properties per schema type40- Validate against Google's supported rich result types41- Test for common errors:42 - Missing @context43 - Invalid @type44 - Wrong data types45 - Placeholder text46 - Relative URLs (should be absolute)47 - Invalid date formats48- Flag deprecated types (see below)4950## Schema Type Status (as of Feb 2026)5152Read `references/schema-types.md` for the full list. Key rules:5354### ACTIVE (recommend freely):55Organization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting5657### VIDEO & SPECIALIZED (recommend freely):58BroadcastEvent, Clip, SeekToAction, SoftwareSourceCode5960See `schema/templates.json` for ready-to-use JSON-LD templates for these types.6162> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.6364### RESTRICTED (only for specific sites):65- **FAQ**: ONLY for government and healthcare authority sites (restricted Aug 2023)6667### DEPRECATED (never recommend):68- **HowTo**: Rich results removed September 202369- **SpecialAnnouncement**: Deprecated July 31, 202570- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 202571- **ClaimReview**: Retired from rich results June 202572- **VehicleListing**: Retired from rich results June 202573- **Practice Problem**: Retired from rich results late 202574- **Dataset**: Retired from rich results late 202575- **Book Actions**: Deprecated then reversed, still functional as of Feb 2026 (historical note)7677## Generation7879When generating schema for a page:801. Identify page type from content analysis812. Select appropriate schema type(s)823. Generate valid JSON-LD with all required + recommended properties834. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill845. Validate output before presenting8586## Common Schema Templates8788### Organization89```json90{91 "@context": "https://schema.org",92 "@type": "Organization",93 "name": "[Company Name]",94 "url": "[Website URL]",95 "logo": "[Logo URL]",96 "contactPoint": {97 "@type": "ContactPoint",98 "telephone": "[Phone]",99 "contactType": "customer service"100 },101 "sameAs": [102 "[Facebook URL]",103 "[LinkedIn URL]",104 "[Twitter URL]"105 ]106}107```108109### LocalBusiness110```json111{112 "@context": "https://schema.org",113 "@type": "LocalBusiness",114 "name": "[Business Name]",115 "address": {116 "@type": "PostalAddress",117 "streetAddress": "[Street]",118 "addressLocality": "[City]",119 "addressRegion": "[State]",120 "postalCode": "[ZIP]",121 "addressCountry": "US"122 },123 "telephone": "[Phone]",124 "openingHours": "Mo-Fr 09:00-17:00",125 "geo": {126 "@type": "GeoCoordinates",127 "latitude": "[Lat]",128 "longitude": "[Long]"129 }130}131```132133### Article/BlogPosting134```json135{136 "@context": "https://schema.org",137 "@type": "Article",138 "headline": "[Title]",139 "author": {140 "@type": "Person",141 "name": "[Author Name]"142 },143 "datePublished": "[YYYY-MM-DD]",144 "dateModified": "[YYYY-MM-DD]",145 "image": "[Image URL]",146 "publisher": {147 "@type": "Organization",148 "name": "[Publisher]",149 "logo": {150 "@type": "ImageObject",151 "url": "[Logo URL]"152 }153 }154}155```156157## Output158159- `SCHEMA-REPORT.md`: detection and validation results160- `generated-schema.json`: ready-to-use JSON-LD snippets161162### Validation Results163| Schema | Type | Status | Issues |164|--------|------|--------|--------|165| ... | ... | ✅/⚠️/❌ | ... |166167### Recommendations168- Missing schema opportunities169- Validation fixes needed170- Generated code for implementation171172## Error Handling173174| Scenario | Action |175|----------|--------|176| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |177| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |178| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |179| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |180181## Limitations182- Use this skill only when the task clearly matches the scope described above.183- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.184- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.