schema
Adds or fixes schema markup and structured data (JSON-LD), such as FAQ, product and review schema, for rich results.
- Kind
- Skill
- Works with
- Claude Code
- Source
- Marketing Skills (Corey Haines) @ 88c79f6528a9
- Path
- skills/schema/SKILL.md
- Jobs
- Implementation
- Topics
- SEO
Credit
- Made by
- coreyhaines31
- Original
- github.com/coreyhaines31/marketingskills/blob/88c79f6528a9347…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it with npx.
npx skills add coreyhaines31/marketingskills --skill schema
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/schema/ (the skill folder)
- 1 file(s) the skill refers to
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 88c79f6528a9
- Licence
- MIT
- Last activity
- 31 Oct 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# 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>` …