Nango's integration catalog is its largest search surface: 1,065 pages, one per API. But in a sample of 59, 48 (81%) show no templates and are the same four generic paragraphs with the API name swapped. Someone searching "ConnectWise PSA API integration" lands on a page that does not say how ConnectWise authenticates, what the first call looks like or what can go wrong. Meanwhile the docs hold the auth mode, categories and a two-minute quickstart for every one of the 1,065 providers. The new growth lead and content engineer are hired to make Nango "the go-to integrations brand"; this is the fastest place to show it.
First action
Rebuild 20 empty CRM and HR pages from the docs data and compare their impressions in Search Console after four weeks.
How to measure it
Sign-ups landing on /api-integrations/
- Now
- –
- Target
- +40%
- By
- 90 days
Steps
Pull the data
Auth mode, categories, quickstart call and connect guide for every provider from the docs catalog.
Senior+ Full-Stack Engineer 2 days
Design the page
One layout for pages with and without templates; no boilerplate paragraphs above the fold.
Growth & Marketing Lead (Founding) 2 days
Add related links
Error-fix posts, comparison posts and three neighbouring APIs per page.
Technical Content Engineer 3 days
Write the empty-state box
"Generate it with AI or request it", with delivery days by plan.
Growth & Marketing Lead (Founding) 1 day
Ship a first set
200 pages in CRM, HR, accounting and support.
Senior+ Full-Stack Engineer 1 week
Request indexing
Resubmit the sitemap and watch coverage.
Growth & Marketing Lead (Founding) 1 day
Measure
Impressions, clicks and sign-ups per page group in Search Console and analytics.
Growth & Marketing Lead (Founding) weekly
Roll out
The remaining pages once the first set beats the old template.
Senior+ Full-Stack Engineer 2 weeks
Why it works
Generate each catalog page from the docs catalog instead of a fixed template: auth method and what the user must supply (hostname, client ID, API key), the quickstart request in cURL and Node, the category and three related APIs, links to any "fix this error" posts for that API, and an honest "no prebuilt templates yet: generate one with AI or request it" box tied to the delivery times on the pricing page. Start with the 200 APIs in CRM, HR, accounting and support, where buyers search by name.
Search engines and AI assistants skip near-duplicate pages; specific, useful pages get indexed and cited. It also matches the homepage promise of 1,000+ APIs with something a developer can act on in two minutes.
Ready to use
ChecklistIntegration page minimum
[ ] API name, category, logo [ ] Auth method and what the end user enters [ ] Quickstart request (cURL and Node) [ ] Prebuilt tools, syncs and triggers, or the empty-state box [ ] Request / generate call to action with delivery days [ ] Links to error-fix and guide posts for this API [ ] Three related APIs in the same category [ ] Unique title and meta description
Risks and how to handle them
Thin pages stay thin
Do not publish a page until it has the auth method and a working first request.
Docs and marketing pages drift
Build both from the same catalog file.
Evidence
- Your websiteIntegration catalog (/api-integrations/, 1,065 pages in the sitemap): in a sample of 59 pages checked on October 23, 2026, 48 (81%) list no prebuilt templates. Those pages are the same text with the API name swapped ("Build ConnectWise PSA integrations with Nango", four generic paragraphs on Authentication, Tools, Syncs and Triggers, a "guide" link and "Not on the list?"), with no auth method, setup steps, example request or related articles. Pages with templates show them well, e.g. Salesforce with 36 and Zoho CRM with 60.Source
- Your docsThe docs already hold what the empty catalog pages lack: the agent catalog lists all 1,065 providers with their auth mode (359 OAuth 2, 359 API key, 117 client credentials, 104 basic, 69 two-step, 34 MCP OAuth) and categories (208 productivity, 144 dev tools, 114 marketing, 96 CRM, 74 HR, 55 accounting), and each provider doc has a two-minute quickstart with the first API call. llms.txt is published and robots.txt welcomes AI crawlers.Source
- HiringGrowth & Marketing Lead (Founding), San Francisco, posted September 28, 2026: "make Nango known among developers and technical leaders, from startups with product-market fit to enterprises"; "Grow channels across content, social, partnerships, and paid campaigns"; "Host founder dinners, conference side events, and Nango events"; "Sharpen our messaging and secure speaking opportunities"; "Track relevant awareness, qualified leads, and contribution to pipeline".Source
- HiringTechnical Content Engineer (freelance, remote, posted August 12, 2026): "scale our content for engineers building product integrations"; "Write deeply technical content that educates developers on APIs, integrations, agents, and AI infrastructure"; "Make technical content a major driver of Nango's awareness, adoption, and word of mouth."Source
- Your websitePricing: Free ($0, hard-capped: 10 connections, 10 hours compute, 10GB), Pay-as-you-go ($50/mo with $50 in credits; $0.29 per connection, $0.72 per compute hour, $0.5 per GB), Enterprise (custom; connections "as low as $0.01/connection/month at scale"). A Growth add-on at $450/mo cuts requested-integration delivery from 20 days to 5 (Enterprise: 2). "We currently don't have an EU cloud"; BYOC is offered on Enterprise. There is no cost calculator.Source