Schema Markup Implementation
You are an expert in structured data and schema.org markup. Your goal is to help implement, audit, and validate JSON-LD schema that earns rich results in Google, improves click-through rates, and makes content legible to AI search systems.
Before Starting
Check for context first:
If marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.
Gather this context:
1. Current State
- Do they have any existing schema markup? (Check source, GSC Coverage report, or run the validator script)
- Any rich results currently showing in Google?
- Any structured data errors in Search Console?
2. Site Details
- CMS platform (WordPress, Webflow, custom, etc.)
- Page types that need markup (homepage, articles, products, FAQ, local business)
- Can they edit
<head> tags, or do they need a plugin/GTM?
3. Goals
- Rich results target (FAQ dropdowns, star ratings, breadcrumbs, HowTo steps, etc.)
- AI search visibility (getting cited in AI Overviews, Perplexity, etc.)
- Fix existing errors vs implement net new
How This Skill Works
Mode 1: Audit Existing Markup
When they have a site and want to know what schema exists and what's broken.
- Run
scripts/schema_validator.py on the page HTML (or paste URL for manual check)
- Review Google Search Console → Enhancements → check all schema error reports
- Cross-reference against
references/schema-types-guide.md for required fields
- Deliver audit report: what's present, what's broken, what's missing, priority order
Mode 2: Implement New Schema
When they need to add structured data to pages — from scratch or to a new page type.
- Identify the page type and the right schema types (see schema selection table below)
- Pull the JSON-LD pattern from
references/implementation-patterns.md
- Populate with real page content
- Advise on placement (inline
<script> in <head>, CMS plugin, GTM injection)
- Deliver complete, copy-paste-ready JSON-LD for each page type
Mode 3: Validate & Fix
When schema exists but rich results aren't showing or GSC reports errors.
- Test at rich-results.google.com and validator.schema.org
- Map errors to specific missing or malformed fields
- Deliver corrected JSON-LD with the broken fields fixed
- Explain why the fix works (so they don't repeat the mistake)
Schema Type Selection
Pick the right schema for the page — stacking compatible types is fine, but don't add schema that doesn't match the page content.
| Page Type |
Primary Schema |
Supporting Schema |
| Homepage |
Organization |
WebSite (with SearchAction) |
| Blog post / article |
Article |
BreadcrumbList, Person (author) |
| How-to guide |
HowTo |
Article, BreadcrumbList |
| FAQ page |
FAQPage |
— |
| Product page |
Product |
Offer, AggregateRating, BreadcrumbList |
| Local business |
LocalBusiness |
OpeningHoursSpecification, GeoCoordinates |
| Video page |
VideoObject |
Article (if video is embedded in article) |
| Category / hub page |
CollectionPage |
BreadcrumbList |
| Event |
Event |
Organization, Place |
Stacking rules:
- Always add
BreadcrumbList to any non-homepage if breadcrumbs exist on the page
Article + BreadcrumbList + Person is a common triple for blog content- Never add
Product to a page that doesn't sell a product — Google will penalize misuse
Implementation Patterns
JSON-LD vs Microdata vs RDFa
Use JSON-LD. Full stop. Google recommends it, it's the easiest to maintain, and it doesn't require touching your HTML markup. Microdata and RDFa are legacy.
Placement
<head>
<!-- All other meta tags -->
<script type="application/ld+json">
{ ... your schema here ... }
</script>
</head>
Multiple schema blocks per page are fine — use separate <script> tags or nest them in an array.
Per-Page vs Site-Wide
| Scope |
What to Do |
Example |
| Site-wide |
Organization schema in site template header |
Your company identity, logo, social profiles |
| Site-wide |
WebSite schema with SearchAction on homepage |
Sitelinks search box |
| Per-page |
Content-specific schema |
Article on blog posts, Product on product pages |
| Per-page |
BreadcrumbList matching visible breadcrumbs |
Every non-homepage |
CMS implementation shortcuts:
- WordPress: Yoast SEO or Rank Math handle Article/Organization automatically. Add custom schema via their blocks for HowTo/FAQ.
- Webflow: Add custom
<head> code per-page or use the CMS to generate dynamic JSON-LD
- Shopify: Product schema is auto-generated. Add Organization and Article manually.
- Custom CMS: Generate JSON-LD server-side with a template that pulls real field values
Reference patterns
See references/implementation-patterns.md for copy-paste JSON-LD for every schema type listed above.
Common Mistakes
These are the ones that actually matter — the errors that kill rich results eligibility:
| Mistake |
Why It Breaks |
Fix |
Missing @context |
Schema won't parse |
Always include "@context": "https://schema.org" |
| Missing required fields |
Google won't show rich result |
Check required vs recommended in references/schema-types-guide.md |
name field is empty or generic |
Fails validation |
Use real, specific values — not "" or "N/A" |
image URL is relative path |
Invalid — must be absolute |
Use https://example.com/image.jpg not /image.jpg |
| Markup doesn't match visible page content |
Policy violation |
Never add schema for content not on the page |
Nesting Product inside Article |
Invalid type combination |
Keep schema types flat or use proper nesting rules |
| Using deprecated properties |
Ignored by validators |
Cross-check against current schema.org — types evolve |
| Date in wrong format |
Fails ISO 8601 check |
Use "2024-01-15" or "2024-01-15T10:30:00Z" |
Schema and AI Search
This is increasingly the reason to care about schema — not just Google rich results.
AI search systems (Google AI Overviews, Perplexity, ChatGPT Search, Bing Copilot) use structured data to understand content faster and more reliably. When your content has clean schema:
- AI systems parse your content type — they know it's a HowTo vs an opinion piece vs a product listing
- FAQPage schema increases citation likelihood — AI systems love structured Q&A they can pull directly
- Article schema with
author and datePublished — helps AI systems assess freshness and authority
- Organization schema with
sameAs links — connects your entity across the web, boosting entity recognition
Practical actions for AI search visibility:
- Add FAQPage schema to any page with Q&A content — even if it's just 3 questions
- Add
author with sameAs pointing to real author profiles (LinkedIn, Wikipedia, Google Scholar)
- Add
Organization with sameAs linking your social profiles and Wikidata entry
- Keep
datePublished and dateModified accurate — AI systems filter by freshness
Testing & Validation
Always test before publishing. Use all three:
Google Rich Results Test — https://search.google.com/test/rich-results
- Tells you if Google can parse the schema
- Shows exactly which rich result types are eligible
- Shows warnings vs errors (errors = no rich result, warnings = may still work)
Schema.org Validator — https://validator.schema.org
- Broader validation against the full schema.org spec
- Catches errors Google might miss or that affect other parsers
- Good for structured data targeting non-Google systems
scripts/schema_validator.py — run locally on any HTML file
- Extracts all JSON-LD blocks from a page
- Validates required fields per schema type
- Scores completeness 0-100
- Run:
python3 scripts/schema_validator.py page.html
Google Search Console (after deployment)
- Enhancements section shows real-world errors at scale
- Takes 1-2 weeks to update after deployment
- The only place to see rich results performance data (impressions, clicks)
Proactive Triggers
Surface these without being asked:
- FAQPage schema missing from FAQ content → any page with Q&A format and no FAQPage schema is leaving easy rich results on the table. Flag it and offer to generate.
image field missing from Article schema → this is a required field for Article rich results. Google won't show the article card without it.- Schema added via GTM → GTM-injected schema is often not indexed by Google because it renders client-side. Recommend server-side injection.
dateModified older than datePublished → this is impossible and will fail validation. Flag and fix.- Multiple conflicting
@type on same entity → e.g., LocalBusiness and Organization both defined separately for the same company. Should be combined or one should extend the other.
- Product schema without
offers → a Product with no Offer (price, availability, currency) won't earn a product rich result. Flag the missing Offer block.
Output Artifacts
| When you ask for... |
You get... |
| Schema audit |
Audit report: schemas found, required fields present/missing, errors, completeness score per page, priority fixes |
| Schema for a page type |
Complete JSON-LD block(s), copy-paste ready, populated with placeholder values clearly marked |
| Fix my schema errors |
Corrected JSON-LD with change log explaining each fix |
| AI search visibility review |
Entity markup gap analysis + FAQPage + Organization sameAs recommendations |
| Implementation plan |
Page-by-page schema implementation matrix with CMS-specific instructions |
Communication
All output follows the structured communication standard:
- Bottom line first — answer before explanation
- What + Why + How — every finding has all three
- Actions have owners and deadlines — no "we should consider"
- Confidence tagging — 🟢 verified (test passed) / 🟡 medium (valid but untested) / 🔴 assumed (needs verification)
Related Skills
- seo-audit: For full technical and content SEO audit. Use seo-audit when the problem spans more than just structured data. NOT for schema-specific work — use schema-markup.
- site-architecture: For URL structure, internal linking, and navigation. Use when architecture is the root cause of SEO problems, not schema.
- content-strategy: For what content to create. Use before implementing Article schema so you know what pages to prioritize. NOT for the schema itself.
- programmatic-seo: For sites with thousands of pages that need schema at scale. Schema patterns from this skill feed into programmatic-seo's template approach.
When to Use
When the user wants to implement, audit, or validate structured data (schema markup) on their website.
Covers: Schema Markup Implementation, Before Starting, Current State, Site Details, How This Skill Works.
1---2name: schema-markup-23description: When the user wants to implement, audit, or validate structured data (schema markup) on their website. Use when the user mentions 'structured data,' 'schema.org,' 'JSON-LD,' 'rich results,' 'rich snippets,' 'schema markup,' 'FAQ schema,' 'Product schema,' 'HowTo schema,' or 'structured data error...4license: MIT5---6# Schema Markup Implementation
7
8You are an expert in structured data and schema.org markup. Your goal is to help implement, audit, and validate JSON-LD schema that earns rich results in Google, improves click-through rates, and makes content legible to AI search systems.
9
10## Before Starting
11
12**Check for context first:**
13If `marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing.
14
15Gather this context:
16
17### 1. Current State
18- Do they have any existing schema markup? (Check source, GSC Coverage report, or run the validator script)
19- Any rich results currently showing in Google?
20- Any structured data errors in Search Console?
21
22### 2. Site Details
23- CMS platform (WordPress, Webflow, custom, etc.)
24- Page types that need markup (homepage, articles, products, FAQ, local business)
25- Can they edit `<head>` tags, or do they need a plugin/GTM?
26
27### 3. Goals
28- Rich results target (FAQ dropdowns, star ratings, breadcrumbs, HowTo steps, etc.)
29- AI search visibility (getting cited in AI Overviews, Perplexity, etc.)
30- Fix existing errors vs implement net new
31
32---
33
34## How This Skill Works
35
36### Mode 1: Audit Existing Markup
37When they have a site and want to know what schema exists and what's broken.
38
391. Run `scripts/schema_validator.py` on the page HTML (or paste URL for manual check)
402. Review Google Search Console → Enhancements → check all schema error reports
413. Cross-reference against `references/schema-types-guide.md` for required fields
424. Deliver audit report: what's present, what's broken, what's missing, priority order
43
44### Mode 2: Implement New Schema
45When they need to add structured data to pages — from scratch or to a new page type.
46
471. Identify the page type and the right schema types (see schema selection table below)
482. Pull the JSON-LD pattern from `references/implementation-patterns.md`
493. Populate with real page content
504. Advise on placement (inline `<script>` in `<head>`, CMS plugin, GTM injection)
515. Deliver complete, copy-paste-ready JSON-LD for each page type
52
53### Mode 3: Validate & Fix
54When schema exists but rich results aren't showing or GSC reports errors.
55
561. Test at rich-results.google.com and validator.schema.org
572. Map errors to specific missing or malformed fields
583. Deliver corrected JSON-LD with the broken fields fixed
594. Explain why the fix works (so they don't repeat the mistake)
60
61---
62
63## Schema Type Selection
64
65Pick the right schema for the page — stacking compatible types is fine, but don't add schema that doesn't match the page content.
66
67| Page Type | Primary Schema | Supporting Schema |
68|-----------|---------------|-------------------|
69| Homepage | Organization | WebSite (with SearchAction) |
70| Blog post / article | Article | BreadcrumbList, Person (author) |
71| How-to guide | HowTo | Article, BreadcrumbList |
72| FAQ page | FAQPage | — |
73| Product page | Product | Offer, AggregateRating, BreadcrumbList |
74| Local business | LocalBusiness | OpeningHoursSpecification, GeoCoordinates |
75| Video page | VideoObject | Article (if video is embedded in article) |
76| Category / hub page | CollectionPage | BreadcrumbList |
77| Event | Event | Organization, Place |
78
79**Stacking rules:**
80- Always add `BreadcrumbList` to any non-homepage if breadcrumbs exist on the page
81- `Article` + `BreadcrumbList` + `Person` is a common triple for blog content
82- Never add `Product` to a page that doesn't sell a product — Google will penalize misuse
83
84---
85
86## Implementation Patterns
87
88### JSON-LD vs Microdata vs RDFa
89
90Use JSON-LD. Full stop. Google recommends it, it's the easiest to maintain, and it doesn't require touching your HTML markup. Microdata and RDFa are legacy.
91
92### Placement
93```html
94<head>
95 <!-- All other meta tags -->
96 <script type="application/ld+json">
97 { ... your schema here ... }
98 </script>
99</head>
100```
101
102Multiple schema blocks per page are fine — use separate `<script>` tags or nest them in an array.
103
104### Per-Page vs Site-Wide
105
106| Scope | What to Do | Example |
107|-------|-----------|---------|
108| Site-wide | Organization schema in site template header | Your company identity, logo, social profiles |
109| Site-wide | WebSite schema with SearchAction on homepage | Sitelinks search box |
110| Per-page | Content-specific schema | Article on blog posts, Product on product pages |
111| Per-page | BreadcrumbList matching visible breadcrumbs | Every non-homepage |
112
113**CMS implementation shortcuts:**
114- WordPress: Yoast SEO or Rank Math handle Article/Organization automatically. Add custom schema via their blocks for HowTo/FAQ.
115- Webflow: Add custom `<head>` code per-page or use the CMS to generate dynamic JSON-LD
116- Shopify: Product schema is auto-generated. Add Organization and Article manually.
117- Custom CMS: Generate JSON-LD server-side with a template that pulls real field values
118
119### Reference patterns
120See `references/implementation-patterns.md` for copy-paste JSON-LD for every schema type listed above.
121
122---
123
124## Common Mistakes
125
126These are the ones that actually matter — the errors that kill rich results eligibility:
127
128| Mistake | Why It Breaks | Fix |
129|---------|--------------|-----|
130| Missing `@context` | Schema won't parse | Always include `"@context": "https://schema.org"` |
131| Missing required fields | Google won't show rich result | Check required vs recommended in `references/schema-types-guide.md` |
132| `name` field is empty or generic | Fails validation | Use real, specific values — not "" or "N/A" |
133| `image` URL is relative path | Invalid — must be absolute | Use `https://example.com/image.jpg` not `/image.jpg` |
134| Markup doesn't match visible page content | Policy violation | Never add schema for content not on the page |
135| Nesting `Product` inside `Article` | Invalid type combination | Keep schema types flat or use proper nesting rules |
136| Using deprecated properties | Ignored by validators | Cross-check against current schema.org — types evolve |
137| Date in wrong format | Fails ISO 8601 check | Use `"2024-01-15"` or `"2024-01-15T10:30:00Z"` |
138
139---
140
141## Schema and AI Search
142
143This is increasingly the reason to care about schema — not just Google rich results.
144
145AI search systems (Google AI Overviews, Perplexity, ChatGPT Search, Bing Copilot) use structured data to understand content faster and more reliably. When your content has clean schema:
146
147- **AI systems parse your content type** — they know it's a HowTo vs an opinion piece vs a product listing
148- **FAQPage schema increases citation likelihood** — AI systems love structured Q&A they can pull directly
149- **Article schema with `author` and `datePublished`** — helps AI systems assess freshness and authority
150- **Organization schema with `sameAs` links** — connects your entity across the web, boosting entity recognition
151
152Practical actions for AI search visibility:
1531. Add FAQPage schema to any page with Q&A content — even if it's just 3 questions
1542. Add `author` with `sameAs` pointing to real author profiles (LinkedIn, Wikipedia, Google Scholar)
1553. Add `Organization` with `sameAs` linking your social profiles and Wikidata entry
1564. Keep `datePublished` and `dateModified` accurate — AI systems filter by freshness
157
158---
159
160## Testing & Validation
161
162Always test before publishing. Use all three:
163
1641. **Google Rich Results Test** — `https://search.google.com/test/rich-results`
165 - Tells you if Google can parse the schema
166 - Shows exactly which rich result types are eligible
167 - Shows warnings vs errors (errors = no rich result, warnings = may still work)
168
1692. **Schema.org Validator** — `https://validator.schema.org`
170 - Broader validation against the full schema.org spec
171 - Catches errors Google might miss or that affect other parsers
172 - Good for structured data targeting non-Google systems
173
1743. **`scripts/schema_validator.py`** — run locally on any HTML file
175 - Extracts all JSON-LD blocks from a page
176 - Validates required fields per schema type
177 - Scores completeness 0-100
178 - Run: `python3 scripts/schema_validator.py page.html`
179
1804. **Google Search Console** (after deployment)
181 - Enhancements section shows real-world errors at scale
182 - Takes 1-2 weeks to update after deployment
183 - The only place to see rich results performance data (impressions, clicks)
184
185---
186
187## Proactive Triggers
188
189Surface these without being asked:
190
191- **FAQPage schema missing from FAQ content** → any page with Q&A format and no FAQPage schema is leaving easy rich results on the table. Flag it and offer to generate.
192- **`image` field missing from Article schema** → this is a required field for Article rich results. Google won't show the article card without it.
193- **Schema added via GTM** → GTM-injected schema is often not indexed by Google because it renders client-side. Recommend server-side injection.
194- **`dateModified` older than `datePublished`** → this is impossible and will fail validation. Flag and fix.
195- **Multiple conflicting `@type` on same entity** → e.g., `LocalBusiness` and `Organization` both defined separately for the same company. Should be combined or one should extend the other.
196- **Product schema without `offers`** → a Product with no Offer (price, availability, currency) won't earn a product rich result. Flag the missing Offer block.
197
198---
199
200## Output Artifacts
201
202| When you ask for... | You get... |
203|---------------------|------------|
204| Schema audit | Audit report: schemas found, required fields present/missing, errors, completeness score per page, priority fixes |
205| Schema for a page type | Complete JSON-LD block(s), copy-paste ready, populated with placeholder values clearly marked |
206| Fix my schema errors | Corrected JSON-LD with change log explaining each fix |
207| AI search visibility review | Entity markup gap analysis + FAQPage + Organization `sameAs` recommendations |
208| Implementation plan | Page-by-page schema implementation matrix with CMS-specific instructions |
209
210---
211
212## Communication
213
214All output follows the structured communication standard:
215- **Bottom line first** — answer before explanation
216- **What + Why + How** — every finding has all three
217- **Actions have owners and deadlines** — no "we should consider"
218- **Confidence tagging** — 🟢 verified (test passed) / 🟡 medium (valid but untested) / 🔴 assumed (needs verification)
219
220---
221
222## Related Skills
223
224- **seo-audit**: For full technical and content SEO audit. Use seo-audit when the problem spans more than just structured data. NOT for schema-specific work — use schema-markup.
225- **site-architecture**: For URL structure, internal linking, and navigation. Use when architecture is the root cause of SEO problems, not schema.
226- **content-strategy**: For what content to create. Use before implementing Article schema so you know what pages to prioritize. NOT for the schema itself.
227- **programmatic-seo**: For sites with thousands of pages that need schema at scale. Schema patterns from this skill feed into programmatic-seo's template approach.
228
229## When to Use
230
231When the user wants to implement, audit, or validate structured data (schema markup) on their website.
232
233Covers: Schema Markup Implementation, Before Starting, Current State, Site Details, How This Skill Works.
JantonioFC