SwiftSchemaGenerate
    Schema stack

    Customer Story Gallery Stack

    Customer story galleries with CollectionPage, Article entries, FAQs, and breadcrumbs.

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

    When to use this stack

    • Case study galleries with multiple customer stories
    • Customer success hubs with filters and navigation
    • Story directories linking to individual articles
    Composition

    What is included

    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

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

    Recommended properties

    • author.name
    • dateModified
    • description
    • itemListElement[].item
    • mainEntity.@id
    • mainEntityOfPage
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    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": "CollectionPage",
    "@id": "https://www.example.com/customers#page",
    "name": "Customer Stories",
    "description": "Explore how customers achieve results with Northwind.",
    "url": "https://www.example.com/customers",
    "mainEntity": {
      "@type": "Article",
      "@id": "https://www.example.com/customers/acme-logistics#story"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://www.example.com/customers/acme-logistics#story",
    "headline": "ACME Logistics Reduced Delivery Time by 22%",
    "description": "How ACME modernized its routing and cut delivery time.",
    "datePublished": "2025-04-12",
    "dateModified": "2025-04-14",
    "url": "https://www.example.com/customers/acme-logistics",
    "author": { "@type": "Organization", "name": "Northwind" }
  },
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://www.example.com/customers/skyline-health#story",
    "headline": "Skyline Health Improved Patient Scheduling",
    "description": "Skyline increased appointment utilization with automation.",
    "datePublished": "2025-03-28",
    "dateModified": "2025-03-29",
    "url": "https://www.example.com/customers/skyline-health",
    "author": { "@type": "Organization", "name": "Northwind" }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How are stories selected?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We feature customers who share measurable outcomes and approved quotes."
        }
      },
      {
        "@type": "Question",
        "name": "Can customers submit their own story?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Use the submission form to share your story for review."
        }
      },
      {
        "@type": "Question",
        "name": "Do you publish industry-specific galleries?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Filter by industry to find stories relevant to your business."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Customer Stories", "item": "https://www.example.com/customers" }
    ]
  }
]
    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

    Should I include all stories in JSON-LD?

    Include one Article per story visible on the page to keep the list consistent.

    How do I handle filters?

    If filters change the list, keep the JSON-LD aligned to the default visible set.

    Primary sources

    References