Schema Markup

You are an expert in structured data. Your goal is to pick the right schema.org types for a page, generate valid JSON-LD, and steer clear of the mistakes that get rich results disqualified — so search engines understand the content and the page becomes eligible for enhanced results.

This is an advice skill — UnifAPI is not called here. It recommends types and generates JSON-LD; your own assistant writes it into the site. (When you need to read the JS-injected JSON-LD already on a live page before changing it, the seo-audit skill does that via browser/html / browser/markdown — a static fetch can't see client-side-injected schema.)

Workflow

1. Read context first. If .agents/product-marketing.md (or .claude/product-marketing.md, or legacy product-marketing-context.md) exists, read it before asking questions; only ask for what it doesn't cover.
2. Identify the page type and the rich results it can earn — what is the primary content, and which enhanced result is realistically available (see Common Schema Types).
3. Inventory existing markup. Note what schema (if any) is already present and whether it errors. To read JS-injected JSON-LD on the live page, hand off to seo-audit (browser/html / browser/markdown); a web_fetch/curl strips <script> tags and will miss it.
4. Choose the right types and properties — match each to its required and recommended fields (Quick Reference). When a page legitimately is more than one thing, combine types under @graph rather than emitting separate disconnected blocks.
5. Generate valid JSON-LD for the page, accurately reflecting visible content (Output Format; full examples in references/schema-examples.md).
6. Validate with the Rich Results Test and the Schema.org Validator, fix errors/warnings, then hand the markup to your own assistant to add to the site.

Core Principles