Products › SaaS

Integrations Page Blueprint — SaaS

Third-party connections are a major decision factor. Structure which tools your software integrates with so AI can match you to stack-specific queries. When someone asks "what analytics tools integrate with Slack?", your integrations page is the answer — but only if the data is structured.

View Prompt View JSON

What this page needs

An integrations page must list each connected tool as a structured entry so AI can match your product to queries about specific technology stacks and workflows.

SoftwareApplication for your product. A SoftwareApplication node with @id of #software anchors the page to your product, so AI knows which tool these integrations belong to.
ItemList of integration entries. An ItemList as mainEntity contains ListItem entries, each wrapping a SoftwareApplication stub for the integrated tool — with name, URL, image, and a description of what the integration does.
CollectionPage type. Declaring the page as a CollectionPage tells AI this is a curated list, not a single-topic page. This helps AI understand the page's purpose is to enumerate connections.
Organization reference. Linking back to your Organization node connects the integrations list to your company identity, reinforcing that these are official, supported connections.

Why these fields matter to AI

Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.

Researched and tested by Minnesota AI

SoftwareApplication

name: Non-negotiable. AI cannot recommend or describe unnamed software.
url: AI needs a stable URL to route users and attribute recommendations.
applicationCategory: AI uses this to match the tool to category-specific queries. Without it AI must infer the category from page content alone.
operatingSystem: AI filters software recommendations by platform. Without this AI cannot answer platform-specific queries.
description: AI pulls this for summarization. Must be one specific sentence describing the core function — not a tagline or marketing copy.

Organization

name: AI uses this to identify the vendor behind the software.
url: Confirms the organization maps to an accessible domain.

WebSite

@id: All other schema nodes reference this ID. Without it the graph is disconnected.

Use This Prompt to Implement Your Schema

Copy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.

You are implementing AIFDS-compliant JSON-LD structured data for a SaaS Integrations page.

AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which
structured data fields AI systems actually read, parse, and use when deciding whether
to cite a page. Documentation at aifds.org.

Before generating any code, ask me for the following information in a single numbered list.
Do not generate schema until I have answered every required field.

REQUIRED — do not proceed without these:
1. App category
2. Company name
3. Domain
4. Integrations faq answer
5. Integrations faq question
6. Integrations page description
7. Integration
8. Logo
9. Product name

OPTIONAL — ask for these but proceed if I skip them:
1. Any additional details not covered above

Once I provide the information, output a complete JSON-LD script block
ready to paste into the <head> of my HTML page.

Output requirements:
- Valid JSON-LD wrapped in <script type="application/ld+json"> tags
- schema.org vocabulary only
- Every AIFDS-required field for this industry and page type included
- Include this data attribute on the script tag: data-aifds="aifds.org SaaS Integrations"
- No placeholder text — omit missing optional fields rather than fill with examples
- After the code block, list any optional fields skipped that would strengthen AI citation

Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your integrations page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "CollectionPage",
      "@id": "https://YOUR_DOMAIN.com/integrations/#webpage",
      "url": "https://YOUR_DOMAIN.com/integrations/",
      "name": "Integrations",
      "description": "YOUR_INTEGRATIONS_PAGE_DESCRIPTION",
      "isPartOf": {
        "@type": "WebSite",
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "about": {
        "@id": "https://YOUR_DOMAIN.com/#software"
      },
      "mainEntity": {
        "@type": "ItemList",
        "name": "Integrations",
        "numberOfItems": 3,
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "item": {
              "@type": "SoftwareApplication",
              "name": "YOUR_INTEGRATION_1_NAME",
              "url": "YOUR_INTEGRATION_1_URL",
              "image": "YOUR_INTEGRATION_1_LOGO",
              "description": "YOUR_INTEGRATION_1_DESCRIPTION"
            }
          },
          {
            "@type": "ListItem",
            "position": 2,
            "item": {
              "@type": "SoftwareApplication",
              "name": "YOUR_INTEGRATION_2_NAME",
              "url": "YOUR_INTEGRATION_2_URL",
              "image": "YOUR_INTEGRATION_2_LOGO",
              "description": "YOUR_INTEGRATION_2_DESCRIPTION"
            }
          },
          {
            "@type": "ListItem",
            "position": 3,
            "item": {
              "@type": "SoftwareApplication",
              "name": "YOUR_INTEGRATION_3_NAME",
              "url": "YOUR_INTEGRATION_3_URL",
              "image": "YOUR_INTEGRATION_3_LOGO",
              "description": "YOUR_INTEGRATION_3_DESCRIPTION"
            }
          }
        ]
      }
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://YOUR_DOMAIN.com/#software",
      "name": "YOUR_PRODUCT_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "applicationCategory": "YOUR_APP_CATEGORY",
      "operatingSystem": "Web"
    },
    {
      "@type": "Organization",
      "@id": "https://YOUR_DOMAIN.com/#organization",
      "name": "YOUR_COMPANY_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png"
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/integrations/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Integrations",
          "item": "https://YOUR_DOMAIN.com/integrations/"
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "YOUR_INTEGRATIONS_FAQ_QUESTION_1",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_INTEGRATIONS_FAQ_ANSWER_1"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_INTEGRATIONS_FAQ_QUESTION_2",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_INTEGRATIONS_FAQ_ANSWER_2"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

How should I list integrations — one per ListItem?

Yes. Each integration should be a separate ListItem inside an ItemList, with the item property containing a SoftwareApplication stub. Include the integration's name, URL, logo, and a short description of what the connection does. This lets AI enumerate your integrations and match them to stack-specific queries.

Should I distinguish native integrations from third-party ones?

If you have both native (built-in) and third-party (via Zapier, Make, etc.) integrations, you can use the description field on each SoftwareApplication stub to clarify the connection type. AI systems benefit from knowing whether an integration is a direct API connection or runs through a middleware platform, as this affects reliability expectations.

Does an API count as an integration?

Your API is the foundation that makes integrations possible, but it is not an integration itself. List your API separately — on a developer docs page, for example — and use the integrations page to list the specific tools and platforms your software connects with out of the box. AI treats "has an API" and "integrates with Slack" as different signals.