Schema Markup Generator

Schema Markup Generator

Generate JSON-LD structured data for rich results, AI citations, and enhanced search visibility.

Install

git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/schema-markup-generator ~/.claude/skills/

When to Use

• Adding structured data to new or existing pages
• Generating JSON-LD for specific schema types
• Auditing existing schema for errors or missing fields
• Improving AI search visibility (pairs with aeo-geo-optimizer)
• Enabling rich results (FAQ dropdowns, star ratings, how-to steps)

Workflow

Step 1: Identify Content Type

Step 2: Generate JSON-LD

Generate a <script type="application/ld+json"> block with all required and recommended fields for the schema type. Always use JSON-LD format (not Microdata or RDFa).

Step 3: Validate

• Google Rich Results Test: https://search.google.com/test/rich-results
• Schema.org Validator: https://validator.schema.org/
• Check Google Search Console for structured data errors

Schema Templates

Article

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title (max 110 chars)",
  "description": "Brief description of the article",
  "author": {
    "@type": "Person",
    "name": "Author Name",
    "url": "https://example.com/author/name",
    "jobTitle": "Author Title",
    "sameAs": ["https://linkedin.com/in/author", "https://twitter.com/author"]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Publisher Name",
    "logo": {"@type": "ImageObject", "url": "https://example.com/logo.png"}
  },
  "datePublished": "2026-03-18T00:00:00Z",
  "dateModified": "2026-03-18T00:00:00Z",
  "image": "https://example.com/article-image.jpg",
  "mainEntityOfPage": {"@type": "WebPage", "@id": "https://example.com/article-url"}
}

FAQPage

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the question?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The complete answer text. Can include <a href=url>HTML links</a>."
      }
    }
  ]
}

HowTo

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Do Something",
  "description": "Brief description",
  "totalTime": "PT30M",
  "estimatedCost": {"@type": "MonetaryAmount", "currency": "USD", "value": "0"},
  "step": [
    {
      "@type": "HowToStep",
      "name": "Step 1 Title",
      "text": "Detailed step instructions",
      "image": "https://example.com/step1.jpg"
    }
  ]
}

Product

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Product description",
  "image": "https://example.com/product.jpg",
  "brand": {"@type": "Brand", "name": "Brand Name"},
  "sku": "SKU-12345",
  "offers": {
    "@type": "Offer",
    "price": "29.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/product"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "127"
  }
}

BreadcrumbList

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com"},
    {"@type": "ListItem", "position": 2, "name": "Category", "item": "https://example.com/category"},
    {"@type": "ListItem", "position": 3, "name": "Current Page"}
  ]
}

Required vs Recommended Fields

Common Mistakes

1. Missing required fields — always check per-type requirements 2. Incorrect date format — use ISO 8601 (YYYY-MM-DDTHH:MM:SSZ) 3. Markup does not match visible content — schema must reflect what users see 4. Using Microdata instead of JSON-LD — Google recommends JSON-LD 5. Nesting errors — validate JSON syntax before deploying 6. Duplicate schema — one schema block per type per page 7. Self-referencing Organization — publisher should be the organization, not the page

Integration with Other Skills

• aeo-geo-optimizer — Schema is a key AEO signal; implement types recommended by the AEO audit
• technical-seo-audit — Audit identifies missing/broken schema; this skill generates the fixes
• seo-content-writer — Content structure should align with schema structure

Schema Markup Generator — Examples

Example 1: Blog Post with FAQ Schema

Prompt

Generate schema markup for my blog post about email deliverability. The post has an FAQ section with 4 questions. Author is Jane Smith, published today.

Output

Two JSON-LD blocks: Article schema (with author Person, publisher Organization, dates) and FAQPage schema (4 Question/Answer pairs matching the visible FAQ content).

---

Example 2: E-commerce Product Page

Prompt

Generate Product schema for our flagship widget. Price: $49.99, in stock, 4.7 stars from 312 reviews, SKU: WDG-PRO-001, brand: WidgetCo.

Output

Product schema with nested Offer (price, currency, availability), AggregateRating (ratingValue, reviewCount), Brand, and image fields. Plus BreadcrumbList for navigation context.

---

Example 3: Schema Audit and Fix

Prompt

Audit the structured data on our top 5 blog posts and fix any issues.

What the skill does

1. Extracts existing JSON-LD from each page 2. Validates against schema.org requirements 3. Identifies: 2 posts missing dateModified, 1 post with invalid date format, 3 posts missing author.sameAs links, all posts missing publisher.logo 4. Generates corrected schema blocks for each page

Schema Markup Generator Reference

Reference data, benchmarks, and platform-specific details for the Schema Markup Generator skill.

<!-- TODO: Add platform API schemas, benchmark data, and domain-specific reference tables -->