Cookies & analytics

    We use cookies for analytics and to serve ads. Accept to enable Google Analytics and AdSense. You can decline to stay opt-out.

    SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact
      Stack

      Integrations Directory Stack

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

      Open generatorValidate in Rich Results Test

      When to use this stack

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

      What's included

      • Represents the list of integrations shown on the directory page.

      • Software App
        Open generator

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

      • Frequently Asked Questions
        Open generator

        Answers setup, availability, and support questions.

      • Breadcrumb
        Open generator

        Provides navigation context for the integrations directory.

      Required properties (stack union)

      Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

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

      Recommended properties (stack union)

      description
      itemListElement[].item
      mainEntity[].acceptedAnswer.text
      mainEntity[].author.name
      mainEntity[].name
      name
      numberOfItems
      offers.url
      softwareVersion
      url

      Combined JSON-LD

      Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the 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" }
          ]
        }
      ]

      Implementation steps

      1. Start from your live product detail page content; ensure titles, prices, and availability match the page.
      2. Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
      3. Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
      4. Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
      5. Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
      6. Validate in the Rich Results Test and revalidate after price/availability/policy changes.

      Common errors and fixes

      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.

      References