Marketing SkillsView repo

Marketing Skill

Schema

Implements schema.org structured data as clean, validated JSON-LD so search engines understand your pages and can show rich results — star ratings, FAQs, breadcrumbs, prices. Point your agent at it when you want a specific page eligible for enhanced search listings and need the markup written correctly.

Maintained by Corey Hainesv2.0.0Updated 2026-05-131 references
npx skills add coreyhaines31/marketingskills

Installs the full library — Schema included

MarkdownView source

Schema markup is structured data (best delivered as JSON-LD in the page head or end of body) that tells search engines what a page is about and makes it eligible for rich results like FAQ dropdowns, star ratings, and breadcrumbs. Match the type to the page: Organization and WebSite for a homepage, Article/BlogPosting for posts, Product or SoftwareApplication for product pages, FAQPage for Q&A, and BreadcrumbList for navigation — and combine several on one page with @graph. Two rules govern everything: the markup must accurately reflect visible content (never mark up what isn't there), and every value must be well-formed — ISO 8601 dates, fully-qualified URLs, exact enumerations. Validate with Google's Rich Results Test before deploying; note that valid schema makes you eligible for rich results but Google decides when to show them.

When to use it

Your agent reaches for this skill when you ask for things like:

“schema markup,”“structured data,”“JSON-LD,”“rich snippets,”“schema.org,”“FAQ schema,”“product schema,”“review schema,”

What's inside

The playbook covers

Initial AssessmentCore PrinciplesCommon Schema TypesQuick ReferenceMultiple Schema TypesValidation and TestingImplementationOutput FormatTask-Specific Questions

Reference library — 1 deep-dives

Schema Markup ExamplesComplete JSON-LD examples for common schema types.

See it in action

You ask

Add schema markup to our SaaS product's homepage. We're a project management tool called TaskFlow. We need Organization schema and any other relevant types.

The skill delivers
FAQPage JSON-LD

{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "What is schema markup?", "acceptedAnswer": { "@type": "Answer", "text": "Structured data that helps search engines understand your content and enables rich results." } }] }

FAQ

What format should I use for schema markup?

JSON-LD. Google recommends it, it's the easiest to implement and maintain, and it lives in a single script block in the head or at the end of the body — no need to weave attributes through your HTML. On React/Next.js sites, render it server-side so search engines see it.

I added schema but I'm not seeing rich results. Why?

First validate with Google's Rich Results Test and the Schema.org validator to rule out syntax errors, bad nesting, or missing required properties. But valid schema only makes a page eligible — Google chooses when to actually display rich results. Check Search Console's enhancement reports to confirm the markup is detected and see any errors versus warnings.

Can I use more than one schema type on a single page?

Yes — wrap them in an @graph array under one @context. A SaaS homepage, for example, can carry Organization, WebSite (with SearchAction), and BreadcrumbList together. Just make sure every type accurately represents content that's actually on the page.

Related skills

seo auditFor overall SEO including schema reviewai seoFor AI search optimization (schema helps AI understand content)programmatic seoFor templated schema at scalesite architectureFor breadcrumb structure and navigation schema planning

Build a tool for this workflow?

Marketers run this skill mid-task — the exact moment your tool matters. Partner tiers put your tool inside the skill their agent runs.

See partner tiers