Claim and evidence
And it turned out beautifully, driving 16% of the entire organic traffic.Zapier · ahrefs.com · 2022-08-12
Secondary
A reputable third party analysed it (Lenny's Newsletter, First Round Review, Reforge, an Ahrefs study).
Integration pages credited with a 16% share of organic traffic
Working · 2025-02 Zapier still documents the approach (page updated Feb 2025); Google tolerates templated pages only when they add user value, and long app chains earn little traffic
What the numbers show
of Zapier's organic traffic driven by its programmatic app pages (Ahrefs analysis)
ahrefs.comWhy it works
Integration searches are numerous, specific and high intent. A template plus structured app data (triggers, actions) lets a catalog become thousands of pages, each matching one query. Partner-written copy keeps pages from being identical.
How to run it
- List every integration or app pair your product supports and check search demand for the 'A + B' pattern
- Design one template with data that differs per page (actions, triggers, use cases)
- Give each page its own title, H1 and URL matched to the query
- Let partners or users supply unique descriptive copy
- Link related pages to each other and track indexation and traffic per page
- Prune pairs that earn nothing
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option APage per app pair
Generate one page for every app and every supported combination, as Zapier does.
- Option BPartner-written copy
Let partners describe their own app through a partner program so pages are not identical.
- Option CPrune non-performers
Track indexation and traffic per page and remove pairs that earn nothing.
Timeline
- 12022 Zapier — One page per app and per app pair, with app owners writing the descriptive copy through a partner program
- 22025 Zapier — Own write-up says it rolls out pages for every supported app and every combination of apps
- 32025-02 status checked: Working
Dated examples
- 2025
Zapier
Own write-up says it rolls out pages for every supported app and every combination of apps
No page counts or traffic given by Zapier itself
“they're able to roll out individual pages for every single app they support, along with every combination of apps.”
✓ quote checked word-for-word on the pagezapier.com · undated
- 2022
Zapier
One page per app and per app pair, with app owners writing the descriptive copy through a partner program
Integration pages credited with a 16% share of organic traffic
“And it turned out beautifully, driving 16% of the entire organic traffic.”
✓ quote checked word-for-word on the pageahrefs.com · 2022-08-12
Does it still work?
Zapier still documents the approach (page updated Feb 2025); Google tolerates templated pages only when they add user value, and long app chains earn little traffic source
Risks
- Chains of three or more apps rank for few keywords and get little or no traffic
- Near-identical pages can fall under Google's scaled content abuse policy
- Needs a real integration catalog; invented pairs are thin
Sources
- ahrefs.com
“Yet, Zapier’s blog alone brings 1.6M organic visits every month.”
✓ quote checked word-for-word on the page - zapier.com
Change log
- 2026-11-20 — harvest v0.1 (acq-search)