Integration Page Design

An integration page shows prospects how your product connects with the tools they already use. "[Product] + HubSpot," "[Product] + Slack," "[Product] + Salesforce." Each integration page targets search queries from users looking for tools that work with their existing stack. These pages convert at 2-5x the rate of generic feature pages because the visitor has already qualified themselves: they use the integration partner tool.

The principle: every integration page is a landing page for a self-qualified audience. Someone searching "[your product] Slack integration" already uses Slack and is evaluating your product. Give them exactly what they need: what connects, how it works, what data flows, and how to set it up.

Architecture

Integration page structure

/integrations/                    → Hub page listing all integrations
/integrations/hubspot/           → Individual integration page
/integrations/salesforce/        → Individual integration page
/integrations/slack/             → Individual integration page

Architecture rules

• Hub page + individual pages. The hub lists all integrations with categories and filters. Each integration gets its own page
• Categorize integrations. CRM, Communication, Enrichment, Automation, Analytics. Categories help users find relevant integrations and help Google understand the page structure
• One page per integration. Don't combine HubSpot and Salesforce on one CRM integrations page. Each integration has its own URL, its own search potential, and its own SEO value
• Use the partner's brand name in the URL. /integrations/hubspot/ not /integrations/crm-connector/. Users search by brand name

Individual Integration Page Template

Page structure

Section writing rules

• "What connects" must be specific. Not "syncs your data." Instead: "Syncs contacts, companies, deals, and activities between [Product] and HubSpot. Two-way sync. Real-time. Custom field mapping available"
• Use cases show workflows, not features. Not "contact sync capability." Instead: "When a prospect replies to your sequence, [Product] automatically creates a contact in HubSpot, logs the activity, and updates the deal stage"
• Setup steps must be honest about complexity. If setup takes 5 minutes with no code, say that. If it requires API configuration, say that. Dishonest "easy setup" claims create bad first experiences
• Include limitations. "Syncs contacts but not custom objects" or "One-way sync only (push to Slack, not pull from Slack)." Honest limitations build trust and reduce support tickets

Hub Page Design

Hub page elements

Hub page rules

• Show every integration. Don't hide integrations behind pagination or "show more." Google needs to crawl all links from the hub
• Category filters should not use JavaScript-only rendering. Google must be able to see all integration links without executing JS. Use server-rendered HTML with progressive enhancement
• Logo + name + one sentence. The grid entry is: partner logo, partner name, one sentence describing what the integration does. Links to the individual page
• Featured section highlights your strongest integrations. If HubSpot and Salesforce are your most popular, feature them. This sends users to your best integration pages first

SEO Optimization

Keyword targeting

SEO rules

• H1 includes both product and partner names. "[Product] + HubSpot Integration" or "Connect [Product] with HubSpot"
• Meta title targets the specific query. "[Product] HubSpot Integration - Sync Contacts, Deals & Activities"
• Use the partner's brand in alt text. Screenshot showing the HubSpot integration → alt="[Product] integration with HubSpot CRM showing contact sync settings"
• Add FAQ schema. Questions like "Does [Product] integrate with HubSpot?" and "How do I set up the [Product] HubSpot integration?" capture additional search visibility
• Internal link from relevant blog posts and use case pages. Any content mentioning HubSpot should link to /integrations/hubspot/

pSEO for Integration Pages

Integration pages are ideal for programmatic SEO because they follow a repeatable template.

Template data model

{
  "partner_name": "HubSpot",
  "partner_logo": "/images/integrations/hubspot.svg",
  "partner_category": "CRM",
  "sync_objects": ["contacts", "companies", "deals", "activities"],
  "sync_direction": "two-way",
  "setup_time": "5 minutes",
  "setup_complexity": "no-code",
  "plan_required": "Pro",
  "use_cases": [
    {
      "title": "Auto-create contacts from replies",
      "description": "When a prospect replies to your sequence..."
    }
  ],
  "faq": [...]
}

pSEO rules for integration pages

• Each page must have unique content. At minimum: unique use cases, unique FAQ, and unique "what connects" section per integration. Don't just swap the partner name
• 400+ words of unique content per page. Template text shared across all pages doesn't count. The unique content per page must hit 400+ words
• Update data when partners release changes. If HubSpot adds a new API or changes their data model, update your integration page. Stale integration data causes support tickets and trust loss

Measurement

Pre-Publish Checklist

• [ ] Hub page lists all integrations with logo, name, and one-line description
• [ ] Each integration has its own URL (/integrations/[partner]/)
• [ ] Hero section includes both product and partner names
• [ ] "What connects" section lists specific data objects and sync direction
• [ ] 3-4 use cases showing practical workflows
• [ ] Setup steps are honest about time and complexity
• [ ] Limitations are disclosed (what doesn't sync, one-way vs two-way)
• [ ] Pricing/plan information included (which plan needed)
• [ ] Partner logo used with permission
• [ ] FAQ section with 3-5 integration-specific questions
• [ ] FAQ schema markup implemented
• [ ] Internal links from relevant blog posts and use case pages
• [ ] Hub page linked from main navigation

Anti-Pattern Check

• All integrations on one page. A single /integrations/ page listing 50 integrations with no individual pages. Each integration can't rank for its own queries. Give each integration its own URL
• Same content with partner name swapped. Every integration page says "Seamlessly connect [Product] with [Partner] for a streamlined workflow." The only difference is the partner name. This is thin content. Write unique use cases and content per integration
• No setup instructions. The integration page says "Integrates with HubSpot" but doesn't show how. The reader's next question is always "how do I set it up?" Answer it on the page
• Hiding limitations. The page says "Full integration with Salesforce." Reality: one-way sync, contacts only, no custom objects. The prospect discovers this after signing up. Disclose limitations upfront
• Integration pages not linked from anywhere. 30 integration pages exist but they're not in the navigation, not on the homepage, not linked from blog posts. They're orphaned. Link from the main nav and relevant content
• Outdated integration data. The page says "syncs with HubSpot free tier" but HubSpot changed their API access 6 months ago. Now it requires Pro. Stale data creates bad experiences. Update quarterly
• No CTA on integration pages. The visitor learned about the integration but has no way to act. No demo button, no sign-up link, no "connect now" button. Every integration page needs a clear next step