← Back to Blog
Case StudySEOContent StrategyB2B Marketing

Case Study: SEO From Scratch — 34 Buying Keywords Ranking in 4 Months (No Backlinks)

A B2B FinTech company. Existing domain, no content programme, DA in the low 20s. Four months later: 34 buying-intent keywords ranking, 6 in the top 3. Here is exactly what we did.

SPSantosh Paudel· November 24, 2025· 15 min read· 9 views
Table of contents

Client: B2B payments infrastructure company (confidential) Sector: FinTech / SaaS Timeline: 4 months Starting position: No content programme, DA 22, 3 ranking pages (all branded) Outcome: 34 buying-intent keywords ranking, 6 in top 3, 1,240 organic sessions/month from zero


The Brief

When this client came to me, they had one of the most common problems in B2B SaaS: a technically strong product, a small but capable team, and an organic search presence that was essentially invisible.

Their paid channel was working — Google Ads driving demo requests at an acceptable CPL. But the founders were watching competitors compound their position month over month in organic search, and they knew they were building on rented land.

The ask: build an SEO content programme that generates inbound pipeline without depending on paid.

The constraint: no budget for link building campaigns. We had to earn ranking from content quality and topical authority alone.


Why Most B2B SEO Fails Before It Starts

Companies start with the wrong keyword list.

They use keyword tools, find the highest-volume terms in their category, and write content targeting those terms. Then they wonder why nothing ranks.

The problem: high-volume terms in any established B2B category are dominated by authoritative aggregators, review sites, and category leaders who have been publishing for years. A DA 22 domain targeting "payment processing software" is not going to beat Capterra, G2, and Stripe.

The availability heuristic tricks us: "if I can see this keyword, I can rank for it." We can't — not yet.

The right approach for a low-authority domain is to start where you can actually win, build authority in a cluster, then expand.


Phase 1: Keyword Strategy (Weeks 1–2)

Finding the Winnable Layer

Instead of starting with volume, we started with specificity.

Using Ahrefs, I built a keyword map in three tiers:

Tier 1 — Navigational/brand: 12 branded terms. These would mostly rank automatically as the site matured.

Tier 2 — Competitive head terms: "B2B payment software," "payment API for platforms." Average KD 45–65. These are the eventual goal but not where we start.

Tier 3 — Long-tail buying intent: 200+ specific queries with KD under 25 and clear commercial intent. Things like "payment API for SaaS platforms comparison," "how to embed payment processing in marketplace," "B2B invoice payment automation UK."

The insight: Tier 3 keywords have something Tier 2 doesn't — specificity of intent. Someone searching "payment API for SaaS platforms comparison" is actively evaluating. Conversion probability on a ranking page is dramatically higher than a generic category page.

Cluster Architecture

From the 200+ Tier 3 keywords, I built 6 content clusters:

  1. Payment API for platforms (target ICP: marketplace founders, SaaS builders)
  2. B2B invoice automation (target ICP: finance teams at mid-market companies)
  3. Payment reconciliation (target ICP: CFOs and finance ops)
  4. Embedded finance (target ICP: fintech product managers)
  5. Payment compliance UK (target ICP: compliance officers, UK-focused)
  6. Payment infrastructure comparison (target ICP: late-stage buyers comparing vendors)

Each cluster: 1 pillar page (2,500–3,500 words), 4–6 supporting articles (1,200–1,800 words), and 2–3 FAQ/glossary entries.


Phase 2: Content Production (Weeks 3–10)

The Production System

AI-assisted research phase: For each target keyword, I used Claude to generate a comprehensive brief — competitor analysis, common search intent patterns, subtopics competitors were addressing, gaps in existing content. Research time: 45 minutes per article (down from 3–4 hours).

Expert draft phase: The client's head of product (12 years in payments) recorded 30-minute voice notes for each topic area. These became the substance of the articles — product expertise, real examples, opinions that aggregator content cannot replicate.

AI editing and structuring phase: Voice notes were transcribed, restructured, and polished. Claude was used for structure and clarity — not to generate opinions, which came from the product expert.

SEO optimisation phase: Target keyword in H1 and first 100 words, semantic keywords throughout, internal links to related cluster content.

Review and publish: The client's head of marketing reviewed each piece. Average review time: 30 minutes per article.

Total time per published article: ~3.5–4 hours. Output: 18 articles published in the first 10 weeks.

What We Actually Wrote

  • How to Embed Payment Processing in a SaaS Platform: A Technical Guide for Product Teams
  • B2B Invoice Automation: What Finance Teams Actually Need to Know Before Buying
  • Payment API vs Payment Gateway: The Difference That Matters for Platform Builders
  • UK Payment Compliance in 2025: What Every Marketplace Needs to Know About PSD2
  • Payment Reconciliation Automation: A CFO's Guide to Choosing the Right System
  • Embedded Finance Explained: What It Is, What It Isn't, and When It Makes Sense

Specific, technical, opinionated — the kind of content a product expert would actually find useful.


Phase 3: Internal Linking and Technical SEO (Weeks 8–12)

Internal Linking Strategy

Every supporting article linked to its pillar page. Every pillar page linked to each supporting article. Related articles across clusters linked to each other where topic overlap was genuine.

The effect: Google can crawl the entire cluster from any entry point, and PageRank distributes across all connected pages rather than pooling at individual posts.

Technical Fixes

During a Week 2 audit:

  • Page speed: Core Web Vitals below threshold on 60% of pages. Resolved by image compression, deferred JS loading, removing unused scripts.
  • Crawlability: Key category pages blocked in robots.txt from a legacy staging configuration.
  • Duplicate content: URL parameter issues creating duplicate versions of product pages.

Results: Month 4

MonthOrganic Sessions
Month 182
Month 2340
Month 3740
Month 41,240

Month-over-month growth averaging 55%.

Keyword rankings:

  • 34 keywords ranking in positions 1–50 (from 3 at baseline, all branded)
  • 6 keywords in positions 1–3 (payment API and embedded finance clusters)
  • 11 keywords in positions 4–10

Pipeline: 2 inbound demo requests attributed to organic search in month 4. Both from the payment API for platforms cluster. Contract values (if closed) would represent 40x the cost of the content programme.

No backlinks: No outreach campaign, no guest posting, no link building. One article from the compliance cluster was linked to by a UK payments industry newsletter — unprompted, because the content was actually useful.


What This Proves (and What It Doesn't)

What it proves: You don't need a high-authority domain to rank in B2B if you pick the right fight. Specificity beats volume. Cluster architecture beats individual articles. Expert-led content beats AI-generated filler.

What it doesn't prove: This isn't a template you can copy-paste. The specific keywords, clusters, and production approach were built for this client's ICP, product, and competitive landscape.


The Underlying Mechanism

Compounding authority. Every article we published made the next article more likely to rank. Search engines don't evaluate pages in isolation — they evaluate the authority of the domain on a topic. When a site demonstrates comprehensive coverage of "payment API for platforms" across 8 interlinking articles, it signals topical authority that a single generic post cannot.

Relevance over volume. We wrote 18 articles over 10 weeks. Other brands in this category publish 30+ posts per month and rank for almost nothing. Volume without topical relevance is noise.

The flywheel starting. Month 4's 1,240 sessions will compound into month 8's projected 4,000–5,000 sessions. The early months are the hardest. The returns accelerate.


The Honest Timeline

Months 1–3 will feel like nothing is working. Traffic will be low. Rankings will appear slowly.

Month 4–6 is when you start seeing real signals. Some keywords crack the top 10. Traffic doubles.

Month 9–12 is when the investment pays back. Traffic compounds, leads come in, and the programme begins to self-justify its cost.

The failure mode is stopping in month 2 because "nothing is happening." Everything is happening — it just hasn't become visible yet.

Free resource

Get the AI-SEO Content Checklist

A practical checklist for getting your own content cited by Google AI Overviews, ChatGPT, and Perplexity — not just ranked.

No spam. Unsubscribe anytime.

Browse all free guides →

Run this on your own numbers

Content ROI & Payback Calculator — free, no signup, runs in your browser.

Open the calculator →

Want to implement this with guidance?

Santosh helps founders turn insights like this into real systems.

SEO Content Strategy

External Resources

Further Reading & Tools

Related Posts

01
14 min
SEOSEO Strategy
TodayAnalytics & Data Marketing

Which Keywords Have You Already Lost to AI Overviews?

Impressions holding while CTR collapses is the AI Overview footprint. Here is the BigQuery query, a standard-library Python triage script, and what happened when I ran the same test against my own 4,553 impressions and 22 clicks.

Read article
02
14 min
SEO StrategyContent Strategy
TodaySEO Strategy

Perplexity freshness and the publishing cadence maths

What is actually published about freshness in AI citations, where the two biggest datasets disagree, and the arithmetic for when refreshing an old page beats writing a new one.

Read article
03
14 min
Content StrategySEO
TodayContent Strategy

E-E-A-T When Everyone Publishes AI Content

An adversarial audit over 20 of my drafts returned 221 defects, 68 of them source-fidelity failures: truncated quotes, statistics attached to the wrong source. This post carried four of its own. Here is what E-E-A-T actually asks for, checked against Google's live documentation.

Read article