How do buyers ask integration questions?
Buyers already use X and want to know whether it connects to Y. The questions fall into three kinds:
- Can it: "Does X integrate with Y?" "Can I connect Y to X?"
- How: "How do I send X data to Y?" "How to connect X and Y?"
- Down to the action: "Can X create a Y task when a new row is added?"
All three kinds want the same things: which actions are supported, how to set it up, and what the limits are. The integration page is the page written for exactly that question.
How do integration pages differ from comparison and alternatives pages?
| Integration page (X and Y) | Comparison page (X vs Y) | Alternatives page (alternatives to X) | |
|---|---|---|---|
| The buyer's situation | Already uses one of the two and wants them to work together | Choosing one of two candidates | No longer wants X and has no candidate yet |
| What the page must answer | Can they connect, what can they do, how to set up, what are the limits | Which one suits me better | What else is available |
| Core fields | Triggers, actions, setup steps, permissions, limits | A side-by-side table | Inclusion rule and ranking |
| Relationship between the two products | Complementary | Competing | Competing |
For how to write comparison and alternatives pages see How do you write an “X vs Y” comparison page that AI cites? and How to write an “X alternatives” page that AI will cite; this guide covers only integration pages. If your page is about "using X to get a task done", that is a use-case page; see How to write "X for Y" use-case pages that AI will cite.
What structure do big platforms' integration pages actually have?
On 2026-11-12 we fetched six public integration pages with curl (no scripts run, desktop Chrome User-Agent) and recorded what their HTML says. Make's integration page was stopped by a Cloudflare challenge page (403), so we did not get it; unverified.
| Page | Does the title contain both product names | Structured data | Visible text | What is in the HTML |
|---|---|---|---|---|
| zapier.com/apps/google-sheets/integrations/slack | Yes: "Google Sheets Slack Integration - Quick Connect - Zapier" | 10: SoftwareApplication, Service x3, BreadcrumbList x2, VideoObject, FAQPage (7 questions), HowTo (3 steps) and more | About 40,300 characters | 17 h2s; every trigger and action listed with required fields, trigger type and polling interval; FAQ as questions; 3-step setup |
| n8n.io/integrations/google-sheets/and/openai/ | Yes: "Google Sheets and OpenAI: Automate Workflows with n8n" | 2: WebApplication and FAQPage (5 questions) | About 16,100 characters | 15 h2s; a supported actions list for each product, one sentence per item; tutorials, related integrations, FAQ; no separate limits section |
| notion.com/connections/slack | No, the title is just "Slack"; the meta description has both Notion and Slack | None | About 3,500 characters | About, Features (permissions), How to use (three entry points), Details (maker, category, support email) |
| asana.com/apps/slack | Yes: "Slack + Asana • Asana" | None | About 8,100 characters | A list of actions, one statement of a limit, three setup steps, questions and support; the h1 on the page is a "RECOMMENDED" badge, not the title |
| mailchimp.com/integrations/shopify-mailchimp/ | No: "Intuit Mailchimp is the marketing and automation platform built for e-commerce | Mailchimp"; Shopify appears only in og:title | Organization, WebSite, WebPage | About 10,500 characters | The h1 does not contain Shopify either; there is a "Connect your Shopify and Mailchimp accounts" section, the rest is marketing |
| hubspot.com/integrations/slack (redirects to ecosystem.hubspot.com/marketplace/apps/slack) | No: "HubSpot Marketplace" | None | About 20 characters | No meta description and no canonical; the content is rendered by scripts, so a crawler that does not run scripts reads nothing |
None of the six does everything. The most complete are Zapier and n8n: both product names in the title, actions listed one by one in the text, and FAQPage repeating the questions; the Notion and Asana pages are short but state the permissions, entry points, actions and one limit. Three typical gaps: no product names in the title (Notion, Mailchimp, HubSpot), an h1 that is not the page topic (Asana, Mailchimp), and body text rendered by scripts (HubSpot; see Do AI crawlers render JavaScript? for whether crawlers run scripts).
We have no evidence of how often AI cites these pages; the above only describes what the pages say. For general structured data guidance see Does structured data help AI search?.
Which fields should an integration page have?
Following the buyer's three kinds of questions, the page should answer at least these things, each as text in the body, not only in an image or a script-rendered panel:
| Field | Question it answers | How to write it | Who did it in the test |
|---|---|---|---|
| Both product names | "Does X connect to Y?" | In the title, h1 and first sentence | Zapier, n8n, Asana |
| Supported actions | "Can it create a task?" | One per line, starting with a verb plus one sentence of explanation | Zapier, n8n, Asana, Notion (permissions) |
| Triggers | "Can it notify me when a row is added?" | State the event, and where relevant how often it is checked | Zapier |
| Setup steps | "How do I connect them?" | Numbered steps saying where in which product to click and which permissions are needed | Zapier (3 steps), Asana (3 steps), Notion (3 entry points) |
| Limits | "What can't it do?" | A separate section: how many accounts per connection, which data is not synced, who can set it up | Asana (updates from private projects); n8n has no separate section |
| Who made it | "Is it official or third-party?" | State the maker and a support contact | Notion, Asana (Made by) |
| FAQ | The users' own words | Question style, matching the FAQPage data | Zapier, n8n |
Official basis: Zapier's integration publishing requirements say the integration description must start with "<name> is a…", contain no links, and explain what the app does rather than sell it (read 2026-11-12). We found no official document from a search engine or AI company on how to write integration pages, and whether FAQPage and HowTo help citation is not stated officially.
How do you write the skeleton of an integration page?
<title>Example Notes + Slack integration: send a Slack message for new notes</title> <meta name="description" content="Connect Example Notes to Slack. Send a message when a note is created, and create notes from Slack. Setup takes four steps. Supports one workspace per connection."> <h1>Example Notes and Slack integration</h1> <p>Example Notes connects to Slack. It sends a message to a channel when a note is created and lets you create a note from any Slack message.</p> <h2>What can the Example Notes and Slack integration do?</h2> <!-- triggers and actions, one line each --> <h2>How do I connect Example Notes to Slack?</h2> <!-- numbered steps, permissions --> <h2>What are the limits?</h2> <!-- one workspace per connection, ... --> <h2>Frequently asked questions</h2> <!-- real questions, same text as the FAQPage data -->
This is a placeholder example we made up: put both product names in the title and h1, write the headings as the buyer's questions, and give limits their own section. See Do title and meta description matter for AI search? for how to write the title and meta description.
How do I do it, step by step?
1. One page for each important partner product
Make a page only for products you really integrate with. Each page needs its own actions and setup steps; do not generate pages in bulk by swapping names, because they carry no unique information to cite.
2. Put both product names in the title, h1 and first sentence
The Notion and Mailchimp pages miss this; buyers search for both names.
3. Write actions and triggers one by one as text
One per line, starting with a verb. Zapier and n8n list them this way.
4. Use a numbered list for the setup steps
Say in which product to act, which permissions are needed, and whether an admin is required.
5. Write "limits" in their own section
State what it cannot do. Asana's page says that updates from private projects may be sent to a channel with non-members; sentences like this are easier to cite than marketing language.
6. Use question headings and add an FAQ
Use the buyer's own words for the questions and give the conclusion first; keep the FAQPage data identical to the body text, see Is FAQ structured data (FAQPage) still useful?. For how to write see How to write content AI will quote: before and after.
7. Link to the platform's official page and to your docs
You cannot change the platform's directory page, so write everything on your own page and link to the platform page; see Can AI read n8n, Zapier and Make template and integration pages?. For API docs see How should developer docs be written so AI can understand and cite them?. For directories such as Slack see How do Slack apps and Discord bots get recommended by AI?.
8. Re-test a few weeks later with the same questions
Ask ChatGPT and Perplexity "does X connect to Y", ask each question 3 times, and note whether you are mentioned and which URLs are cited.
If you build a Jira or Confluence app, the Atlassian Marketplace app page's robots.txt and sitemap tests and the vendor's naming rules are in How do AI search tools find Atlassian Marketplace apps? App pages tested, plus the vendor's requirements.
FAQ
How does an integration page differ from a comparison page?
An integration page answers "can X and Y be used together", and the two products complement each other; a comparison page answers "X or Y", and the two products compete. The core of an integration page is actions, setup steps and limits; the core of a comparison page is the side-by-side table.
Should the title of an integration page contain both product names?
Yes. Buyers search for both names. Of the six pages we tested, the titles of Zapier, n8n and Asana contain both names; Notion, Mailchimp and HubSpot do not.
Should an integration page list the supported actions?
Yes, one per line. The Zapier and n8n pages both list triggers or actions one by one in the HTML, with one sentence each.
Does an integration page have to carry FAQPage structured data?
Not necessarily. We found no official document saying it makes a page cited more often, so officially it is not stated. In the test, Zapier and n8n have FAQPage; Notion and Asana do not. Questions and answers in the body are the foundation.
Won't stating limits scare users away?
When buyers ask "can it", the boundary is what they need most. Asana's page states one limit on updates from private projects. A page without limits leaves AI to fill the gap from other sources. This point is our judgment, with no data behind it.
Can I generate all integration pages in bulk from one template?
You can reuse one structure, but each page's actions, steps and limits must be real. Pages that only swap the product name carry no unique information; Zapier and n8n both explicitly refuse bulk content that only swaps names for their template descriptions.
What happens if the page is rendered by scripts?
In our test of HubSpot's integration page, the visible text without scripts is about 20 characters, with no meta description and no canonical. A crawler that does not run scripts cannot read the content. We have not verified what real search crawlers do.
Which matters more, the platform's directory page or the integration page on my own site?
There is no data to compare them; unverified. You cannot change the format of the platform's directory page, while your own page can carry every field, so do both and link them to each other.
Sources
- Zapier · Google Sheets Slack Integration (Read 2026-11-12)
- n8n · Google Sheets and OpenAI integration (Read 2026-11-12)
- Notion · Slack connection page (Read 2026-11-12)
- Asana · Slack + Asana (Read 2026-11-12)
- Mailchimp · Shopify Integration for Mailchimp (Read 2026-11-12)
- HubSpot · HubSpot Marketplace: Slack (Read 2026-11-12)
- Zapier · Integration publishing requirements (Read in full 2026-11-12, page has no date)
- kagentx evaluations: the data on the case study pages; each example gives its date.