Schema
Add or fix JSON-LD and schema.org markup so product and marketing pages qualify for Google rich results.
Overview
Schema is an agent skill most often used in Launch (also Grow content refreshes) that implements accurate schema.org JSON-LD so pages can earn Google rich results.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill schemaWhat is this skill?
- Assesses page type, existing schema errors, and target rich-result types before implementation
- Implements schema.org JSON-LD aligned with accuracy and Google rich-result eligibility
- Reads `.agents/product-marketing.md` (or legacy paths) to avoid redundant intake questions
- Pairs with broader seo-audit and ai-seo skills when issues exceed markup alone
Adoption & trust: 15k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your pages rank or convert poorly because Google cannot reliably interpret your content or show rich snippets you expect.
Who is it for?
SaaS marketing sites, content blogs, and ecommerce product pages ready to add or fix JSON-LD for specific rich-result types.
Skip if: Full-site technical SEO audits, purely off-page link building, or teams with no deploy path to change page templates.
When should I use this skill?
User wants to add, fix, or optimize schema markup, JSON-LD, rich snippets, or structured data on their site.
What do I get? / Deliverables
You get validated structured data and a clear rich-results target list; escalate to seo-audit or ai-seo when broader SEO or AI-search work is needed.
- JSON-LD blocks or template patches for target page types
- Rich-results goal list tied to business value
- Notes on validation and existing-schema gaps
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Structured data is the canonical launch/SEO shelf because its primary deliverable is search-visible markup on live pages. SEO subphase covers technical on-page signals—schema is the structured-data layer beneath rankings and snippets.
Where it fits
Ship FAQ and Organization JSON-LD on a new pricing page before launch week.
Refresh article templates with Article and BreadcrumbList schema after a content push.
Add basic WebSite schema on a validation landing page to test rich-result appearance early.
How it compares
Use for structured-data implementation, not as a substitute for a full seo-audit pass or MCP analytics integrations.
Common Questions / FAQ
Who is schema for?
Solo builders and indie marketers shipping landing pages, docs, or storefronts who need JSON-LD and rich-result eligibility without hiring an SEO agency.
When should I use schema?
Use it in Launch when polishing SEO before distribution, in Grow when updating content templates, and whenever you say schema markup, JSON-LD, FAQ schema, or Google rich results.
Is schema safe to install?
Review the Security Audits panel on this Prism page and inspect the skill source in your repo before letting an agent edit production templates or inject script blocks.
SKILL.md
READMESKILL.md - Schema
# Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing schema, understand: 1. **Page Type** - What kind of page? What's the primary content? What rich results are possible? 2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing? 3. **Goals** - Which rich results are you targeting? What's the business value? --- ## Core Principles ### 1. Accuracy First - Schema must accurately represent page content - Don't markup content that doesn't exist - Keep updated when content changes ### 2. Use JSON-LD - Google recommends JSON-LD format - Easier to implement and maintain - Place in `<head>` or end of `<body>` ### 3. Follow Google's Guidelines - Only use markup Google supports - Avoid spam tactics - Review eligibility requirements ### 4. Validate Everything - Test before deploying - Monitor Search Console - Fix errors promptly --- ## Common Schema Types | Type | Use For | Required Properties | |------|---------|-------------------| | Organization | Company homepage/about | name, url | | WebSite | Homepage (search box) | name, url | | Article | Blog posts, news | headline, image, datePublished, author | | Product | Product pages | name, image, offers | | SoftwareApplication | SaaS/app pages | name, offers | | FAQPage | FAQ content | mainEntity (Q&A array) | | HowTo | Tutorials | name, step | | BreadcrumbList | Any page with breadcrumbs | itemListElement | | LocalBusiness | Local business pages | name, address | | Event | Events, webinars | name, startDate, location | **For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md) --- ## Quick Reference ### Organization (Company Page) Required: name, url Recommended: logo, sameAs (social profiles), contactPoint ### Article/BlogPosting Required: headline, image, datePublished, author Recommended: dateModified, publisher, description ### Product Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review ### FAQPage Required: mainEntity (array of Question/Answer pairs) ### BreadcrumbList Required: itemListElement (array with position, name, item) --- ## Multiple Schema Types You can combine multiple schema types on one page using `@graph`: ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", ... }, { "@type": "WebSite", ... }, { "@type": "BreadcrumbList", ... } ] } ``` --- ## Validation and Testing ### Tools - **Google Rich Results Test**: https://search.google.com/test/rich-results - **Schema.org Validator**: https://validator.schema.org/ - **Search Console**: Enhancements reports ### Common Errors **Missing required properties** - Check Google's documentation for required fields **Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact **Mismatch with page content** - Schema d