IFTTT's internal linking fix and its 33% YoY traffic gain

IFTTT, the SaaS platform that automates actions between apps and devices, is a large site by page count and a public, named one, which makes agency Uproer’s published account of its internal linking rebuild worth reading directly rather than through a summary. We fetched the case study itself to check which numbers are measured outcomes and which are illustrative examples, since the two are easy to blur together in a piece written to sell an SEO service.

What was actually broken#

Uproer’s starting diagnosis was crawlability, not link strategy. IFTTT.com carried hundreds of thousands of indexable pages, but its internal links rendered only in JavaScript. Running a Screaming Frog crawl configured the way a searchbot follows links, ignoring JavaScript, the agency found only 59 pages reachable at all. That number is the case study’s anchor: almost the entire site was invisible to a crawler that could not execute the site’s scripts, no matter how the pages themselves were organized.

What changed, and over what timeframe#

The fix came in phases across a 6-month engagement. First, an HTML sitemap page listing site URLs in plain HTML, a near-term patch that did not require a front-end rebuild. Then server-side rendering, so the site’s real internal links existed in the raw HTML search engines fetch instead of only in client-side JavaScript. Longer term, the agency added breadcrumb links, sidebar navigation, footer navigation and a content-based internal linking strategy connecting related pages to each other, the site-wide interlinking layer the earlier fixes made worth building.

The numbers the source reports as measured#

Two figures in the case study are presented as actual outcomes, not projections. The HTML sitemap launch alone delivered, in the agency’s words, nearly a 3x increase in indexed pages within two weeks, evidence that Google had pages to find once they existed in crawlable HTML. Over the full 6-month engagement, Uproer reports IFTTT achieved 33% year-over-year organic traffic growth, describing internal linking as the tactic the team made a priority. A separate figure in the same piece, an indexing rate moving from 60% to 80% producing a 15% traffic lift, is explicitly labeled a hypothetical example for estimating opportunity size, not a real IFTTT measurement, and we have left it out of the metrics above for that reason.

Why the attribution needs a caveat#

The 33% growth figure is the headline number, and it is real in the sense that the source states it as IFTTT’s actual result. But the engagement was not an internal-linking-only test: Uproer’s own description includes a full technical and content audit running in parallel, so the traffic gain cannot be cleanly isolated to the linking rebuild the way a controlled split test could isolate it. What the source does support cleanly is the crawlability finding, 59 pages reachable out of hundreds of thousands, and the two-week indexed-page jump that followed the HTML sitemap fix specifically. Treat those two as the most load-bearing numbers in this case, and the 33% as a real but multi-cause result from the same engagement.