For SaaS marketing and product marketing teams
SaaS integration pages that answer the buyer’s real question
Buyers search for your product plus the tool they already use. Give each integration a page that says what it triggers, what it does, how long setup takes and which plan includes it, built from one row of product data.
- Free on WordPress.org
- Clean /integrations/ URLs
- Hub page lists every integration
Why integration pages underperform
A logo and one sentence is not an integration page
Most integrations directories are a grid of near-identical cards that say the product integrates with Slack and link to sign-up. The buyer still does not know what happens, how long setup takes or whether their plan includes it.
The usual integrations page
- A grid of logos, each opening a page with one generic paragraph
- Plan availability lives on the pricing page, and the integration page never mentions it
- Connections that run through Zapier presented as if they were native
- A plan change means editing 40 pages, so half of them go stale
With PageForge
- One row per integration, confirmed by the team that owns it
- Trigger, action, setup time, plans and help link on every page
- Pages nested under an Integrations parent and listed by the Sitemap block
- Change the Plans column and refresh every page in one update run
The data
One row per page, every detail that changes
Pollywise is a fictional survey tool with seven integrations. Integration builds the title and the /integrations/ URL, Trigger and Action make the when-this-happens sentence at the top of the page, and SetupTime, Plans and HelpLink answer the three questions a buyer asks before trying it.
| Integration | Category | Trigger | Action | SetupTime | Plans | HelpLink | |
|---|---|---|---|---|---|---|---|
| 2 | Slack | Chat | a survey gets a new response | post a summary of the answers to a channel | About 2 minutes | All plans | /help/slack/ |
| 3 | HubSpot | CRM | a respondent leaves an email address | create or update the contact with their score | About 5 minutes | Team and Business | /help/hubspot/ |
| 4 | Google Sheets | Spreadsheets | a response is submitted | add a row with every answer | About 2 minutes | All plans | /help/google-sheets/ |
| 5 | Salesforce | CRM | a low score comes in | open a case on the matching account | About 10 minutes | Business | /help/salesforce/ |
| 6 | Microsoft Teams | Chat | a survey closes | send the results summary to a team | About 3 minutes | Team and Business | /help/teams/ |
| 7 | Notion | Docs | a response includes a feature request | add it to a product database | About 4 minutes | All plans | /help/notion/ |
| 8 | Zapier | Automation | any survey event happens | start a Zap with the full response | About 5 minutes | All plans | /help/zapier/ |
Placeholders
{Integration} {Category} {Trigger} {Action} {SetupTime} {Plans} {HelpLink}
Patterns
TitlePollywise + {Integration} integration
URL/integrations/{integration}/
Campaign size
40 integrations + 12 industries + 8 alternatives = 60 pages from three templates
Pages this creates
- Pollywise + Slack integration
- Pollywise + HubSpot integration
- Pollywise + Google Sheets integration
- Pollywise + Salesforce integration
- Pollywise + Notion integration
How it works
From an integration list to a live directory in four steps
01
Export the integration list
One row per integration, taken from product docs or the team that built it: trigger, action, setup time, plans and the help article. Add a column saying whether it is native or runs through a third party.
02
Create the hub and the template
Publish a page called Integrations, then set the template’s Target Post Type to Page and Parent Page to Integrations. The Slug Pattern {integration} gives /integrations/slack/.
03
Check the run and read three drafts
Check and preview shows the first title and URL and flags rows that would share a slug. Generate as drafts and read Slack, Salesforce and Zapier first, because they are the most different rows.
04
Publish, then update with each release
When an integration moves to another plan or gains a trigger, edit the row and run Update it from the CSV and current template. Status, URL and parent stay as they are.
Built for product data
Everything an integration page needs, filled from your spec
Your template explains what never changes. Your columns carry what is true about each integration. PageForge joins them and handles the URL, metadata and hub listing.
The generated page
What a buyer sees on Pollywise + Slack integration
The first row becomes a page that answers the evaluation question in one line: when a survey gets a new response, Pollywise posts a summary of the answers to a channel. Right below it, about 2 minutes of setup and availability on all plans remove the two objections that stop a trial. The link to the Slack setup guide lets an admin check the steps before anyone signs up.
- The trigger and the action in one plain sentence
- Setup time and plan availability near the top
- A direct link to the setup guide
Hub and URLs
Give every integration a clean URL under one hub
Native Pages under an Integrations parent produce /integrations/slack/ and /integrations/google-sheets/, with no /pageforge/ prefix. The Sitemap block on that parent lists every published integration page, so none of them depends on the XML sitemap to be found.
- Create the parent page before the run
- Set the hub list’s grouping to none in Free
- Link the hub from your main navigation
Search snippets
A meta description that names the trigger and the action
With no Service or City column, the SEO title follows your Title Pattern, and the Meta Description Pattern can carry what the integration actually does. PageForge writes both into Yoast SEO, Rank Math, SEOPress or All in One SEO, or prints them itself when none is active.
- SEO title: Pollywise + Slack integration
- Focus keyphrase taken from the SEO title
- Canonical and social fields filled for every page
Compared
PageForge versus a hand-built integrations directory
Both can look good on launch day. The gap opens the first time an integration changes plan.
| PageForge | Hand-built directory pages | |
|---|---|---|
| What the integration does | From the Trigger and Action columns | Often one generic line |
| Plan availability on the page | From the Plans column | Usually only on the pricing page |
| Clean /integrations/ URLs | Yes | Yes |
| Duplicate slug check before publishing | Yes | No |
| Hub listing every integration | Sitemap block | Maintained by hand |
| Updating plans on 40 pages | One update run | 40 separate edits |
| SEO title and description per page | Built from patterns | Partly |
What SaaS integration pages are for
SaaS integration pages answer the question a buyer asks before starting a trial: does this product work with the tools I already use, and what exactly happens when it does? Someone who searches “pollywise hubspot integration” has usually shortlisted you already. They want the trigger, the action, the setup effort and the plan on one page, without booking a demo to find out.
PageForge builds these pages in WordPress from one row per integration. The row holds the product facts. One template holds the layout and the explanation that never changes. Each page gets its own title, a URL under your Integrations hub, a meta description and its fields in your SEO plugin.
The examples use Pollywise, a fictional survey tool with seven integrations. Replace it with your own product and the structure holds.
The searches behind SaaS integration pages
Software buyers search in a few repeatable shapes. Each shape is its own page type, with its own template and its own CSV.
| Page type | Example searches | Columns it needs | Example URL |
|---|---|---|---|
| Integration | “pollywise slack integration”, “send survey responses to salesforce” | Integration, Trigger, Action, SetupTime, Plans | /integrations/slack/ |
| Use case | “survey software for property managers”, “nps survey tool for clinics” | Industry, Job, ExampleSurvey | /industries/property-management/ |
| Alternative | “typeform alternative for nps” | Competitor, Difference, CheckedOn, Source | /alternatives/typeform/ |
A product with 40 integrations, 12 target industries and 8 alternatives has 60 pages across three templates. Integration pages are often read late in an evaluation, by someone ticking a requirement off a list, so a vague page costs you at the point where the buyer is closest to signing up.
What each row needs
Take the data from the product, not from a brainstorm. The engineer or product manager who owns each integration can confirm a row in two minutes, and a wrong row is a support ticket waiting to happen.
| Column | The buyer’s question it answers | Value in the Slack row |
|---|---|---|
| Integration | Do you connect to my tool? | Slack |
| Category | What else connects in this group? | Chat |
| Trigger | When does it fire? | a survey gets a new response |
| Action | What does it do? | post a summary of the answers to a channel |
| SetupTime | How much effort is it? | About 2 minutes |
| Plans | Do I have to upgrade? | All plans |
| HelpLink | Where are the setup steps? | /help/slack/ |
Columns worth adding
- Native: Yes, or Via Zapier. Buyers and support teams both need to know.
- Direction: one-way into the other tool, or two-way.
- DataSent: which fields travel, such as answers, score or email address.
- Limits: what the integration does not do.
- Requirements: what the buyer needs on the other side, such as admin rights.
- LastChecked: the date someone confirmed the row against the live product.
The common failure is the logo page: a logo, the sentence “Pollywise integrates with Slack” and a sign-up button, repeated 40 times with only the name changed. Google’s spam policies describe scaled content as pages produced mainly to rank, with little value added, and a directory of identical logo pages comes close to that description. If all you can say about an integration is its name, it does not need a page yet.
A worked example: seven Pollywise integrations
This is the integration list exported from the product. The product and its plans are fictional.
Integration,Category,Trigger,Action,SetupTime,Plans,HelpLink
Slack,Chat,a survey gets a new response,post a summary of the answers to a channel,About 2 minutes,All plans,/help/slack/
HubSpot,CRM,a respondent leaves an email address,create or update the contact with their score,About 5 minutes,Team and Business,/help/hubspot/
Google Sheets,Spreadsheets,a response is submitted,add a row with every answer,About 2 minutes,All plans,/help/google-sheets/
Salesforce,CRM,a low score comes in,open a case on the matching account,About 10 minutes,Business,/help/salesforce/
Microsoft Teams,Chat,a survey closes,send the results summary to a team,About 3 minutes,Team and Business,/help/teams/
Notion,Docs,a response includes a feature request,add it to a product database,About 4 minutes,All plans,/help/notion/
Zapier,Automation,any survey event happens,start a Zap with the full response,About 5 minutes,All plans,/help/zapier/
The template settings:
| Field | Value |
|---|---|
| Title Pattern | Pollywise + {Integration} integration |
| Slug Pattern | {integration} |
| Target Post Type | Page |
| Parent Page | Integrations |
| Meta Description Pattern | Connect Pollywise to {Integration}: when {Trigger}, it will {Action}. Plans: {Plans}. |
The key sentence in the body is When {Trigger}, Pollywise will {Action}. The Trigger and Action cells are written in lowercase on purpose, so they read naturally in the middle of that sentence. For Notion it comes out as “When a response includes a feature request, Pollywise will add it to a product database.”
What the seven rows produce:
| Integration | URL | Plans | Setup |
|---|---|---|---|
| Slack | /integrations/slack/ | All plans | About 2 minutes |
| HubSpot | /integrations/hubspot/ | Team and Business | About 5 minutes |
| Google Sheets | /integrations/google-sheets/ | All plans | About 2 minutes |
| Salesforce | /integrations/salesforce/ | Business | About 10 minutes |
| Microsoft Teams | /integrations/microsoft-teams/ | Team and Business | About 3 minutes |
| Notion | /integrations/notion/ | All plans | About 4 minutes |
| Zapier | /integrations/zapier/ | All plans | About 5 minutes |
Seven rows give seven pages with no duplicate URLs. They fall into five categories: Chat and CRM with two integrations each, and Spreadsheets, Docs and Automation with one. Four integrations are on all plans, two need Team or Business, and one, Salesforce, is Business only. Setup ranges from about 2 to about 10 minutes, with a median of 4.
The meta descriptions run from 120 to 153 characters. HubSpot’s is the longest, at 153, which is about as long as a snippet can be before search results start trimming it. See Title, URL and meta description patterns for how slugs are cleaned and how the SEO title is built.
Because these rows have no Service or City column, the SEO title is the page title, “Pollywise + Slack integration”, and the focus keyphrase follows it. The schema is your business item and a WebPage item. The Service item needs Service and City columns, which integration rows have no reason to carry. Details are in Schema markup.
Rows that need more data
- Zapier is the thinnest row. “Any survey event happens” and “start a Zap with the full response” are true and tell a buyer almost nothing. That page needs the three or four Zaps customers actually build, and a plain statement that the other app connects through Zapier, not through Pollywise.
- Salesforce is Business only and takes the longest. A buyer on the Team plan should learn that before the trial, not after. Add a Requirements column, because a Salesforce admin will want to know what access the connection needs.
- Slack and Microsoft Teams look alike. Both are Chat, and both post summaries. They differ in the trigger, a new response against a closed survey, and the page should say so in its first lines. Give each a related link to the other.
- Help links drift. Teams points to /help/teams/ while its page lives at /integrations/microsoft-teams/. That is fine, but help articles get renamed, so click every link on a draft.
What to put on every integration page
- The trigger and the action in one plain sentence, near the top
- Whether the connection is native or runs through a third party
- Which way data moves, and which fields travel
- Setup time, and who has to do it
- The plans that include it, with a link to your pricing page
- What it does not do
- A link to the setup guide in your help center
- A screenshot or short example of the result in the other tool
- Related integrations in the same category
- One next step: start a trial, or connect it if you already have an account
Hub, category and related links
Publish the Integrations page before the run, make it the template’s Parent Page, and add the PageForge Sitemap block to it. The free plugin’s grouping options are city, state, service or none. These rows have none of those columns, so set grouping to none, or every integration lands under a fallback heading. See Hub pages with the sitemap block.
PageForge Free adds no automatic links between generated pages. For a “More chat integrations” line, add RelatedName and RelatedLink columns, such as Microsoft Teams and /integrations/microsoft-teams/ on the Slack row, and write the link into the template. Generate one draft and click it. More patterns are on the internal linking page.
Use-case and alternative pages
Use-case pages need their own template and CSV, with columns such as Industry, Job and ExampleSurvey: who the buyer is, the job they are hiring the product for, and a survey they could send on day one. Put them under an Industries parent.
Alternative pages carry the most risk. Write only differences you can stand behind, give each row a CheckedOn date and a Source link, and show both on the page. A competitor changes its pricing or ships a feature, and your page is wrong until someone rechecks it. The affiliate and comparison use case covers comparison structure in more depth, and programmatic SEO for SaaS covers planning the full set. Google’s guide to helpful, people-first content is a useful test for any page you are unsure about.
How to run it in PageForge
With PageForge Free:
- Publish a page called Integrations. It becomes the parent and the hub.
- Open PageForge > Settings and set Business Type (Schema) to Organization, or whichever type fits your company.
- Open PageForge > Data Sources, choose the CSV under CSV Upload and click Upload CSV.
- Open PageForge > Templates and click Add New Template. Build the layout, or choose a designed page as Base Layout to Clone. In PageForge Template Settings, enter the patterns above, set Target Post Type to Page, Parent Page to Integrations and Generated Post Status to Draft.
- On the Generate screen, choose the template and CSV and click Check and preview. You should see
Ready: 7 new, 0 to update, 0 skipped.and the first page at /integrations/slack/. - Click Generate 7 pages now, read the Slack, Salesforce and Zapier drafts first, then publish.
- Repeat with a second template and parent for use-case pages.
Keeping SaaS integration pages accurate
Integration pages go stale quietly. An integration moves to another plan, gains a trigger, or loses a field, and nobody remembers the marketing page. Give the CSV an owner in product marketing and review it with each release.
When a row changes, upload the new file and run the same template with Update it from the CSV and current template. PageForge refreshes the title, content and meta description on the pages it generated, keeps their status, URL and parent, and skips pages someone edited by hand unless you choose to overwrite them. See Update pages you already generated.
Renaming an integration is different. “Microsoft Teams” becoming “Teams” in the CSV changes the slug, so PageForge creates a new page and leaves the old one where it is. Redirect the old URL with your SEO or redirect plugin.
Pro Every Pro plan adds AI content per page, which drafts a section for each integration from its row for your team to review, and bulk AI meta. From Starter, a Parent Path column places each row under its own hub, so one file can cover integration, use-case and alternative pages. XLSX and TSV uploads take an export from your product database as it is. Google Sheets sync, which keeps pages in step with the product team’s sheet, is on Professional and Enterprise. See AI content for WordPress pages.
Common mistakes
- Implying a native connection. If it runs through Zapier, say so on the page.
- Prices in the Plans column. Use plan names and link the pricing page. A price typed into 40 pages is 40 pages to fix.
- Leaving the default content type. PageForge Page content cannot have a parent, so the URL becomes /pageforge/slack/. Choose Page.
- Putting the folder in the Slug Pattern. The slug is only the last part of the URL. The /integrations/ part comes from the parent page.
- One template for every page type. Integration, use-case and alternative pages answer different questions and need different layouts.
- Publishing the whole partner list. An integration nobody has tested should not get a page that describes it.
Free or Pro
The free plugin runs up to 100 rows per run, which covers most integration directories, including the 60-page example above. Pro has no row limit. Move to Pro when you want AI drafts per integration, per-row parent pages, XLSX or TSV uploads, a queue that publishes on a schedule, or a sheet the product team edits directly. Compare editions on Free vs Pro, or start with how to turn a CSV into WordPress pages.
Use cases
Blueprints with a sample CSV included
{ProductA} vs {ProductB} for {UseCase}Comparison pages built from your own testing notes, kept current as your picks change.10 models make 45 pairs; 45 pairs × 3 use cases = 135 possible pagesSee the blueprintDirectories and listing sites{Category} in {City}, {State}Category and city pages for directories, published only where you have real listings.8 categories × 60 cities = 480 possible pages, published only where listings existSee the blueprintAgencies and freelancers{Service} in {City}, {State}Run a proven page structure for each client, with their own data, design and sign-off.5 clients × 6 services × 20 towns = 600 pages across 5 sitesSee the blueprintWill Google treat 40 integration pages as thin or doorway pages?
It can, if the only thing that changes from page to page is the logo. Google’s spam policies target pages mass-produced to rank with little added value, and a directory of identical logo pages comes close to that. Give every row its own trigger, action, setup time, plans and limits, and leave out integrations you cannot describe beyond their name.
Should Zapier-only integrations get their own page?
Only if the page says plainly that the connection runs through Zapier. A buyer searching for your product plus Asana wants to know whether a native connection exists, and implying one creates a support ticket later. Add a Native column with Yes or Via Zapier, show it near the top, and link the Zapier setup guide from those pages.
How do I get URLs like /integrations/slack/?
Publish a page called Integrations first, then set the template’s Target Post Type to Page, Parent Page to Integrations and Slug Pattern to {integration}. Google Sheets becomes /integrations/google-sheets/ because spaces turn into hyphens. Pretty permalinks must be on. On a fresh install the default target is the PageForge content type, which adds a /pageforge/ prefix and has no parents, so change it.
Can one CSV cover integration, use-case and alternative pages?
In Free, use one template and one CSV per page type, because each template has one parent page. A product with 40 integrations, 12 industries and 8 alternatives gets 60 pages from three templates, each under its own hub. Pro, from Starter, can read a Parent Path column, so one file can place rows under /integrations/, /industries/ or /alternatives/.
Does PageForge add SoftwareApplication schema?
No. PageForge adds one JSON-LD block with your business item, using the type you choose in Settings such as Organization, and a WebPage item for each page. Its Service item needs Service and City columns, which integration rows do not have. If you want software-specific markup, add it through your SEO plugin or theme and test the combined output.
What happens when an integration moves to a different plan?
Edit the Plans cell, upload the CSV and run the same template with Update it from the CSV and current template. PageForge refreshes the title, content and meta description on the pages it generated, keeps their status and URL, and reports untouched rows as unchanged. A page your team rewrote by hand is skipped unless you choose to overwrite it.
Can AI write the integration copy?
On Pro, yes, with review. AI content per page sends each row’s values and the page title to your own AI provider and places the returned section where you put {seo_content}. It can only write about what the row says, so add columns such as Limits or ExampleUse first, and check every claim against the product before publishing. Every Pro plan includes it.
How many integration pages can I generate at once?
The free plugin runs up to 100 rows per run, which covers most integration directories. Pro has no per-run row limit and can queue rows for a background scheduler that publishes up to a daily limit. The sample’s seven rows take one short run, and a 40-integration directory fits in a single Free run.
Turn your integration list into pages buyers can evaluate
Install the free plugin, upload a CSV with five integrations and generate them as drafts under your Integrations page. Read each one the way a buyer comparing tools would.
