How Reply.io grew from 15,000 to 50,000 monthly organic sessions in 9 months

The content operation that wasn't compounding

Reply.io's content team had real infrastructure by the time I came in – over 400 published articles, an established brand, and a team that understood SEO mattered. The problem wasn't effort. Nothing was compounding.

Monthly organic sessions sat at around 15,000. For a platform serving thousands of sales teams globally, that number was far below where it should have been. The team was publishing constantly without moving rankings for the terms that actually brought buyers in.

A technical audit surfaced the drag. Broken internal links were creating dead ends across the library. Meta descriptions were missing on dozens of indexed pages, and sitemap configuration errors were stopping Google from crawling live content. None of these would have crashed performance on their own. Together, they were quietly suppressing everything.

Link building was the other weak point. Reply had been paying around $90,000 a year to an external agency and getting 8 to 12 backlinks a month – mostly from generic directories and content farms with almost no real traffic. That spend was significant relative to what it was actually building.

Beneath both issues was the same root problem: no system for decisions. No framework for which articles to update versus retire. No briefs tied to search intent. No refresh schedule. Every call – write, update, or archive – went to whoever had time that week.

Reply didn't need more content. It needed a system.

What we built

The engagement covered eight connected pieces. Content, links, technical SEO, and automation each affect the others – so the order mattered as much as the work.

Technical foundation first

Before touching a single article, I ran a full technical SEO audit. Three issues surfaced: broken internal links creating dead ends in the link graph, empty or duplicate meta descriptions on already-indexed pages, and sitemap configuration errors causing Google to skip entire content sections. We fixed the foundation first. There's no point rebuilding a content operation on a broken technical base.

Remapping 400+ articles

Reply had over 400 published articles but no way to know which ones were working, which had room to grow, and which were quietly hurting topical authority. I remapped the entire library into a TOFU / MOFU / BOFU structure. Each article got a funnel stage, a primary search intent, and a matching CTA. Awareness-stage articles got different calls-to-action from articles targeting buyers comparing tools. That sounds obvious in theory. It's rarely applied at the article level at scale.

The remap also produced a concrete 90- to 120-day content calendar with a monthly revision cycle – articles to write, articles to update, a priority order, and a named owner.

A process for writing and managing writers

Reply needed a steady supply of quality articles. I built the writer operation from scratch: a vetted network of 30+ writers across SEO and SaaS content, a brief template tied to search intent and funnel stage, and a quality review process that caught problems before they reached the editor. Every brief included the target keyword, search intent, funnel stage, required CTA, structural outline, and tone examples. Writers who consistently delivered got prioritised. Those who didn't were replaced.

Output reached 20 to 30 articles a month at a consistent quality level – without one person bottlenecking commissioning, briefing, reviewing, and publishing.

Link building that moved rankings

The agency model Reply was using – $90,000 a year, 8 to 12 links a month – is a common approach and usually a poor trade. The links came from sites with high domain ratings and almost no real traffic. That kind of portfolio costs a lot while doing very little. I replaced it with direct outreach to real SaaS companies – businesses with real audiences and editorial standards.

The quality shift mattered more than the volume increase. A link from a SaaS site with 50,000 monthly visitors carries more weight than ten links from directories.

Content update cadence

Most content teams deprioritise updates in favour of new articles. New content feels like progress. Updates feel like maintenance. The result is a library that slowly decays as competitors publish fresher content on the same topics. I built a refresh schedule that treated updates as a production item. Every article got a review date – no more than two months out – and updates followed the same brief-based workflow as new articles. The content decay analysis (linked in the sidebar) flagged articles where traffic was dipping before the drop showed up in a monthly report.

Automated publishing and GSC monitoring

Manual publishing at volume creates quality risk. Steps get skipped, internal links don't get added, metadata gets left blank. I built an automated publishing workflow that standardised the final steps before anything went live. I also connected Google Search Console data to a Slack alert. When traffic on any indexed URL dropped meaningfully week-over-week, the alert fired. The team had days to investigate instead of finding out at month-end review. Catching a drop early is the difference between a quick fix and a three-month ranking recovery.

pSEO competitor comparison engine

Reply competes against well-known alternatives, which is an advantage for programmatic SEO. Queries like "Reply.io vs. [Competitor]" have clear search volume and clear buyer intent. I built a comparison page engine and shipped 30 Reply vs. Competitor pages in the first month. Each page gave a fair, detailed comparison across the criteria buyers actually care about – Reply's advantages made concrete rather than promotional, proper on-page SEO and internal links to product pages, and CTAs calibrated to bottom-of-funnel intent. Most pages were indexed within days. Several ranked in the top three for their target queries within 60 days.

Reporting across every channel

The engagement closed with a reporting layer covering the full content operation. Organic traffic and position movement, backlink acquisition rate, lead attribution from organic, and LLM visibility – whether Reply appears in AI-generated answers, which most SEO reports skip entirely – went to the CMO monthly. The content team got a weekly digest. Everything pulled from live data.

What I delivered

• Full technical SEO audit with prioritised fix log
• Funnel-stage remap of 400+ articles with updated CTAs and a 90-120-day content calendar
• Brief template tied to search intent and funnel stage
• Vetted writer network (30+ writers) with a quality review process
• Direct-outreach link building program replacing the agency retainer
• 30 Reply vs. Competitor comparison pages – built, indexed, and ranking in month one
• Automated publishing workflow with a per-article checklist
• GSC → Slack alert for week-over-week traffic drops on indexed URLs
• Monthly reporting dashboard covering organic sessions, backlinks, lead attribution, and LLM visibility

The numbers

• 15,000 → 50,000 monthly organic sessions in 9 months – 3.3× growth
• 20+ backlinks a month from real SaaS sites, replacing a $90K/year agency that delivered 8-12
• 30 Reply vs. Competitor pages built, indexed, and ranking in the first month
• 400+ articles remapped to TOFU/MOFU/BOFU with stage-specific CTAs

What changed in the content operation

None of that came from a single big bet. It came from fixes that compounded on each other.

The technical cleanup showed results within weeks. Once the sitemap issues and broken link graph were fixed, crawl coverage improved and pages that had been quietly held back started moving. This kind of work rarely gets noticed because it's invisible when it's working – it removes drag that nobody could see.

The link building shift took about three months to show up in rankings, which is normal. By month four, domain authority signals were building from real SaaS referrers. Head terms that had been stuck started moving. Quality mattered more than volume.

The comparison pages outperformed everything else early on. Thirty pages indexed and ranking in the first month pulled in leads the broader content operation wouldn't have reached for another quarter. Someone searching "Reply.io vs. Outreach" has already narrowed their shortlist. The pages were built to win that moment.

The content update cadence has the longest tail. Refreshed articles recover gradually and then hold. The articles updated in the first quarter now have the most stable ranking positions.

The operation is running. The writer network is producing. The GSC alerts fire when they should. The comparison pages are ranking. That's what a nine-month engagement is supposed to leave behind – not a final report, but a system that keeps working.

Honest caveats

• The 3.3× figure covers organic sessions. Brand search and direct traffic are driven by product and community – those moved separately, not through SEO structure. The organic growth was real and measurable, but it was growth in one channel.
• The first three months felt like infrastructure work, not traffic work. Technical fixes, remapping, brief-building, and writer onboarding all happen before the traffic line moves. Anyone expecting to see results in month one will be disappointed. Month three is more realistic for early signals.
• Direct-outreach link building requires more active relationship management than an agency retainer. Someone on the team has to own it. The volume and quality are both better than the agency model, but it's not passive.

Want the same for your team?

Book a 30-min call. Bring the keyword cluster you most want to own. I'll audit what's holding it back and show you what a full content operations rebuild would mean for your traffic numbers – before you commit to anything.