The Complete JSON-LD Schema Guide for AI Citations 2026: 7 Schemas That Matter

Schema.org markup is the language AI models use to understand your content.

While AI systems can parse unstructured text, structured data provides clear, machine-readable signals about content type, authorship, dates, and relationships. This guide covers the Schema.org implementations that actually impact AI citations.

Why JSON-LD Matters for AI Citations

How AI Models Use Structured Data

AI models parse Schema.org markup to understand:

JSON-LD vs Microdata

JSON-LD is the recommended format:

Google explicitly recommends JSON-LD for structured data implementation.

Tier 1 Schemas: Highest Citation Impact

These schemas have the most direct impact on AI citation behavior.

FAQPage Schema

Why it matters: FAQPage provides AI models with pre-structured Q&A pairs that can be directly extracted and cited.

Impact: Highest citation probability among all schema types for Q&A content.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the average cost of customer acquisition in SaaS?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The average customer acquisition cost (CAC) in SaaS is $702 as of 2025, up 45% from 2023. This varies significantly by segment: SMB averages $350, mid-market $1,200, and enterprise $5,000+. CAC payback period should target under 12 months for healthy unit economics."
      }
    },
    {
      "@type": "Question",
      "name": "How do you calculate SaaS CAC?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Calculate SaaS CAC by dividing total sales and marketing expenses by the number of new customers acquired in that period. Formula: CAC = (Sales Costs + Marketing Costs) / New Customers. Include salaries, tools, advertising, and content costs. Exclude customer success and implementation costs."
      }
    },
    {
      "@type": "Question",
      "name": "What is a good CAC to LTV ratio?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A healthy CAC:LTV ratio is 1:3 or better, meaning customer lifetime value should be at least 3x acquisition cost. Ratios below 1:3 indicate unprofitable customer acquisition. Ratios above 1:5 may indicate under-investment in growth. Most successful SaaS companies target 1:3 to 1:4."
      }
    }
  ]
}

Best practices:

• Include 3-7 questions per page (not too few, not overwhelming)
• Answers should be comprehensive (50-150 words)
• Questions should match how users actually ask
• Answers must match visible FAQ content exactly

Article Schema

Why it matters: Article schema provides AI models with structured metadata about content authorship, dates, and publication context.

Impact: Essential for content pages targeting informational queries.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "SaaS Pricing Strategy: The Complete 2026 Guide",
  "description": "Data-driven pricing strategies for SaaS companies, including value-based pricing, tiering, and psychological pricing tactics.",
  "image": "https://example.com/images/saas-pricing-guide.jpg",
  "datePublished": "2025-06-15T09:00:00Z",
  "dateModified": "2026-01-09T14:30:00Z",
  "author": {
    "@type": "Person",
    "name": "Dr. Sarah Chen",
    "honorificSuffix": "PhD",
    "jobTitle": "Chief Economist",
    "url": "https://example.com/authors/sarah-chen",
    "sameAs": [
      "https://linkedin.com/in/sarahchen",
      "https://twitter.com/sarahchen"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png",
      "width": 600,
      "height": 60
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/guides/saas-pricing-strategy"
  },
  "keywords": ["SaaS pricing", "pricing strategy", "value-based pricing"],
  "articleSection": "Guides",
  "wordCount": 2500
}

Critical fields for AI citations:

Person Schema (Author)

Why it matters: Author credentials significantly impact citation probability (+40% with visible credentials). Person schema is the technical implementation of E-E-A-T signals.

→ Strategy guide: E-E-A-T for AI: Building Authority Signals - which credentials matter by industry, building authority without formal credentials, Knowledge Graph entity establishment.

Technical implementation:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Dr. Sarah Chen",
  "honorificSuffix": "PhD",
  "jobTitle": "Chief Economist",
  "url": "https://example.com/authors/sarah-chen",
  "worksFor": {
    "@type": "Organization",
    "name": "Example Company"
  },
  "alumniOf": {
    "@type": "Organization",
    "name": "MIT Sloan School of Management"
  },
  "sameAs": [
    "https://linkedin.com/in/sarahchen",
    "https://twitter.com/sarahchen"
  ]
}

Essential properties: honorificSuffix (credentials), jobTitle, alumniOf (education), sameAs (cross-platform verification).

Tier 2 Schemas: Strong Supporting Impact

These schemas provide important context and improve citation quality.

Organization Schema

Why it matters: Establishes publisher authority and entity identity.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Company",
  "alternateName": "ExampleCo",
  "url": "https://example.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/logo.png",
    "width": 600,
    "height": 60
  },
  "description": "Enterprise SaaS platform for revenue operations, serving 10,000+ companies globally.",
  "foundingDate": "2018-03-15",
  "founders": [
    {
      "@type": "Person",
      "name": "Jane Smith"
    }
  ],
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": 250
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Tech Street",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-123-4567",
    "contactType": "customer service"
  },
  "sameAs": [
    "https://linkedin.com/company/example",
    "https://twitter.com/example",
    "https://facebook.com/example",
    "https://en.wikipedia.org/wiki/Example_Company"
  ],
  "award": ["G2 Leader 2025", "Gartner Cool Vendor 2024"]
}

HowTo Schema

Why it matters: For procedural content, HowTo provides AI models with clear step-by-step structure.

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Set Up Value-Based Pricing for Your SaaS",
  "description": "Step-by-step guide to implementing value-based pricing that increases revenue per customer.",
  "totalTime": "PT4H",
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "0"
  },
  "supply": [
    {
      "@type": "HowToSupply",
      "name": "Customer interview data (minimum 20 interviews)"
    },
    {
      "@type": "HowToSupply",
      "name": "Competitive pricing analysis"
    }
  ],
  "tool": [
    {
      "@type": "HowToTool",
      "name": "Survey tool (Typeform, SurveyMonkey)"
    },
    {
      "@type": "HowToTool",
      "name": "Spreadsheet (Excel, Google Sheets)"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Conduct Value Discovery Interviews",
      "text": "Interview 20-30 customers to understand the specific value they derive from your product. Focus on: problems solved, time saved, revenue impact, and alternative solutions they considered.",
      "url": "https://example.com/guides/value-pricing#step-1",
      "image": "https://example.com/images/step-1.jpg"
    },
    {
      "@type": "HowToStep",
      "name": "Quantify Value Metrics",
      "text": "Convert qualitative interview data into quantifiable metrics. Calculate: average time saved per week, revenue increase percentage, cost reduction, and strategic value indicators.",
      "url": "https://example.com/guides/value-pricing#step-2"
    },
    {
      "@type": "HowToStep",
      "name": "Build Value-Based Pricing Model",
      "text": "Create pricing tiers based on value delivered, not features. Price should capture 10-20% of the value you create for customers. Test with existing customers before launch.",
      "url": "https://example.com/guides/value-pricing#step-3"
    }
  ]
}

BreadcrumbList Schema

Why it matters: Helps AI models understand content hierarchy and site structure.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Guides",
      "item": "https://example.com/guides"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Pricing",
      "item": "https://example.com/guides/pricing"
    },
    {
      "@type": "ListItem",
      "position": 4,
      "name": "Value-Based Pricing Guide",
      "item": "https://example.com/guides/pricing/value-based"
    }
  ]
}

Tier 3 Schemas: Specialized Applications

These schemas serve specific content types.

SoftwareApplication Schema

For SaaS landing pages and product content:

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Example Analytics",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web browser",
  "description": "Revenue analytics platform for SaaS companies",
  "offers": {
    "@type": "Offer",
    "price": "99",
    "priceCurrency": "USD",
    "priceValidUntil": "2026-12-31"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "ratingCount": "2847",
    "bestRating": "5"
  },
  "screenshot": "https://example.com/images/dashboard.png",
  "featureList": [
    "Real-time revenue dashboards",
    "Cohort analysis",
    "Churn prediction",
    "Custom reporting"
  ]
}

LocalBusiness Schema

For local businesses and Gemini optimization:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Consulting",
  "image": "https://example.com/office.jpg",
  "url": "https://example.com",
  "telephone": "+1-555-123-4567",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Business Ave",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 37.7749,
    "longitude": -122.4194
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "18:00"
    }
  ],
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "156"
  }
}

Complete Page Example: All Schemas Combined

Here's how multiple schemas work together on a single page:

<head>
  <!-- Article Schema -->
  <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Article",
      "headline": "SaaS Pricing Strategy: The Complete 2026 Guide",
      "description": "Data-driven pricing strategies for SaaS companies...",
      "datePublished": "2025-06-15T09:00:00Z",
      "dateModified": "2026-01-09T14:30:00Z",
      "author": {
        "@type": "Person",
        "@id": "https://example.com/authors/sarah-chen#person"
      },
      "publisher": {
        "@type": "Organization",
        "@id": "https://example.com#organization"
      }
    }
  </script>

  <!-- Person Schema (Author) -->
  <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Person",
      "@id": "https://example.com/authors/sarah-chen#person",
      "name": "Dr. Sarah Chen",
      "honorificSuffix": "PhD",
      "jobTitle": "Chief Economist",
      "url": "https://example.com/authors/sarah-chen",
      "sameAs": [
        "https://linkedin.com/in/sarahchen",
        "https://twitter.com/sarahchen"
      ]
    }
  </script>

  <!-- Organization Schema (Publisher) -->
  <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "@id": "https://example.com#organization",
      "name": "Example Company",
      "url": "https://example.com",
      "logo": {
        "@type": "ImageObject",
        "url": "https://example.com/logo.png"
      }
    }
  </script>

  <!-- BreadcrumbList Schema -->
  <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://example.com"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Guides",
          "item": "https://example.com/guides"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Pricing Guide",
          "item": "https://example.com/guides/pricing"
        }
      ]
    }
  </script>

  <!-- FAQPage Schema -->
  <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What is value-based pricing?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Value-based pricing sets prices based on the value delivered to customers rather than cost-plus or competitor-based approaches..."
          }
        }
      ]
    }
  </script>
</head>

Validation and Testing

Validation Tools

Validation Checklist

• All required properties present
• No syntax errors (valid JSON)
• URLs resolve correctly
• Dates in ISO 8601 format
• Schema matches visible content
• No duplicate conflicting schemas
• Rich Results Test passes

Common Errors

Implementation Checklist

Minimum Viable Implementation

• Article schema with datePublished, dateModified, author
• Person schema for primary author
• Organization schema for publisher
• FAQPage schema if FAQ section exists

Full Implementation

• Article schema (complete)
• Person schema (with credentials, sameAs)
• Organization schema (with sameAs, awards)
• BreadcrumbList schema
• FAQPage schema
• HowTo schema (for procedural content)
• SoftwareApplication (for product pages)
• LocalBusiness (for local presence)

Ongoing Maintenance

• Update dateModified with substantive changes only
• Verify sameAs URLs remain valid
• Re-validate after CMS updates
• Monitor Rich Results reports in Search Console

Key Takeaways

1. FAQPage has highest direct impact - Provides AI models with extractable Q&A pairs. Implement first if you have FAQ content.

2. Article + Person + Organization is the foundation - These three schemas together establish content identity, authorship, and publisher authority.

3. dateModified signals freshness - Critical for Perplexity and AI Overviews. Only update with substantive content changes.

4. Credentials in Person schema matter - honorificSuffix for degrees, alumniOf for education, award for recognition directly impact E-E-A-T signals.

5. Consistency across platforms is key - sameAs links should point to verified, consistent profiles. AI models cross-reference.

6. Schema supports but doesn't replace content quality - Well-structured data helps AI parse good content. It won't rescue poor content.

Further Reading

• Google Structured Data Documentation
• Schema.org Full Vocabulary
• E-E-A-T for AI Citations
• Complete AI Citation Optimization Guide
• Content Freshness for AI Citations

---

Track the impact of your Schema.org implementation: Qwairy monitors how structured data changes affect your AI citations. See the correlation between schema improvements and visibility changes across ChatGPT, Claude, Perplexity, and Gemini—with before/after comparisons and trend tracking.