Schema Architect

Design and implement Schema.org structured data for maximum AI visibility and rich search results.

Related: Use llms-txt-builder skill for AI navigation files.

Schema Priority Matrix

High-Impact (Implement First):

Schema Type	Use Case	AI Benefit	Rich Result
`Organization` + `WebSite`	Company info	Entity recognition	Sitelinks search box
`FAQPage`	Q&A content	Direct answer extraction	FAQ dropdowns
`HowTo`	Tutorials/guides	Step extraction	Step-by-step snippet
`Article/BlogPosting`	Blog content	Content attribution	Article carousel
`Product` + `Offer`	Pricing/e-commerce	Product info extraction	Price in search
`AggregateRating`	Reviews/testimonials	Trust signals	Star ratings
`BreadcrumbList`	Navigation	Site structure	Breadcrumb trail

Medium-Impact: Person, LocalBusiness, Event, Course, SoftwareApplication

Site Archetype Mappings

See references/site-archetypes.yaml for page-to-schema mappings per site type (SaaS, e-commerce, agency, blog, docs).

Implementation Templates

See references/schema-templates.yaml for JSON-LD code snippets:

Organization schema
FAQPage schema
HowTo schema
Article schema
Product schema

Multimodal Structured Data

Include media references:

Image objects with alt descriptions
Video objects with transcripts
Audio references where applicable

Workflow

Audit existing structured data
Identify missing high-impact schemas
Map content types to schema types
Generate JSON-LD code
Validate with testing tools
Plan maintenance schedule

Output Format

Schema Implementation Plan
--------------------------
Current Coverage: X/10
Target Coverage: Y/10

Priority Implementations:
1. Organization schema (homepage)
2. FAQPage schema (support pages)
3. Article schema (blog posts)
4. HowTo schema (tutorials)

Validation:
- Rich Results Test: [Pass/Fail]
- Schema.org Validator: [Pass/Fail]

Validation Tools

Google Rich Results Test
Schema.org Validator
Structured Data Linter

Platform Integration

Platform	Approach
WordPress	Yoast/RankMath schema settings
Next.js	next-seo configuration
Astro	schema components
Static	JSON-LD in `<head>`

schema-architect