SwiftSchemaGenerate
    Schema stack

    Integrations Directory Stack

    Integration directories with ItemList + SoftwareApplication entries, FAQs, and breadcrumbs.

    Open generatorValidate in Rich Results Test
    Included schema
    Item List
    Software App
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Integration or partner catalogs listing apps and connectors
    • Marketplace integration directories
    • Product pages showcasing supported integrations with FAQs
    Composition

    What is included

    • Item List

      Represents the list of integrations shown on the directory page.

    • Software App

      Describes each integration app with name, category, and platform.

    • Frequently Asked Questions

      Answers setup, availability, and support questions.

    • Breadcrumb

      Provides navigation context for the integrations directory.

    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

    • applicationCategory
    • itemListElement[].item.@id
    • itemListElement[].name
    • itemListElement[].position
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • name
    • numberOfItems
    • offers.url
    • softwareVersion
    • url
    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": "ItemList",
    "@id": "https://www.example.com/integrations#list",
    "name": "Integrations Directory",
    "url": "https://www.example.com/integrations",
    "numberOfItems": 2,
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "item": { "@id": "https://www.example.com/integrations/slack#app" }
      },
      {
        "@type": "ListItem",
        "position": 2,
        "item": { "@id": "https://www.example.com/integrations/zapier#app" }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "SoftwareApplication",
    "@id": "https://www.example.com/integrations/slack#app",
    "name": "Slack Integration",
    "description": "Send alerts and notifications to Slack channels.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Web",
    "url": "https://www.example.com/integrations/slack"
  },
  {
    "@context": "https://schema.org",
    "@type": "SoftwareApplication",
    "@id": "https://www.example.com/integrations/zapier#app",
    "name": "Zapier Integration",
    "description": "Connect workflows across hundreds of apps.",
    "applicationCategory": "DeveloperApplication",
    "operatingSystem": "Web",
    "url": "https://www.example.com/integrations/zapier"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Do integrations require a paid plan?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Some integrations require a paid plan. Each integration page lists the plan requirements."
        }
      },
      {
        "@type": "Question",
        "name": "How long does setup take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most integrations can be connected in under 10 minutes."
        }
      },
      {
        "@type": "Question",
        "name": "Where can I get support?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Support links are listed on each integration detail page."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Integrations", "item": "https://www.example.com/integrations" }
    ]
  }
]
    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 every integration in ItemList?

    Yes. Add one ListItem per integration visible on the page and keep the order aligned to the UI.

    How do I handle native vs third-party apps?

    Use SoftwareApplication for each integration regardless of ownership and describe it in the page copy.

    Primary sources

    References