SwiftSchemaGenerate
    Schema stack

    Case Study Stack

    Case study pages tying an Article to the featured Organization plus FAQs and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Article
    Organization
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Customer story pages highlighting results and proof
    • Industry-specific case studies that pair narrative with organization context
    • Pages where FAQs address scope, timeline, and implementation details
    Composition

    What is included

    • Article

      Represents the case study story with headline, description, author, and dates.

    • Organization

      Captures the featured customer/company and aligns it to the case study.

    • Frequently Asked Questions

      Answers common buyer questions about scope, timeline, results, and stack.

    • Breadcrumb

      Provides navigation context from the case study hub.

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • author.name
    • datePublished
    • description
    • headline
    • itemListElement[].name
    • logo
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • about.name
    • address.addressCountry
    • address.addressLocality
    • dateModified
    • image
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • publisher.name
    • sameAs
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://www.example.com/case-studies/acme-logistics#article",
    "headline": "How ACME Logistics Cut Delivery Time by 22%",
    "description": "See how ACME Logistics modernized routing and reduced delivery times using Example Platform.",
    "image": "https://www.example.com/images/case-studies/acme-delivery.webp",
    "datePublished": "2025-03-12",
    "dateModified": "2025-03-20",
    "url": "https://www.example.com/case-studies/acme-logistics",
    "author": { "@type": "Person", "name": "Jordan Perez" },
    "publisher": { "@type": "Organization", "name": "Example Platform" },
    "about": { "@id": "https://www.example.com/case-studies/acme-logistics#customer" }
  },
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "@id": "https://www.example.com/case-studies/acme-logistics#customer",
    "name": "ACME Logistics",
    "url": "https://www.acmelogistics.com",
    "logo": "https://www.example.com/images/logos/acme-logistics.svg",
    "address": { "@type": "PostalAddress", "addressCountry": "US", "addressLocality": "Chicago" },
    "sameAs": [
      "https://www.linkedin.com/company/acme-logistics"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What was the project scope?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We rebuilt ACME’s routing engine, integrated live carrier ETAs, and automated dispatch across 3 regions."
        }
      },
      {
        "@type": "Question",
        "name": "How long did implementation take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "The first region launched in 6 weeks; full rollout completed in 14 weeks with phased QA."
        }
      },
      {
        "@type": "Question",
        "name": "What technology was used?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We used Example Platform APIs, a React admin console, and existing telemetry to feed route optimization."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Case Studies", "item": "https://www.example.com/case-studies" },
      { "@type": "ListItem", "position": 3, "name": "ACME Logistics", "item": "https://www.example.com/case-studies/acme-logistics" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Do I need both Article and Organization?

    Yes. Article is the case study content; Organization anchors the featured customer and can be reused across related assets.

    Can I add results data?

    Include concrete metrics in the Article body and consider adding an image or table; keep JSON-LD aligned to the page.

    Primary sources

    References