[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M797NETF01C49ZW9W6JGFCK3":3,"skill-same:01M797NETF01C49ZW9W6JGFCK3":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M797NETF01C49ZW9W6JGFCK3","schema-markup-generator",null,"Generate Schema.org JSON-LD structured data for FAQ, HowTo, Article, Product, LocalBusiness, and 6 other types targeting rich results. Use when the user asks to \"add schema markup\", \"generate structured data\", \"JSON-LD\", \"FAQ schema\", \"rich snippets\", \"I want star ratings in Google\", or \"structured data validation errors\". Produces validated markup targeting Google Rich Results, Bing structured data, and AI system understanding. Validates against Google Rich Results Test requirements. For broader technical SEO, see technical-seo-checker. For meta tag optimization, see meta-tags-optimizer.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fschema-markup-generator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: schema-markup-generator\nversion: \"4.0.0\"\ndescription: 'Generate Schema.org JSON-LD structured data for FAQ, HowTo, Article, Product, LocalBusiness, and 6 other types targeting rich results. Use when the user asks to \"add schema markup\", \"generate structured data\", \"JSON-LD\", \"FAQ schema\", \"rich snippets\", \"I want star ratings in Google\", or \"structured data validation errors\". Produces validated markup targeting Google Rich Results, Bing structured data, and AI system understanding. Validates against Google Rich Results Test requirements. For broader technical SEO, see technical-seo-checker. For meta tag optimization, see meta-tags-optimizer.'\nlicense: Apache-2.0\ncompatibility: \"Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations.\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\"\nallowed-tools: WebFetch\nmetadata:\n  author: aaron-he-zhu\n  version: \"4.0.0\"\n  geo-relevance: \"medium\"\n  tags:\n    - seo\n    - structured-data\n    - json-ld\n    - rich-results\n    - rich-snippets\n    - faq-schema\n    - howto-schema\n    - product-schema\n    - article-schema\n    - localbusiness-schema\n    - schema-org\n  triggers:\n    - \"add schema markup\"\n    - \"generate structured data\"\n    - \"JSON-LD\"\n    - \"rich snippets\"\n    - \"FAQ schema\"\n    - \"schema.org\"\n    - \"structured data markup\"\n    - \"add FAQ rich results\"\n    - \"I want star ratings in Google\"\n    - \"product markup\"\n    - \"recipe schema\"\n---\n\n# Schema Markup Generator\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n\n\u003Cdetails>\n\u003Csummary>Browse all 20 skills\u003C\u002Fsummary>\n\n**Research** · [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) · [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) · [serp-analysis](..\u002F..\u002Fresearch\u002Fserp-analysis\u002F) · [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F)\n\n**Build** · [seo-content-writer](..\u002Fseo-content-writer\u002F) · [geo-content-optimizer](..\u002Fgeo-content-optimizer\u002F) · [meta-tags-optimizer](..\u002Fmeta-tags-optimizer\u002F) · **schema-markup-generator**\n\n**Optimize** · [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) · [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) · [internal-linking-optimizer](..\u002F..\u002Foptimize\u002Finternal-linking-optimizer\u002F) · [content-refresher](..\u002F..\u002Foptimize\u002Fcontent-refresher\u002F)\n\n**Monitor** · [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) · [backlink-analyzer](..\u002F..\u002Fmonitor\u002Fbacklink-analyzer\u002F) · [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) · [alert-manager](..\u002F..\u002Fmonitor\u002Falert-manager\u002F)\n\n**Cross-cutting** · [content-quality-auditor](..\u002F..\u002Fcross-cutting\u002Fcontent-quality-auditor\u002F) · [domain-authority-auditor](..\u002F..\u002Fcross-cutting\u002Fdomain-authority-auditor\u002F) · [entity-optimizer](..\u002F..\u002Fcross-cutting\u002Fentity-optimizer\u002F) · [memory-management](..\u002F..\u002Fcross-cutting\u002Fmemory-management\u002F)\n\n\u003C\u002Fdetails>\n\nThis skill creates Schema.org structured data markup in JSON-LD format to help search engines understand your content and enable rich results in SERPs.\n\n## When to Use This Skill\n\n- Adding FAQ schema for expanded SERP presence\n- Creating How-To schema for step-by-step content\n- Adding Product schema for e-commerce pages\n- Implementing Article schema for blog posts\n- Adding Local Business schema for location pages\n- Creating Review\u002FRating schema\n- Implementing Organization schema for brand presence\n- Any page where rich results would improve visibility\n\n## What This Skill Does\n\n1. **Schema Type Selection**: Recommends appropriate schema types\n2. **JSON-LD Generation**: Creates valid structured data markup\n3. **Property Mapping**: Maps your content to schema properties\n4. **Validation Guidance**: Ensures schema meets requirements\n5. **Nested Schema**: Handles complex, multi-type schemas\n6. **Rich Result Eligibility**: Identifies which rich results you can target\n\n## How to Use\n\n### Generate Schema for Content\n\n```\nGenerate schema markup for this [content type]: [content\u002FURL]\n```\n\n```\nCreate FAQ schema for these questions and answers: [Q&A list]\n```\n\n### Specific Schema Types\n\n```\nCreate Product schema for [product name] with [details]\n```\n\n```\nGenerate LocalBusiness schema for [business name and details]\n```\n\n### Audit Existing Schema\n\n```\nReview and improve this schema markup: [existing schema]\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~web crawler connected:**\nAutomatically crawl and extract page content (visible text, headings, lists, tables), existing schema markup, page metadata, and structured content elements that map to schema properties.\n\n**With manual data only:**\nAsk the user to provide:\n1. Page URL or full HTML content\n2. Page type (article, product, FAQ, how-to, local business, etc.)\n3. Specific data needed for schema (prices, dates, author info, Q&A pairs, etc.)\n4. Current schema markup (if optimizing existing)\n\nProceed with the full workflow using provided data. Note in the output which data is from automated extraction vs. user-provided data.\n\n## Instructions\n\nWhen a user requests schema markup:\n\n1. **Identify Content Type and Rich Result Opportunity**\n\n   Reference the [CORE-EEAT Benchmark](..\u002F..\u002Freferences\u002Fcore-eeat-benchmark.md) item **O05 (Schema Markup)** for content-type to schema mapping:\n\n   ```markdown\n   ### CORE-EEAT Schema Mapping (O05)\n\n   | Content Type | Required Schema | Conditional Schema |\n   |-------------|----------------|--------------------|\n   | Blog (guides) | Article, Breadcrumb | FAQ, HowTo |\n   | Blog (tools) | Article, Breadcrumb | FAQ, Review |\n   | Blog (insights) | Article, Breadcrumb | FAQ |\n   | Alternative | Comparison*, Breadcrumb, FAQ | AggregateRating |\n   | Best-of | ItemList, Breadcrumb, FAQ | AggregateRating per tool |\n   | Use-case | WebPage, Breadcrumb, FAQ | — |\n   | FAQ | FAQPage, Breadcrumb | — |\n   | Landing | SoftwareApplication, Breadcrumb, FAQ | WebPage |\n   | Testimonial | Review, Breadcrumb | FAQ, Person |\n\n   *Use the mapping above to ensure schema type matches content type (CORE-EEAT O05: Pass criteria).*\n   ```\n\n   ```markdown\n   ### Schema Analysis\n\n   **Content Type**: [blog\u002Fproduct\u002FFAQ\u002Fhow-to\u002Flocal business\u002Fetc.]\n   **Page URL**: [URL]\n\n   **Eligible Rich Results**:\n   \n   | Rich Result Type | Eligibility | Impact |\n   |------------------|-------------|--------|\n   | FAQ | ✅\u002F❌ | High - Expands SERP presence |\n   | How-To | ✅\u002F❌ | Medium - Shows steps in SERP |\n   | Product | ✅\u002F❌ | High - Shows price, availability |\n   | Review | ✅\u002F❌ | High - Shows star ratings |\n   | Article | ✅\u002F❌ | Medium - Shows publish date, author |\n   | Breadcrumb | ✅\u002F❌ | Medium - Shows navigation path |\n   | Video | ✅\u002F❌ | High - Shows video thumbnail |\n   \n   **Recommended Schema Types**:\n   1. [Primary schema type] - [reason]\n   2. [Secondary schema type] - [reason]\n   ```\n\n2. **Generate Schema Markup**\n\n   Based on the identified content type, generate the appropriate JSON-LD schema. Supported types: FAQPage, HowTo, Article\u002FBlogPosting\u002FNewsArticle, Product, LocalBusiness, Organization, BreadcrumbList, Event, Recipe, and combined multi-type schemas.\n\n   > **Reference**: See [references\u002Fschema-templates.md](.\u002Freferences\u002Fschema-templates.md) for complete, copy-ready JSON-LD templates for all schema types with required and optional properties.\n\n   For each schema generated, include:\n   - All required properties for the chosen type\n   - Rich result preview showing expected SERP appearance\n   - Notes on which properties are required vs. optional\n\n   When combining multiple schema types on one page, wrap them in a JSON array inside a single `\u003Cscript type=\"application\u002Fld+json\">` tag.\n\n3. **Provide Implementation and Validation**\n\n    ```markdown\n    ## Implementation Guide\n\n    ### Adding Schema to Your Page\n\n    **Option 1: In HTML \u003Chead>**\n    ```html\n    \u003Chead>\n      \u003Cscript type=\"application\u002Fld+json\">\n        [Your JSON-LD schema here]\n      \u003C\u002Fscript>\n    \u003C\u002Fhead>\n    ```\n\n    **Option 2: Before closing \u003C\u002Fbody>**\n    ```html\n      \u003Cscript type=\"application\u002Fld+json\">\n        [Your JSON-LD schema here]\n      \u003C\u002Fscript>\n    \u003C\u002Fbody>\n    ```\n\n    ### Validation Steps\n\n    1. **~~schema validator**\n       - Test your live URL or paste code\n       - Check for errors and warnings\n\n    2. **Schema.org Validator**\n       - URL: https:\u002F\u002Fvalidator.schema.org\u002F\n       - Validates against Schema.org spec\n\n    3. **~~search console**\n       - Monitor rich results in ~~search console\n       - Check Enhancements reports for issues\n\n    ### Validation Checklist\n\n    - [ ] JSON syntax is valid (no trailing commas)\n    - [ ] All required properties present\n    - [ ] URLs are absolute, not relative\n    - [ ] Dates are in ISO 8601 format\n    - [ ] Content matches visible page content\n    - [ ] No policy violations\n    ```\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Page URL or content provided\n- [ ] Schema type appropriate for content (Article for blog, Product for e-commerce, etc.)\n- [ ] All required data available (author, dates, prices, etc. depending on schema type)\n- [ ] Content eligibility for rich results confirmed\n\n### Output Validation\n- [ ] JSON syntax validates (no trailing commas, proper quotes)\n- [ ] All required properties present for chosen schema type\n- [ ] URLs are absolute, not relative\n- [ ] Dates in ISO 8601 format (YYYY-MM-DDTHH:MM:SS+00:00)\n- [ ] Schema content matches visible page content exactly\n- [ ] Passes ~~schema validator with no errors\n- [ ] Source of each data point clearly stated (~~web crawler extraction, user-provided, or manual entry)\n\n## Example\n\n**User**: \"Generate FAQ schema for a page about SEO with 3 questions\"\n\n**Output**:\n\n```markdown\n## FAQ Schema for SEO Page\n\n### Schema Markup\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is SEO?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO (Search Engine Optimization) is the practice of optimizing websites and content to rank higher in search engine results pages (SERPs). It involves technical optimizations, content creation, and link building to increase organic visibility and drive qualified traffic to your website.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How long does SEO take to work?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO typically takes 3-6 months to show significant results, though this varies based on competition, domain authority, and effort invested. New websites may take 6-12 months, while established sites with existing authority can see improvements in 1-3 months for less competitive keywords.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is SEO better than paid advertising?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO and paid advertising serve different purposes. SEO provides sustainable, long-term traffic without per-click costs but takes time to build. Paid advertising delivers immediate results but stops when you stop paying. Most successful businesses use both: paid ads for immediate leads and SEO for long-term growth.\"\n      }\n    }\n  ]\n}\n```\n\n_Implementation: Wrap the above JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">...\u003C\u002Fscript>` and place in `\u003Chead>` or before `\u003C\u002Fbody>`. Test with ~~schema validator._\n\n### SERP Preview\n\n```\nSEO Guide: Complete Beginner's Tutorial\nyoursite.com\u002Fseo-guide\u002F\nLearn SEO from scratch with our comprehensive guide...\n\n▼ What is SEO?\n  SEO (Search Engine Optimization) is the practice of optimizing...\n▼ How long does SEO take to work?\n  SEO typically takes 3-6 months to show significant results...\n▼ Is SEO better than paid advertising?\n  SEO and paid advertising serve different purposes...\n```\n```\n\n## Schema Type Quick Reference\n\n| Content Type | Schema Type | Key Properties |\n|--------------|-------------|----------------|\n| Blog Post | BlogPosting\u002FArticle | headline, datePublished, author |\n| Product | Product | name, price, availability |\n| FAQ | FAQPage | Question, Answer |\n| How-To | HowTo | step, totalTime |\n| Local Business | LocalBusiness | address, geo, openingHours |\n| Recipe | Recipe | ingredients, cookTime |\n| Event | Event | startDate, location |\n| Video | VideoObject | uploadDate, duration |\n| Course | Course | provider, name |\n| Review | Review | itemReviewed, ratingValue |\n\n## Tips for Success\n\n1. **Match visible content** - Schema must reflect what users see\n2. **Don't spam** - Only add schema for relevant content\n3. **Keep updated** - Update dates and prices when they change\n4. **Test thoroughly** - Validate before deploying\n5. **Monitor Search Console** - Watch for errors and warnings\n\n## Schema Type Decision Tree\n\n> **Reference**: See [references\u002Fschema-decision-tree.md](.\u002Freferences\u002Fschema-decision-tree.md) for the full decision tree (content-to-schema mapping), industry-specific recommendations, implementation priority tiers (P0-P4), and validation quick reference.\n\n## Reference Materials\n\n- [Schema Templates](.\u002Freferences\u002Fschema-templates.md) - Copy-ready JSON-LD templates for all schema types\n- [Validation Guide](.\u002Freferences\u002Fvalidation-guide.md) - Common errors, required properties, testing workflow\n\n## Related Skills\n\n- [seo-content-writer](..\u002Fseo-content-writer\u002F) — Create content worth marking up\n- [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) — Audit existing schema\n- [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) — Technical validation\n- [entity-optimizer](..\u002F..\u002Fcross-cutting\u002Fentity-optimizer\u002F) — Entity audit informs Organization, Person, Product schema\n\n","# Schema Markup Generator\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n\n\u003Cdetails>\n\u003Csummary>Browse all 20 skills\u003C\u002Fsummary>\n\n**Research** · [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) · [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) · [serp-analysis](..\u002F..\u002Fresearch\u002Fserp-analysis\u002F) · [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F)\n\n**Build** · [seo-content-writer](..\u002Fseo-content-writer\u002F) · [geo-content-optimizer](..\u002Fgeo-content-optimizer\u002F) · [meta-tags-optimizer](..\u002Fmeta-tags-optimizer\u002F) · **schema-markup-generator**\n\n**Optimize** · [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) · [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) · [internal-linking-optimizer](..\u002F..\u002Foptimize\u002Finternal-linking-optimizer\u002F) · [content-refresher](..\u002F..\u002Foptimize\u002Fcontent-refresher\u002F)\n\n**Monitor** · [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) · [backlink-analyzer](..\u002F..\u002Fmonitor\u002Fbacklink-analyzer\u002F) · [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) · [alert-manager](..\u002F..\u002Fmonitor\u002Falert-manager\u002F)\n\n**Cross-cutting** · [content-quality-auditor](..\u002F..\u002Fcross-cutting\u002Fcontent-quality-auditor\u002F) · [domain-authority-auditor](..\u002F..\u002Fcross-cutting\u002Fdomain-authority-auditor\u002F) · [entity-optimizer](..\u002F..\u002Fcross-cutting\u002Fentity-optimizer\u002F) · [memory-management](..\u002F..\u002Fcross-cutting\u002Fmemory-management\u002F)\n\n\u003C\u002Fdetails>\n\nThis skill creates Schema.org structured data markup in JSON-LD format to help search engines understand your content and enable rich results in SERPs.\n\n## When to Use This Skill\n\n- Adding FAQ schema for expanded SERP presence\n- Creating How-To schema for step-by-step content\n- Adding Product schema for e-commerce pages\n- Implementing Article schema for blog posts\n- Adding Local Business schema for location pages\n- Creating Review\u002FRating schema\n- Implementing Organization schema for brand presence\n- Any page where rich results would improve visibility\n\n## What This Skill Does\n\n1. **Schema Type Selection**: Recommends appropriate schema types\n2. **JSON-LD Generation**: Creates valid structured data markup\n3. **Property Mapping**: Maps your content to schema properties\n4. **Validation Guidance**: Ensures schema meets requirements\n5. **Nested Schema**: Handles complex, multi-type schemas\n6. **Rich Result Eligibility**: Identifies which rich results you can target\n\n## How to Use\n\n### Generate Schema for Content\n\n```\nGenerate schema markup for this [content type]: [content\u002FURL]\n```\n\n```\nCreate FAQ schema for these questions and answers: [Q&A list]\n```\n\n### Specific Schema Types\n\n```\nCreate Product schema for [product name] with [details]\n```\n\n```\nGenerate LocalBusiness schema for [business name and details]\n```\n\n### Audit Existing Schema\n\n```\nReview and improve this schema markup: [existing schema]\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~web crawler connected:**\nAutomatically crawl and extract page content (visible text, headings, lists, tables), existing schema markup, page metadata, and structured content elements that map to schema properties.\n\n**With manual data only:**\nAsk the user to provide:\n1. Page URL or full HTML content\n2. Page type (article, product, FAQ, how-to, local business, etc.)\n3. Specific data needed for schema (prices, dates, author info, Q&A pairs, etc.)\n4. Current schema markup (if optimizing existing)\n\nProceed with the full workflow using provided data. Note in the output which data is from automated extraction vs. user-provided data.\n\n## Instructions\n\nWhen a user requests schema markup:\n\n1. **Identify Content Type and Rich Result Opportunity**\n\n   Reference the [CORE-EEAT Benchmark](..\u002F..\u002Freferences\u002Fcore-eeat-benchmark.md) item **O05 (Schema Markup)** for content-type to schema mapping:\n\n   ```markdown\n   ### CORE-EEAT Schema Mapping (O05)\n\n   | Content Type | Required Schema | Conditional Schema |\n   |-------------|----------------|--------------------|\n   | Blog (guides) | Article, Breadcrumb | FAQ, HowTo |\n   | Blog (tools) | Article, Breadcrumb | FAQ, Review |\n   | Blog (insights) | Article, Breadcrumb | FAQ |\n   | Alternative | Comparison*, Breadcrumb, FAQ | AggregateRating |\n   | Best-of | ItemList, Breadcrumb, FAQ | AggregateRating per tool |\n   | Use-case | WebPage, Breadcrumb, FAQ | — |\n   | FAQ | FAQPage, Breadcrumb | — |\n   | Landing | SoftwareApplication, Breadcrumb, FAQ | WebPage |\n   | Testimonial | Review, Breadcrumb | FAQ, Person |\n\n   *Use the mapping above to ensure schema type matches content type (CORE-EEAT O05: Pass criteria).*\n   ```\n\n   ```markdown\n   ### Schema Analysis\n\n   **Content Type**: [blog\u002Fproduct\u002FFAQ\u002Fhow-to\u002Flocal business\u002Fetc.]\n   **Page URL**: [URL]\n\n   **Eligible Rich Results**:\n   \n   | Rich Result Type | Eligibility | Impact |\n   |------------------|-------------|--------|\n   | FAQ | ✅\u002F❌ | High - Expands SERP presence |\n   | How-To | ✅\u002F❌ | Medium - Shows steps in SERP |\n   | Product | ✅\u002F❌ | High - Shows price, availability |\n   | Review | ✅\u002F❌ | High - Shows star ratings |\n   | Article | ✅\u002F❌ | Medium - Shows publish date, author |\n   | Breadcrumb | ✅\u002F❌ | Medium - Shows navigation path |\n   | Video | ✅\u002F❌ | High - Shows video thumbnail |\n   \n   **Recommended Schema Types**:\n   1. [Primary schema type] - [reason]\n   2. [Secondary schema type] - [reason]\n   ```\n\n2. **Generate Schema Markup**\n\n   Based on the identified content type, generate the appropriate JSON-LD schema. Supported types: FAQPage, HowTo, Article\u002FBlogPosting\u002FNewsArticle, Product, LocalBusiness, Organization, BreadcrumbList, Event, Recipe, and combined multi-type schemas.\n\n   > **Reference**: See [references\u002Fschema-templates.md](.\u002Freferences\u002Fschema-templates.md) for complete, copy-ready JSON-LD templates for all schema types with required and optional properties.\n\n   For each schema generated, include:\n   - All required properties for the chosen type\n   - Rich result preview showing expected SERP appearance\n   - Notes on which properties are required vs. optional\n\n   When combining multiple schema types on one page, wrap them in a JSON array inside a single `\u003Cscript type=\"application\u002Fld+json\">` tag.\n\n3. **Provide Implementation and Validation**\n\n    ```markdown\n    ## Implementation Guide\n\n    ### Adding Schema to Your Page\n\n    **Option 1: In HTML \u003Chead>**\n    ```html\n    \u003Chead>\n      \u003Cscript type=\"application\u002Fld+json\">\n        [Your JSON-LD schema here]\n      \u003C\u002Fscript>\n    \u003C\u002Fhead>\n    ```\n\n    **Option 2: Before closing \u003C\u002Fbody>**\n    ```html\n      \u003Cscript type=\"application\u002Fld+json\">\n        [Your JSON-LD schema here]\n      \u003C\u002Fscript>\n    \u003C\u002Fbody>\n    ```\n\n    ### Validation Steps\n\n    1. **~~schema validator**\n       - Test your live URL or paste code\n       - Check for errors and warnings\n\n    2. **Schema.org Validator**\n       - URL: https:\u002F\u002Fvalidator.schema.org\u002F\n       - Validates against Schema.org spec\n\n    3. **~~search console**\n       - Monitor rich results in ~~search console\n       - Check Enhancements reports for issues\n\n    ### Validation Checklist\n\n    - [ ] JSON syntax is valid (no trailing commas)\n    - [ ] All required properties present\n    - [ ] URLs are absolute, not relative\n    - [ ] Dates are in ISO 8601 format\n    - [ ] Content matches visible page content\n    - [ ] No policy violations\n    ```\n\n## Validation Checkpoints\n\n### Input Validation\n- [ ] Page URL or content provided\n- [ ] Schema type appropriate for content (Article for blog, Product for e-commerce, etc.)\n- [ ] All required data available (author, dates, prices, etc. depending on schema type)\n- [ ] Content eligibility for rich results confirmed\n\n### Output Validation\n- [ ] JSON syntax validates (no trailing commas, proper quotes)\n- [ ] All required properties present for chosen schema type\n- [ ] URLs are absolute, not relative\n- [ ] Dates in ISO 8601 format (YYYY-MM-DDTHH:MM:SS+00:00)\n- [ ] Schema content matches visible page content exactly\n- [ ] Passes ~~schema validator with no errors\n- [ ] Source of each data point clearly stated (~~web crawler extraction, user-provided, or manual entry)\n\n## Example\n\n**User**: \"Generate FAQ schema for a page about SEO with 3 questions\"\n\n**Output**:\n\n```markdown\n## FAQ Schema for SEO Page\n\n### Schema Markup\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is SEO?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO (Search Engine Optimization) is the practice of optimizing websites and content to rank higher in search engine results pages (SERPs). It involves technical optimizations, content creation, and link building to increase organic visibility and drive qualified traffic to your website.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How long does SEO take to work?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO typically takes 3-6 months to show significant results, though this varies based on competition, domain authority, and effort invested. New websites may take 6-12 months, while established sites with existing authority can see improvements in 1-3 months for less competitive keywords.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is SEO better than paid advertising?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"SEO and paid advertising serve different purposes. SEO provides sustainable, long-term traffic without per-click costs but takes time to build. Paid advertising delivers immediate results but stops when you stop paying. Most successful businesses use both: paid ads for immediate leads and SEO for long-term growth.\"\n      }\n    }\n  ]\n}\n```\n\n_Implementation: Wrap the above JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">...\u003C\u002Fscript>` and place in `\u003Chead>` or before `\u003C\u002Fbody>`. Test with ~~schema validator._\n\n### SERP Preview\n\n```\nSEO Guide: Complete Beginner's Tutorial\nyoursite.com\u002Fseo-guide\u002F\nLearn SEO from scratch with our comprehensive guide...\n\n▼ What is SEO?\n  SEO (Search Engine Optimization) is the practice of optimizing...\n▼ How long does SEO take to work?\n  SEO typically takes 3-6 months to show significant results...\n▼ Is SEO better than paid advertising?\n  SEO and paid advertising serve different purposes...\n```\n```\n\n## Schema Type Quick Reference\n\n| Content Type | Schema Type | Key Properties |\n|--------------|-------------|----------------|\n| Blog Post | BlogPosting\u002FArticle | headline, datePublished, author |\n| Product | Product | name, price, availability |\n| FAQ | FAQPage | Question, Answer |\n| How-To | HowTo | step, totalTime |\n| Local Business | LocalBusiness | address, geo, openingHours |\n| Recipe | Recipe | ingredients, cookTime |\n| Event | Event | startDate, location |\n| Video | VideoObject | uploadDate, duration |\n| Course | Course | provider, name |\n| Review | Review | itemReviewed, ratingValue |\n\n## Tips for Success\n\n1. **Match visible content** - Schema must reflect what users see\n2. **Don't spam** - Only add schema for relevant content\n3. **Keep updated** - Update dates and prices when they change\n4. **Test thoroughly** - Validate before deploying\n5. **Monitor Search Console** - Watch for errors and warnings\n\n## Schema Type Decision Tree\n\n> **Reference**: See [references\u002Fschema-decision-tree.md](.\u002Freferences\u002Fschema-decision-tree.md) for the full decision tree (content-to-schema mapping), industry-specific recommendations, implementation priority tiers (P0-P4), and validation quick reference.\n\n## Reference Materials\n\n- [Schema Templates](.\u002Freferences\u002Fschema-templates.md) - Copy-ready JSON-LD templates for all schema types\n- [Validation Guide](.\u002Freferences\u002Fvalidation-guide.md) - Common errors, required properties, testing workflow\n\n## Related Skills\n\n- [seo-content-writer](..\u002Fseo-content-writer\u002F) — Create content worth marking up\n- [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) — Audit existing schema\n- [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) — Technical validation\n- [entity-optimizer](..\u002F..\u002Fcross-cutting\u002Fentity-optimizer\u002F) — Entity audit informs Organization, Person, Product schema\n\n",{"name":5,"license":15,"version":24,"homepage":25,"metadata":26,"description":7,"allowed-tools":53,"compatibility":54},"4.0.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills",{"tags":27,"author":39,"version":24,"triggers":40,"geo-relevance":52},[28,29,30,31,32,33,34,35,36,37,38],"seo","structured-data","json-ld","rich-results","rich-snippets","faq-schema","howto-schema","product-schema","article-schema","localbusiness-schema","schema-org","aaron-he-zhu",[41,42,43,44,45,46,47,48,49,50,51],"add schema markup","generate structured data","JSON-LD","rich snippets","FAQ schema","schema.org","structured data markup","add FAQ rich results","I want star ratings in Google","product markup","recipe schema","medium","WebFetch","Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations.","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fschema-markup-generator",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill schema-markup-generator",{"tool":70,"command":71},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill schema-markup-generator",{"tool":73,"command":74},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill schema-markup-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fschema-markup-generator\u002FSKILL.md",true,[78,84,88],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fschema-decision-tree.md","REFERENCE","参考文档",3333,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fschema-markup-generator\u002Freferences\u002Fschema-decision-tree.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fschema-templates.md",14832,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fschema-markup-generator\u002Freferences\u002Fschema-templates.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fvalidation-guide.md",12412,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fschema-markup-generator\u002Freferences\u002Fvalidation-guide.md",[93,101,108,115,122,130],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]