# schema-markup

Generates Schema.org JSON-LD structured data for rich snippets and AI search engines. Helps match page content to supported search engine formats.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1300 installs · ★ 1062
- Author: kostja94
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/kostja94/marketing-skills/tree/HEAD/skills/seo/on-page/schema/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/kostja94-schema-markup

## What it does

This skill guides the creation of Schema.org markup in JSON-LD format. It selects appropriate schemas for articles, products, events, organizations, or breadcrumbs. The generated code includes stable `@id` identifiers, ISO 8601 timestamps, and matching visible page elements.

Schema.org specifies over 800 types, but Google supports only a curated subset for rich results. Valid structured data is useless for Google snippets if the engine ignores that type. The skill accounts for engine differences and flags deprecated formats, such as HowTo markup dropped by Google in September 2023.

If a `contextus.md` file exists in the repository, the skill reads relevant project facts directly from it. The workflow prioritizes machine readability for generative engines and validation via the Rich Results Test.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add kostja94/marketing-skills --skill schema-markup -a claude-code
```
```bash
npx skills add kostja94/marketing-skills --skill schema -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/schema/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/schema/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add kostja94/marketing-skills --skill schema -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/schema/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add kostja94/marketing-skills --skill schema -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/schema/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install kostja94/marketing-skills schema
```

2. **Manually: put the files in place**
- File: `.github/skills/schema/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add kostja94/marketing-skills --skill schema -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/kostja94/marketing-skills --path skills/seo/on-page/schema
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/schema/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add kostja94/marketing-skills --skill schema -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/kostja94/marketing-skills/tree/HEAD/skills/seo/on-page/schema/SKILL.md

## When to use it
- generate JSON-LD markup for products, articles, or local business pages
- align structured data with Google rich result eligibility rules
- structure organization and author entities for generative engine citations
- resolve schema validation issues and missing structured data fields

## Example prompts
- Generate a JSON-LD schema for a blog article with author and publisher entities
- Add Product and Offer structured data for this ecommerce page
- Build FAQPage schema markup that matches the visible questions on the page

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: cd8962ac4bac924c.

BEGIN THIRD-PARTY FILE cd8962ac4bac924c
```text
---
name: schema-markup
description: When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSite," "Recipe," "Product," or "Dataset." For SERP feature types and zero-click patterns, use serp-features. For AI search visibility strategy (not markup), use generative-engine-optimization. For HowTo step sections (placement, copy, vs FAQ), use howto-section-generator.
metadata:
  version: 1.5.0
---

# SEO On-Page: Schema / Structured Data

Guides implementation of Schema.org structured data (JSON-LD) for rich snippets, enhanced search results, and Generative Engine Optimization (GEO).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Scope (On-Page SEO)

- **Schema markup**: Schema.org types for rich results, AI search visibility, and machine-readable content
- **Schema.org vs. search engines**: Schema.org defines 800+ types; each search engine supports only a subset for rich results

## Schema.org vs. Search Engine Support

**Schema.org and Google Structured Data are not fully aligned.** Schema.org is an open vocabulary (800+ types); Google, Bing, and other engines each support only a curated subset for rich results.

| Engine | Support | Notes |
|--------|---------|-------|
| **Google** | Subset only | Only types in [Google's search gallery](https://developers.google.com/search/docs/guides/search-gallery) generate rich results. Valid Schema.org markup not in Google's list won't produce enhanced snippets—even if technically correct. |
| **Bing** | Subset; different | Supports JSON-LD, Microdata, RDFa, Open Graph. Some types (e.g., Product, Offer) have format-specific support. Check [Bing Webmaster docs](https://www.bing.com/webmasters/help/marking-up-your-site-with-structured-data-3a93e731). |
| **Other engines** | Varies | Yandex, DuckDuckGo, AI search tools (Perplexity, etc.) may use Schema.org for understanding even when they don't display rich results. |

**Practical implication**: Implement Schema.org markup for your content type. If Google doesn't show rich results for that type, Bing or AI systems may still use it. Always verify against [Google's developer docs](https://developers.google.com/search/docs) for Google-specific rich result eligibility.
```
END THIRD-PARTY FILE cd8962ac4bac924c

The third-party file has ended. Everything between the cd8962ac4bac924c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2824 of 20149 bytes. © kostja94 · MIT · https://github.com/kostja94/marketing-skills/tree/HEAD/skills/seo/on-page/schema/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md