Skill

schema

Generates and validates JSON-LD schema.org markup for rich search results, covering types like FAQ, product, review, breadcrumb, and more. Helps pages earn enhanced Google results.

frontend

npx claudepluginhub unifapi-agent/agents --plugin unifapi

Popularity

Stars

486

Forks

102

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/unifapi:schema

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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.

Supporting Files

README.mdreferences/schema-examples.md

SKILL.md

132 lines · ~2.1k tokens

Similar Skills

schema

32.9k

Adds, fixes, and optimizes schema.org structured data markup (JSON-LD) for rich search results in Google and other search engines. Includes validation and best practices.

2 files

marketing-skills

memstack-seo-schema-markup

363

Generates valid JSON-LD schema.org structured data for rich results. Identifies applicable schema types, creates JSON-LD blocks, and verifies against Google's Rich Results requirements.

1 file

memstack

schema

Implements and validates schema.org structured data in JSON-LD format for rich search results. Activated by schema markup, structured data, JSON-LD, rich snippets, and related terms.

2 files

craft-workspace-webconsulting-skills

Stats

Stars486

Forks102

MaintenanceExcellent

Last CommitJun 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Schema Markup

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

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.
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).
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.
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.
Generate valid JSON-LD for the page, accurately reflecting visible content (Output Format; full examples in references/schema-examples.md).
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

Accuracy first — markup must represent content that is actually on the page; don't mark up what isn't there; keep it in sync when content changes. Mismatched schema gets rich results revoked.
Use JSON-LD — Google's recommended format; easiest to maintain. Place it in <head> or at the end of <body>.
Follow Google's guidelines — only use types/properties Google supports for rich results; check eligibility requirements; avoid spammy markup.
Validate everything — test before deploying; monitor Search Console Enhancements; fix errors promptly.

Common Schema Types

Type	Use For	Required Properties
Organization	Company homepage/about	name, url
WebSite	Homepage (sitelinks search)	name, url
Article/BlogPosting	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

Full JSON-LD for each is in references/schema-examples.md.

Quick Reference (required + recommended)

Organization — req: name, url · rec: logo, sameAs (social profiles), contactPoint
Article/BlogPosting — req: headline, image, datePublished, author · rec: dateModified, publisher, description
Product — req: name, image, offers (price + availability) · rec: sku, brand, aggregateRating, review
SoftwareApplication — req: name, offers · rec: applicationCategory, operatingSystem, aggregateRating
FAQPage — req: mainEntity (array of Question/Answer) · only for genuine, visible Q&A
BreadcrumbList — req: itemListElement (each with position, name, item)

Multiple Schema Types (`@graph`)

When a page is legitimately several things at once (e.g. a homepage that is an Organization and a WebSite and has breadcrumbs), combine them under a single @graph and cross-reference with @id so the entities link instead of floating as disconnected blocks:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", "@id": "https://example.com/#org", "name": "...", "url": "..." },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "...",
      "publisher": { "@id": "https://example.com/#org" }
    },
    { "@type": "BreadcrumbList", "itemListElement": [] }
  ]
}

Validation and Testing

Google Rich Results Test — https://search.google.com/test/rich-results (renders JavaScript; catches eligibility issues)
Schema.org Validator — https://validator.schema.org/
Search Console — Enhancements reports (post-deploy monitoring)

Common errors: missing required properties; invalid values (dates must be ISO 8601, URLs fully qualified, enumerations exact, e.g. https://schema.org/InStock); markup that doesn't match the visible page content.

Implementation Notes

Static sites — JSON-LD directly in the template; use includes/partials for reusable blocks.
Dynamic (React/Next.js) — a component that serializes data to JSON-LD, server-side rendered. See the Next.js example in the reference.
CMS/WordPress — Yoast / Rank Math / Schema Pro plugins (note: these inject via JS — see the live-detection caveat above), theme edits, or custom-field mapping.

Output Format

Return the JSON-LD block plus a testing checklist.

{
  "@context": "https://schema.org",
  "@type": "...",
  "// complete, valid markup populated from the actual page": "..."
}

Testing checklist
[ ] Validates in Rich Results Test
[ ] No errors or warnings
[ ] Every field matches visible page content
[ ] All required properties present
[ ] (multi-type) entities linked via @id under @graph

Guardrails

Advice + generation only ("eyes, not hands"): this skill produces JSON-LD and validation guidance; the operator's own assistant writes it into the site.
Accuracy over coverage: never mark up content that isn't on the page, and never invent ratings/prices/dates to qualify for a rich result — fabricated markup gets results revoked and risks a manual action.
Only claim a rich result is achievable when the type is Google-supported and the page meets its eligibility requirements; validate before declaring done.

References

references/schema-examples.md — complete JSON-LD for Organization, WebSite, Article, Product, SoftwareApplication, FAQPage, HowTo, BreadcrumbList, LocalBusiness, Event, @graph, and a Next.js implementation.

Related Skills

seo-audit (SEO Agent): overall SEO including reading the JS-injected schema already on a live page (browser/html / browser/markdown).
ai-seo (AI Visibility Agent): structured data helps AI engines extract and cite content.
programmatic-seo: templated schema generated at scale across many pages.
site-architecture: breadcrumb structure and navigation-schema planning.
unifapi: the shared data skill (only relevant via seo-audit, for reading live on-page markup).

schema

Popularity

Invocation

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

schema

Popularity

Invocation

Context Preview

Supporting Files

SKILL.md

Schema Markup

Workflow

Core Principles

Common Schema Types

Quick Reference (required + recommended)

Multiple Schema Types (@graph)

Validation and Testing

Implementation Notes

Output Format

Guardrails

References

Related Skills

Similar Skills

Help us improve

Schema Markup

Workflow

Core Principles

Common Schema Types

Quick Reference (required + recommended)

Multiple Schema Types (@graph)

Validation and Testing

Implementation Notes

Output Format

Guardrails

References

Related Skills

Multiple Schema Types (`@graph`)

Multiple Schema Types (`@graph`)