Claude Skill

schema-markup

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Googl

LLM Mart · 0 points · 19 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download thesmokedev-geo-skills-skills_schema-markup-1d09807.zip · 5 KB
Part of thesmokedev/geo-skills — 34 skills

Install

skills CLI npx skills add https://github.com/TheSmokeDev/geo-skills/tree/main/skills/schema-markup
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install thesmokedev-geo-skills@llmmart
Git git clone https://github.com/TheSmokeDev/geo-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole thesmokedev/geo-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Schema Markup

You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.

Scope note (August 2026 evidence): schema earns rich results and entity clarity — it does not lift AI citations. In the Ahrefs controlled study (1,885 pages that added JSON-LD, reported May 2026 via Search Engine Journal), citation rates moved ChatGPT +2.2%, AI Mode +2.4%, AIO -4.6% — all within noise. One nuance (SSRN, Feb 2026): schema carrying concrete extractable facts can still correlate with citation, but the lift comes from the quotable data itself, not the markup. Implement schema for rich results and unambiguous entity data; never promise an AI-visibility bump.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing schema, understand:

  1. Page Type - What kind of page? What's the primary content? What rich results are possible?

  2. Current State - Any existing schema? Errors in implementation? Which rich results already appearing?

  3. Goals - Which rich results are you targeting? What's the business value?


Core Principles

1. Accuracy First

  • Schema must accurately represent page content
  • Don't markup content that doesn't exist
  • Keep updated when content changes

2. Use JSON-LD

  • Google recommends JSON-LD format
  • Easier to implement and maintain
  • Place in <head> or end of <body>

3. Follow Google's Guidelines

  • Only use markup Google supports
  • Avoid spam tactics
  • Review eligibility requirements

4. Validate Everything

  • Test before deploying
  • Monitor Search Console
  • Fix errors promptly

Common Schema Types

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

For complete JSON-LD examples: See references/schema-examples.md


Quick Reference

Organization (Company Page)

Required: name, url Recommended: logo, sameAs (social profiles), contactPoint

Article/BlogPosting

Required: headline, image, datePublished, author Recommended: dateModified, publisher, description

Product

Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review

FAQPage

Required: mainEntity (array of Question/Answer pairs)

BreadcrumbList

Required: itemListElement (array with position, name, item)


Multiple Schema Types

You can combine multiple schema types on one page using @graph:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", ... },
    { "@type": "WebSite", ... },
    { "@type": "BreadcrumbList", ... }
  ]
}

Validation and Testing

Tools

Common Errors

Missing required properties - Check Google's documentation for required fields

Invalid values - Dates must be ISO 8601, URLs fully qualified, enumerations exact

Mismatch with page content - Schema doesn't match visible content


Implementation

Static Sites

  • Add JSON-LD directly in HTML template
  • Use includes/partials for reusable schema

Dynamic Sites (React, Next.js)

  • Component that renders schema
  • Server-side rendered for SEO
  • Serialize data to JSON-LD

CMS / WordPress

  • Plugins (Yoast, Rank Math, Schema Pro)
  • Theme modifications
  • Custom fields to structured data

Output Format

Schema Implementation

// Full JSON-LD code block
{
  "@context": "https://schema.org",
  "@type": "...",
  // Complete markup
}

Testing Checklist

  • Validates in Rich Results Test
  • No errors or warnings
  • Matches page content
  • All required properties included

Task-Specific Questions

  1. What type of page is this?
  2. What rich results are you hoping to achieve?
  3. What data is available to populate the schema?
  4. Is there existing schema on the page?
  5. What's your tech stack?

Related Skills

  • seo-audit: For overall SEO including schema review
  • ai-seo: For AI search optimization (schema gives AI systems clean entity/fact data, but per the Ahrefs May 2026 controlled study it does not by itself lift citations)
  • programmatic-seo: For templated schema at scale
  • site-architecture: For breadcrumb structure and navigation schema planning
Files (geo-skills)
  • references
    • schema-examples.md 8 KB
      # Schema Markup Examples
      
      Complete JSON-LD examples for common schema types.
      
      ## Contents
      - Organization
      - WebSite (with SearchAction)
      - Article / BlogPosting
      - Product
      - SoftwareApplication
      - FAQPage
      - HowTo
      - BreadcrumbList
      - LocalBusiness
      - Event
      - Multiple Schema Types
      - Implementation Example (Next.js)
      
      ## Organization
      
      For company/brand homepage or about page.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "Organization",
        "name": "Example Company",
        "url": "https://example.com",
        "logo": "https://example.com/logo.png",
        "sameAs": [
          "https://twitter.com/example",
          "https://linkedin.com/company/example",
          "https://facebook.com/example"
        ],
        "contactPoint": {
          "@type": "ContactPoint",
          "telephone": "+1-555-555-5555",
          "contactType": "customer service"
        }
      }
      ```
      
      ---
      
      ## WebSite (with SearchAction)
      
      For homepage, enables sitelinks search box.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "WebSite",
        "name": "Example",
        "url": "https://example.com",
        "potentialAction": {
          "@type": "SearchAction",
          "target": {
            "@type": "EntryPoint",
            "urlTemplate": "https://example.com/search?q={search_term_string}"
          },
          "query-input": "required name=search_term_string"
        }
      }
      ```
      
      ---
      
      ## Article / BlogPosting
      
      For blog posts and news articles.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "Article",
        "headline": "How to Implement Schema Markup",
        "image": "https://example.com/image.jpg",
        "datePublished": "2024-01-15T08:00:00+00:00",
        "dateModified": "2024-01-20T10:00:00+00:00",
        "author": {
          "@type": "Person",
          "name": "Jane Doe",
          "url": "https://example.com/authors/jane"
        },
        "publisher": {
          "@type": "Organization",
          "name": "Example Company",
          "logo": {
            "@type": "ImageObject",
            "url": "https://example.com/logo.png"
          }
        },
        "description": "A complete guide to implementing schema markup...",
        "mainEntityOfPage": {
          "@type": "WebPage",
          "@id": "https://example.com/schema-guide"
        }
      }
      ```
      
      ---
      
      ## Product
      
      For product pages (e-commerce or SaaS).
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "Product",
        "name": "Premium Widget",
        "image": "https://example.com/widget.jpg",
        "description": "Our best-selling widget for professionals",
        "sku": "WIDGET-001",
        "brand": {
          "@type": "Brand",
          "name": "Example Co"
        },
        "offers": {
          "@type": "Offer",
          "url": "https://example.com/products/widget",
          "priceCurrency": "USD",
          "price": "99.99",
          "availability": "https://schema.org/InStock",
          "priceValidUntil": "2024-12-31"
        },
        "aggregateRating": {
          "@type": "AggregateRating",
          "ratingValue": "4.8",
          "reviewCount": "127"
        }
      }
      ```
      
      ---
      
      ## SoftwareApplication
      
      For SaaS product pages and app landing pages.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "SoftwareApplication",
        "name": "Example App",
        "applicationCategory": "BusinessApplication",
        "operatingSystem": "Web, iOS, Android",
        "offers": {
          "@type": "Offer",
          "price": "0",
          "priceCurrency": "USD"
        },
        "aggregateRating": {
          "@type": "AggregateRating",
          "ratingValue": "4.6",
          "ratingCount": "1250"
        }
      }
      ```
      
      ---
      
      ## FAQPage
      
      For pages with frequently asked questions.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "What is schema markup?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Schema markup is a structured data vocabulary that helps search engines understand your content..."
            }
          },
          {
            "@type": "Question",
            "name": "How do I implement schema?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "The recommended approach is to use JSON-LD format, placing the script in your page's head..."
            }
          }
        ]
      }
      ```
      
      ---
      
      ## HowTo
      
      For instructional content and tutorials.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "HowTo",
        "name": "How to Add Schema Markup to Your Website",
        "description": "A step-by-step guide to implementing JSON-LD schema",
        "totalTime": "PT15M",
        "step": [
          {
            "@type": "HowToStep",
            "name": "Choose your schema type",
            "text": "Identify the appropriate schema type for your page content...",
            "url": "https://example.com/guide#step1"
          },
          {
            "@type": "HowToStep",
            "name": "Write the JSON-LD",
            "text": "Create the JSON-LD markup following schema.org specifications...",
            "url": "https://example.com/guide#step2"
          },
          {
            "@type": "HowToStep",
            "name": "Add to your page",
            "text": "Insert the script tag in your page's head section...",
            "url": "https://example.com/guide#step3"
          }
        ]
      }
      ```
      
      ---
      
      ## BreadcrumbList
      
      For any page with breadcrumb navigation.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://example.com"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Blog",
            "item": "https://example.com/blog"
          },
          {
            "@type": "ListItem",
            "position": 3,
            "name": "SEO Guide",
            "item": "https://example.com/blog/seo-guide"
          }
        ]
      }
      ```
      
      ---
      
      ## LocalBusiness
      
      For local business location pages.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "LocalBusiness",
        "name": "Example Coffee Shop",
        "image": "https://example.com/shop.jpg",
        "address": {
          "@type": "PostalAddress",
          "streetAddress": "123 Main Street",
          "addressLocality": "San Francisco",
          "addressRegion": "CA",
          "postalCode": "94102",
          "addressCountry": "US"
        },
        "geo": {
          "@type": "GeoCoordinates",
          "latitude": "37.7749",
          "longitude": "-122.4194"
        },
        "telephone": "+1-555-555-5555",
        "openingHoursSpecification": [
          {
            "@type": "OpeningHoursSpecification",
            "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
            "opens": "08:00",
            "closes": "18:00"
          }
        ],
        "priceRange": "$$"
      }
      ```
      
      ---
      
      ## Event
      
      For event pages, webinars, conferences.
      
      ```json
      {
        "@context": "https://schema.org",
        "@type": "Event",
        "name": "Annual Marketing Conference",
        "startDate": "2024-06-15T09:00:00-07:00",
        "endDate": "2024-06-15T17:00:00-07:00",
        "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
        "eventStatus": "https://schema.org/EventScheduled",
        "location": {
          "@type": "VirtualLocation",
          "url": "https://example.com/conference"
        },
        "image": "https://example.com/conference.jpg",
        "description": "Join us for our annual marketing conference...",
        "offers": {
          "@type": "Offer",
          "url": "https://example.com/conference/tickets",
          "price": "199",
          "priceCurrency": "USD",
          "availability": "https://schema.org/InStock",
          "validFrom": "2024-01-01"
        },
        "performer": {
          "@type": "Organization",
          "name": "Example Company"
        },
        "organizer": {
          "@type": "Organization",
          "name": "Example Company",
          "url": "https://example.com"
        }
      }
      ```
      
      ---
      
      ## Multiple Schema Types
      
      Combine multiple schema types using @graph.
      
      ```json
      {
        "@context": "https://schema.org",
        "@graph": [
          {
            "@type": "Organization",
            "@id": "https://example.com/#organization",
            "name": "Example Company",
            "url": "https://example.com"
          },
          {
            "@type": "WebSite",
            "@id": "https://example.com/#website",
            "url": "https://example.com",
            "name": "Example",
            "publisher": {
              "@id": "https://example.com/#organization"
            }
          },
          {
            "@type": "BreadcrumbList",
            "itemListElement": [...]
          }
        ]
      }
      ```
      
      ---
      
      ## Implementation Example (Next.js)
      
      ```jsx
      export default function ProductPage({ product }) {
        const schema = {
          "@context": "https://schema.org",
          "@type": "Product",
          name: product.name,
          // ... other properties
        };
      
        return (
          <>
            <Head>
              <script
                type="application/ld+json"
                dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
              />
            </Head>
            {/* Page content */}
          </>
        );
      }
      ```
      
  • SKILL.md 5.8 KB
    ---
    name: schema-markup
    description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
    metadata:
      version: 1.1.0
    ---
    
    # Schema Markup
    
    You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.
    
    **Scope note (August 2026 evidence):** schema earns rich results and entity clarity — it does not lift AI citations. In the Ahrefs controlled study (1,885 pages that added JSON-LD, reported May 2026 via Search Engine Journal), citation rates moved ChatGPT +2.2%, AI Mode +2.4%, AIO -4.6% — all within noise. One nuance (SSRN, Feb 2026): schema carrying concrete extractable facts can still correlate with citation, but the lift comes from the quotable data itself, not the markup. Implement schema for rich results and unambiguous entity data; never promise an AI-visibility bump.
    
    ## Initial Assessment
    
    **Check for product marketing context first:**
    If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
    
    Before implementing schema, understand:
    
    1. **Page Type** - What kind of page? What's the primary content? What rich results are possible?
    
    2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing?
    
    3. **Goals** - Which rich results are you targeting? What's the business value?
    
    ---
    
    ## Core Principles
    
    ### 1. Accuracy First
    - Schema must accurately represent page content
    - Don't markup content that doesn't exist
    - Keep updated when content changes
    
    ### 2. Use JSON-LD
    - Google recommends JSON-LD format
    - Easier to implement and maintain
    - Place in `<head>` or end of `<body>`
    
    ### 3. Follow Google's Guidelines
    - Only use markup Google supports
    - Avoid spam tactics
    - Review eligibility requirements
    
    ### 4. Validate Everything
    - Test before deploying
    - Monitor Search Console
    - Fix errors promptly
    
    ---
    
    ## Common Schema Types
    
    | Type | Use For | Required Properties |
    |------|---------|-------------------|
    | Organization | Company homepage/about | name, url |
    | WebSite | Homepage (search box) | name, url |
    | Article | 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 |
    
    **For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md)
    
    ---
    
    ## Quick Reference
    
    ### Organization (Company Page)
    Required: name, url
    Recommended: logo, sameAs (social profiles), contactPoint
    
    ### Article/BlogPosting
    Required: headline, image, datePublished, author
    Recommended: dateModified, publisher, description
    
    ### Product
    Required: name, image, offers (price + availability)
    Recommended: sku, brand, aggregateRating, review
    
    ### FAQPage
    Required: mainEntity (array of Question/Answer pairs)
    
    ### BreadcrumbList
    Required: itemListElement (array with position, name, item)
    
    ---
    
    ## Multiple Schema Types
    
    You can combine multiple schema types on one page using `@graph`:
    
    ```json
    {
      "@context": "https://schema.org",
      "@graph": [
        { "@type": "Organization", ... },
        { "@type": "WebSite", ... },
        { "@type": "BreadcrumbList", ... }
      ]
    }
    ```
    
    ---
    
    ## Validation and Testing
    
    ### Tools
    - **Google Rich Results Test**: https://search.google.com/test/rich-results
    - **Schema.org Validator**: https://validator.schema.org/
    - **Search Console**: Enhancements reports
    
    ### Common Errors
    
    **Missing required properties** - Check Google's documentation for required fields
    
    **Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact
    
    **Mismatch with page content** - Schema doesn't match visible content
    
    ---
    
    ## Implementation
    
    ### Static Sites
    - Add JSON-LD directly in HTML template
    - Use includes/partials for reusable schema
    
    ### Dynamic Sites (React, Next.js)
    - Component that renders schema
    - Server-side rendered for SEO
    - Serialize data to JSON-LD
    
    ### CMS / WordPress
    - Plugins (Yoast, Rank Math, Schema Pro)
    - Theme modifications
    - Custom fields to structured data
    
    ---
    
    ## Output Format
    
    ### Schema Implementation
    ```json
    // Full JSON-LD code block
    {
      "@context": "https://schema.org",
      "@type": "...",
      // Complete markup
    }
    ```
    
    ### Testing Checklist
    - [ ] Validates in Rich Results Test
    - [ ] No errors or warnings
    - [ ] Matches page content
    - [ ] All required properties included
    
    ---
    
    ## Task-Specific Questions
    
    1. What type of page is this?
    2. What rich results are you hoping to achieve?
    3. What data is available to populate the schema?
    4. Is there existing schema on the page?
    5. What's your tech stack?
    
    ---
    
    ## Related Skills
    
    - **seo-audit**: For overall SEO including schema review
    - **ai-seo**: For AI search optimization (schema gives AI systems clean entity/fact data, but per the Ahrefs May 2026 controlled study it does not by itself lift citations)
    - **programmatic-seo**: For templated schema at scale
    - **site-architecture**: For breadcrumb structure and navigation schema planning
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related