CASE STUDY 01

Growing organic visibility through technical SEO and content architecture

A technical SEO engagement rarely fails on the audit. It fails on what happens after the audit. This case study documents how I pair crawl and index fixes with a content architecture that gives Google a reason to keep crawling, and how I track whether the two together actually move organic visibility.

By Maharshi KushwahaUpdated 4 min read
Client
Rahul Verma
Company
Finance Niche Website
Industry
Finance & FinTech
Scope
Topical structure, keyword mapping, content strategy, internal linking
Timeframe
2024
Result
8k to 45k monthly visits (+462% growth)
On this page
  1. 01 — Overview
  2. 02 — The Problem
  3. 03 — Initial Analysis
  4. 04 — SEO Strategy
  5. 05 — Implementation
  6. 06 — Results
  7. 07 — What Didn't Work
  8. 08 — Lessons
  9. 09 — Key Takeaways

01 — Overview

Rahul Verma operates a finance niche website covering personal finance, investment topics, and statutory financial products. The site came to me with steady publishing and strong editorial insights, but organic traffic had remained flat at approximately 8,000 monthly visits despite consistent output.

The engagement had two halves that we ran together. The first was a technical SEO cleanup covering crawlability, indexation, and index bloat. The second was a topical structure and internal linking redesign, so authority accumulated in core topic hubs rather than diffusing across isolated posts.

Client
Rahul Verma
Industry
Finance & FinTech
Site type
High-intent editorial finance publishing
Scope
Topical structure, keyword mapping, technical SEO, internal linking
Timeframe
2024

02 — The Problem

The CMS had accumulated tag archives, pagination strings, and date archives that diluted crawl budget. More importantly, financial guides were organised strictly by publication date rather than topical hierarchy. Articles on personal taxation, mutual funds, and credit were scattered across the site without parent hubs linking them together.

The site was leaking crawl equity and had no site architecture that let authority accumulate anywhere.

03 — Initial Analysis

Using my technical SEO audit framework, we reconciled the site crawl with Google Search Console coverage data. We identified soft 404s, thin archive URLs, and widespread keyword cannibalisation where multiple articles targeted overlapping financial queries.

04 — SEO Strategy

The strategy had one principle: fix technical crawl waste first, then restructure content into distinct topic hubs. Parameter URLs and thin archives were pruned or canonicalised, while editorial content was mapped into clear topic clusters following my topical authority framework.

  1. Eliminate crawl noise
  2. Map intent & consolidate overlap
  3. Build authoritative topic hubs
  4. Rewire internal links
  5. Scale search traffic

05 — Implementation

  1. Crawl cleanup

    Canonicalised parameter variants, noindexed thin tag archives, and fixed soft 404 templates across the CMS.

  2. Content consolidation

    Merged overlapping finance articles into definitive guides with 301 redirects from retired URLs.

  3. Topic hub creation

    Created comprehensive topic hubs for major financial categories, added directly into primary navigation.

  4. Internal linking overhaul

    Applied the internal linking framework: supporting articles linked up to their parent hubs, and related articles linked contextually with descriptive anchors.

06 — Results

Verified outcomes achieved for Rahul Verma's finance website:

45,000Monthly organic visits (from 8,000)
+462%Organic traffic growth
TopicalAuthority hubs established
2024Verified client engagement

Technical fixes showed in crawl stats within weeks, while topic clusters accumulated compound impressions over 6 months, scaling total organic visits from 8k to over 45k monthly.

07 — What Didn't Work

Not everything landed. The first version of the hub pages was too thin; they read as navigation rather than as content, and Google treated them that way. They were rewritten to include real explanatory material before they started to pick up impressions.

One set of redirects from merged articles pointed to the hub rather than to the closest merged page, which diluted the consolidation. That was corrected after 3 weeks when the tracked queries for those pages did not recover.

I also underestimated how long template-level changes would take to deploy. The soft 404 fix alone ran 2 weeks over, which pushed the whole timeline.

08 — Lessons

Technical SEO and content architecture are not two projects. They are one system, and the order matters. Cleaning the crawl first made every subsequent change easier to measure and faster to be picked up.

Hub pages have to earn their place. A hub that is only a list of links is a category page, and Google already has plenty of those. The hubs that worked here were the ones that would be worth reading even if nothing linked from them.

Consolidation is more valuable than most teams expect and more painful than they expect. Retiring content that someone wrote is a conversation, not a ticket. I now budget time for that conversation up front.

09 — Key Takeaways

Reconcile three data sources

Crawl, logs and Search Console disagree. The disagreements are the audit.

Fix crawl waste first

It is the fastest change to verify and it makes everything after it more legible.

Architecture before volume

Publishing more into a broken structure is not growth. See why publishing more is not the answer.

Sequence changes to learn

Stagger releases so each one can be attributed. An engagement you cannot learn from is only half done.

If this shape of problem looks like yours, the technical SEO guide covers the mechanisms in depth, and the orphan pages experiment shows one piece of it tested in isolation.

Work With Me See Case Studies

Work with me

Have an SEO problem?

Tell me what you're working on.

Start a Conversation Explore SEO Resources
Email — [email protected]
Based in — India · working remotely
Response — usually within 2 working days