Back to Blog
Case Studies

From 200 to 3,500 Monthly Visitors: A SaaS SEO Case Study

Rajhussain January 5, 2025 Last updated: February 2026 12 min read

The Starting Point: 200 Visitors and No Strategy

When this client came to us, they had a solid B2B project management tool — but almost no one could find it. Their website was getting about 200 organic visitors per month. They ranked for almost nothing. Their blog had 4 posts, all under 500 words, none targeting specific keywords.

The product was good. The marketing was nonexistent. They'd been relying entirely on cold outreach and a small paid ads budget. When they paused ads for a month, signups dropped to nearly zero.

That's the problem with paid-only acquisition: the moment you stop paying, you stop growing. They needed a sustainable organic channel. That's where we came in.

Month 1: The Technical SEO Audit

Before writing a single word of content, we ran a full technical audit. What we found was typical for early-stage SaaS sites:

Crawl errors: 23 broken internal links, 8 404 pages, and 3 redirect chains that confused Google's crawler.

Missing meta tags: 12 pages had no meta description. 6 pages shared the same title tag. The homepage title was just "Home."

Slow performance: Largest Contentful Paint (LCP) was 4.8 seconds — nearly double the recommended 2.5s threshold. The hero image was an uncompressed 3MB PNG.

No sitemap: Google was discovering pages randomly. No XML sitemap had ever been submitted to Search Console.

No schema markup: Zero structured data. No Organization, Article, or FAQ schema on any page.

Fixes applied in Month 1: - Fixed all broken links and redirect chains - Wrote unique title tags and meta descriptions for every page - Compressed images, switched to WebP, and added lazy loading (LCP dropped to 2.1s) - Generated and submitted an XML sitemap - Added Organization schema to the homepage and Article schema to blog posts - Set up Google Search Console and GA4 tracking

Total time: about 3 weeks of technical work. Not glamorous, but absolutely necessary.

Month 2: Keyword Research and Content Strategy

With the technical foundation in place, we moved to keyword research. The goal: find keywords where the client could realistically rank within 6 months.

Our process: 1. Listed every feature the product offered 2. Used Google Autocomplete, People Also Ask, and Search Console data to find related queries 3. Analyzed competitor blogs to identify content gaps 4. Prioritized by a combination of search volume, keyword difficulty, and business relevance

The result: 40 target keywords organized into 4 topic clusters: - Cluster 1: Project management best practices (informational, top-of-funnel) - Cluster 2: Tool comparisons ("X vs Y" pages, middle-of-funnel) - Cluster 3: Workflow automation guides (informational, tied to product features) - Cluster 4: Team productivity tips (broad appeal, link-building targets)

Each cluster had a pillar page and 8-10 supporting blog post topics. We created a 4-month content calendar with 3 posts per week.

Month 3-4: Content Production at Scale

This is where the real work happened. Over 8 weeks, we:

Published 12 new blog posts — each targeting a specific keyword, minimum 1,500 words, with clear headers, internal links, and a CTA. Topics ranged from "How to Run Better Sprint Retrospectives" to "Project Management Software for Remote Teams."

Optimized 5 existing pages — the homepage, pricing page, features page, and 2 existing blog posts. Added proper keyword targeting, improved copy, and enhanced CTAs.

Built an internal linking structure — every new post linked to 2-3 existing pages. Every service page was linked from at least 3 blog posts. We created a simple linking map in a spreadsheet to track it.

Key content decisions: - We prioritized long-tail keywords first (lower competition, faster to rank) - Every post included a "bottom of funnel" CTA — not just "sign up" but specific to the content topic - We wrote comparison posts ("Client vs Asana," "Client vs Monday.com") because these convert at 3-5x the rate of informational content

By the end of Month 4, the site had 16 indexable blog posts and 5 optimized landing pages. Google Search Console was showing a steady increase in impressions — from 500/day to about 2,000/day.

Content alone isn't enough — especially in competitive niches. We needed backlinks to boost domain authority.

What we did: - 8 directory backlinks: Submitted the product to startup directories — Product Hunt, AlternativeTo, SaaSHub, BetaList, Indie Hackers, G2, Capterra, and GetApp. All free, all providing legitimate backlinks. - 2 guest posts: Wrote detailed articles for two industry blogs (one about remote team management, one about productivity tools). Each included a contextual link back to the client's site. - 1 HARO mention: Responded to a Help a Reporter Out query about project management trends. Got quoted in a Forbes article with a backlink.

What we didn't do: - No paid links - No PBN (private blog network) links - No link exchanges or reciprocal linking schemes

Results: Domain rating went from 12 to 24 over the month. Not dramatic, but enough to tip several pages from page 2 to page 1.

Honest assessment: link building had the lowest ROI of anything we did. The directory submissions were easy wins, but the guest posts took 15+ hours each for a single backlink. Content velocity was more impactful.

Month 6: The Results

Six months after starting, here's where the client stood:

Traffic: - Monthly organic visitors: 200 → 3,500 (1,650% increase) - Daily impressions in Search Console: 500 → 8,200 - Average click-through rate: 2.1% → 3.8%

Rankings: - 3 keywords on page 1 of Google - 47 keywords in the top 20 - 12 keywords in positions 11-20 (poised to break into page 1 with continued optimization)

Business impact: - Organic signups: 8/month → 34/month - Inbound demo requests from organic: 2/month → 11/month - Paid ad spend reduced by 40% (organic was picking up the slack) - Cost per acquisition from organic: effectively $0 after the initial investment

The compounding effect was clear: each month built on the previous one. Month 6 traffic was 3x Month 4 traffic, even though we published fewer new posts in Months 5-6.

Key Lessons: What Worked and What We'd Do Differently

What worked best:

1. Content velocity mattered most. The biggest traffic jumps came after publishing sprints. More content = more keywords = more entry points to the site. If we could do it again, we'd publish even more in Months 2-3.

2. Technical fixes were table stakes. Fixing the technical issues didn't directly drive traffic, but without those fixes, nothing else would have worked. You can't rank with a 4.8s LCP and broken internal links.

3. Comparison pages converted best. "Client vs Competitor" pages had 3-5x the signup rate of informational blog posts. These should be the first content you create.

4. Internal linking was underrated. Simply linking existing pages together improved rankings for several keywords without any new content.

What we'd do differently:

1. Start link building earlier. We waited until Month 5, but directory submissions could have been done in Month 1 — they're low effort and compound over time.

2. Focus on fewer topic clusters. Four clusters spread us thin. Two deep clusters would have built topical authority faster.

3. Add video content. We didn't create any video content, but YouTube results appear in Google search for many of our target keywords. That's a missed opportunity.

The bottom line: SEO for SaaS works. It takes patience and consistent execution, but the results compound in a way that paid ads never will. Six months of work created a traffic engine that continues to grow without additional investment.

RH

Rajhussain

Written by Rajhussain, founder of Hykvra Studio. Full-stack developer and technical SEO analyst with 5+ years of experience building and launching SaaS products. Based in Hyderabad, India. He's personally built and shipped CheckSEO.dev, AI Video Creator, and 10+ client MVPs.

Ready to apply this to your product?

Book a free consultation and let's talk about your project.