Schema Markup Analysis & Generation
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 June 2026)
Read ../seo/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.
NO RICH RESULTS, KEEP IF USEFUL:
- FAQPage: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov/health restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use QAPage.
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: Deprecation notice 2025-11-05; Search Console / Rich Results Test support removed 2026-01-06
- Book Actions: Deprecated/removed from Google rich results; do not recommend it for SERP features.
- Search Console / Rich Results Test / appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.
Supported for Dataset Search only:
- Dataset: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.
Still supported (do not flag):
- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz /
eduQuestionType=Flashcard). For e-commerce, hasAdultConsideration (added 2026-05-20; value https://schema.org/SexualContentConsideration) is required for adult products. Product.category accepts Text, CategoryCode, or arrays mixing both.
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
- For review markup, reject fake reviews and undisclosed incentivized reviews.
An incentive must be clearly and prominently disclosed on the page.
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. |
1---
2name: seo-schema
3description: >
4 Detect, validate, and generate Schema.org structured data. JSON-LD format
5 preferred. Use when user says "schema", "structured data", "rich results",
6 "JSON-LD", or "markup".
7user-invocable: true
8argument-hint: "[url]"
9license: MIT
10metadata:
11 source: https://skillmd.com/skills/gabrielmoreira/seo-schema
12 author: AgriciDaniel
13 version: "2.2.5"
14 category: seo
15---
16
17# Schema Markup Analysis & Generation
18
19## Detection
20
211. Scan page source for JSON-LD `<script type="application/ld+json">`
222. Check for Microdata (`itemscope`, `itemprop`)
233. Check for RDFa (`typeof`, `property`)
244. Always recommend JSON-LD as primary format (Google's stated preference)
25
26## Validation
27
28- Check required properties per schema type
29- Validate against Google's supported rich result types
30- Test for common errors:
31 - Missing @context
32 - Invalid @type
33 - Wrong data types
34 - Placeholder text
35 - Relative URLs (should be absolute)
36 - Invalid date formats
37- Flag deprecated types (see below)
38
39## Schema Type Status (as of June 2026)
40
41Read `../seo/references/schema-types.md` for the full list. Key rules:
42
43### ACTIVE (recommend freely):
44Organization, 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
45
46### VIDEO & SPECIALIZED (recommend freely):
47BroadcastEvent, Clip, SeekToAction, SoftwareSourceCode
48
49See `schema/templates.json` for ready-to-use JSON-LD templates for these types.
50
51> **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.
52
53### NO RICH RESULTS, KEEP IF USEFUL:
54- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov/health restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.
55
56### DEPRECATED (never recommend):
57- **HowTo**: Rich results removed September 2023
58- **SpecialAnnouncement**: Deprecated July 31, 2025
59- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025
60- **ClaimReview**: Retired from rich results June 2025
61- **VehicleListing**: Retired from rich results June 2025
62- **Practice Problem**: Deprecation notice 2025-11-05; Search Console / Rich Results Test support removed 2026-01-06
63- **Book Actions**: Deprecated/removed from Google rich results; do not recommend it for SERP features.
64- Search Console / Rich Results Test / appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.
65
66### Supported for Dataset Search only:
67- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.
68
69### Still supported (do not flag):
70- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz / `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-20; value `https://schema.org/SexualContentConsideration`) is required for adult products. `Product.category` accepts `Text`, `CategoryCode`, or arrays mixing both.
71
72## Generation
73
74When generating schema for a page:
751. Identify page type from content analysis
762. Select appropriate schema type(s)
773. Generate valid JSON-LD with all required + recommended properties
784. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill
795. Validate output before presenting
806. For review markup, reject fake reviews and undisclosed incentivized reviews.
81 An incentive must be clearly and prominently disclosed on the page.
82
83## Common Schema Templates
84
85### Organization
86```json
87{
88 "@context": "https://schema.org",
89 "@type": "Organization",
90 "name": "[Company Name]",
91 "url": "[Website URL]",
92 "logo": "[Logo URL]",
93 "contactPoint": {
94 "@type": "ContactPoint",
95 "telephone": "[Phone]",
96 "contactType": "customer service"
97 },
98 "sameAs": [
99 "[Facebook URL]",
100 "[LinkedIn URL]",
101 "[Twitter URL]"
102 ]
103}
104```
105
106### LocalBusiness
107```json
108{
109 "@context": "https://schema.org",
110 "@type": "LocalBusiness",
111 "name": "[Business Name]",
112 "address": {
113 "@type": "PostalAddress",
114 "streetAddress": "[Street]",
115 "addressLocality": "[City]",
116 "addressRegion": "[State]",
117 "postalCode": "[ZIP]",
118 "addressCountry": "US"
119 },
120 "telephone": "[Phone]",
121 "openingHours": "Mo-Fr 09:00-17:00",
122 "geo": {
123 "@type": "GeoCoordinates",
124 "latitude": "[Lat]",
125 "longitude": "[Long]"
126 }
127}
128```
129
130### Article/BlogPosting
131```json
132{
133 "@context": "https://schema.org",
134 "@type": "Article",
135 "headline": "[Title]",
136 "author": {
137 "@type": "Person",
138 "name": "[Author Name]"
139 },
140 "datePublished": "[YYYY-MM-DD]",
141 "dateModified": "[YYYY-MM-DD]",
142 "image": "[Image URL]",
143 "publisher": {
144 "@type": "Organization",
145 "name": "[Publisher]",
146 "logo": {
147 "@type": "ImageObject",
148 "url": "[Logo URL]"
149 }
150 }
151}
152```
153
154## Output
155
156- `SCHEMA-REPORT.md`: detection and validation results
157- `generated-schema.json`: ready-to-use JSON-LD snippets
158
159### Validation Results
160| Schema | Type | Status | Issues |
161|--------|------|--------|--------|
162| ... | ... | ✅/⚠️/❌ | ... |
163
164### Recommendations
165- Missing schema opportunities
166- Validation fixes needed
167- Generated code for implementation
168
169## Error Handling
170
171| Scenario | Action |
172|----------|--------|
173| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |
174| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |
175| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |
176| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |