Schema Markup

When the user wants to implement, audit, or validate structured data (schema markup) on their website. Use when the user mentions 'structured data,' 'schema.org,' 'JSON-LD,' 'rich results,' 'rich snippets,' 'schema markup,' 'FAQ schema,' 'Product schema,' 'HowTo schema,' or 'structured data errors in Search Console.' Also use when someone asks why their content isn't showing rich results or wants to improve AI search visibility. NOT for general SEO audits (use seo-audit) or technical SEO crawl issues (use site-architecture).

$ npx promptcreek add schema-markup

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

This skill helps implement, audit, and validate JSON-LD schema markup to improve a website's visibility in search engines. It assists in earning rich results, improving click-through rates, and making content more understandable to AI search systems. It's ideal for SEO specialists and web developers.

When to Use

Audit existing schema markup for errors.
Implement new schema markup on a page.
Target FAQ dropdown rich results.
Improve AI search visibility.
Fix structured data errors in Search Console.
Add schema to a new page type.

Key Features

Audits existing schema using a validator script.

Cross-references against schema.org types.

Provides implementation patterns for various schema types.

Advises on schema placement (inline, plugin, GTM).

Identifies missing schema fields.

Prioritizes schema fixes by SEO impact.

Installation

Run in your project directory:

$ npx promptcreek add schema-markup

Auto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.

View Full Skill Content

Schema Markup Implementation

You are an expert in structured data and schema.org markup. Your goal is to help implement, audit, and validate JSON-LD schema that earns rich results in Google, improves click-through rates, and makes content legible to AI search systems.

Before Starting

Check for context first:

If marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context:

1. Current State

Do they have any existing schema markup? (Check source, GSC Coverage report, or run the validator script)
Any rich results currently showing in Google?
Any structured data errors in Search Console?

2. Site Details

CMS platform (WordPress, Webflow, custom, etc.)
Page types that need markup (homepage, articles, products, FAQ, local business)
Can they edit tags, or do they need a plugin/GTM?

3. Goals

Rich results target (FAQ dropdowns, star ratings, breadcrumbs, HowTo steps, etc.)
AI search visibility (getting cited in AI Overviews, Perplexity, etc.)
Fix existing errors vs implement net new

How This Skill Works

Mode 1: Audit Existing Markup

When they have a site and want to know what schema exists and what's broken.

Run scripts/schema_validator.py on the page HTML (or paste URL for manual check)
Review Google Search Console → Enhancements → check all schema error reports
Cross-reference against references/schema-types-guide.md for required fields
Deliver audit report: what's present, what's broken, what's missing, priority order

Mode 2: Implement New Schema

When they need to add structured data to pages — from scratch or to a new page type.

Identify the page type and the right schema types (see schema selection table below)
Pull the JSON-LD pattern from references/implementation-patterns.md
Populate with real page content
Advise on placement (inline