๐Ÿ’ผ Portfolio  ยท  Case Studies  ยท  โ† Back to Portfolio
About Services Tools Experience Blog Courses Hire Me
Home โ€บ Portfolio โ€บ Case Study
Case Study 01 ยท Technical SEO

BankBazaar โ€” Site Health Overhaul

How a systematic technical audit across 3,000+ financial product pages resolved critical crawlability issues, fixed indexation errors, and boosted Core Web Vitals โ€” resulting in a 40% organic traffic increase.

โœ… +40% Organic Traffic in 4 Months
๐Ÿ‘จโ€๐Ÿ’ป Lochan Yadavยท๐Ÿข BankBazaarยท๐Ÿ“… 2023ยทโฑ 4-Month Project

The Challenge

BankBazaar operates one of India's most competitive fintech websites โ€” over 15,000 pages spanning personal loans, credit cards, insurance, and investment products. Despite strong content and significant brand authority, the site was consistently underperforming in organic search relative to its potential. Pages were ranking on page 2 and 3 for keywords they should have dominated.

When I audited the site in early 2023, the picture became clear: the technical foundation was silently undermining every piece of content and every link built over years of effort. Crawl budget was being wasted on near-duplicate parameter URLs. Thousands of pages had thin content flags. Core Web Vitals scores were failing on LCP and CLS. Structured data was inconsistent or missing on product pages. And several high-value category pages were accidentally noindexed โ€” effectively invisible to Google.

๐Ÿ’ก
Key Insight: In fintech SEO, technical issues compound faster than in other verticals because financial sites have very high crawl demand from Google. Wasted crawl budget means freshly updated rate tables don't get re-indexed for days, costing real conversions.

Strategy & Approach

Rather than trying to fix everything simultaneously, I structured the work into three prioritised phases based on impact-to-effort ratio:

Phase 1 ยท Weeks 1โ€“4 โ€” Stop the Bleeding
  • Identify and resolve all unintentional noindex tags on category pages
  • Fix canonical tag inconsistencies across 800+ product pages
  • Block crawler-trapping dynamic parameter URLs in robots.txt
  • Correct hreflang errors affecting the EN-IN vs EN-US pages
Phase 2 ยท Weeks 5โ€“10 โ€” Core Web Vitals Sprint
  • Work with the front-end team to defer non-critical JavaScript
  • Implement lazy loading on below-the-fold images and comparison tables
  • Reduce Largest Contentful Paint from 1.8s to 1.1s on key landing pages
  • Fix cumulative layout shift issues caused by third-party ad scripts
Phase 3 ยท Weeks 11โ€“16 โ€” Structured Data & Indexation
  • Deploy FAQPage and FinancialProduct schema across 400+ product pages
  • Submit updated XML sitemap with correct priority and changefreq signals
  • Reclaim 2,100+ orphaned pages by adding them to the internal link graph
  • Implement BreadcrumbList schema site-wide for navigation clarity

Execution

The most complex part of this project was the coordination. Technical SEO changes at scale require sign-off from product, engineering, and legal teams at a financial company. I learned to frame every recommendation in terms of revenue risk rather than SEO best practices โ€” "these 47 product pages are accidentally noindexed, which means Google cannot rank them for loan queries generating โ‚นX in monthly conversions" lands differently than "we have indexation issues."

I built a prioritised issue tracker in Google Sheets, categorised each issue by severity (Critical / High / Medium / Low) and owner (SEO / Dev / Content), and ran a weekly sprint review with the engineering lead. This visibility kept fixes from stalling in backlogs.

For the Core Web Vitals work, I used a combination of Lighthouse CI integrated into the deployment pipeline and manual PageSpeed Insights testing across the 50 highest-traffic templates. Rather than asking engineering to fix everything, I provided component-level recommendations โ€” which specific scripts to defer, which images to convert to WebP, which third-party widgets to load conditionally.

"When Lochan showed us that three of our top credit card comparison pages were noindexed, we realised how much traffic we were leaving on the table." โ€” BankBazaar Product Manager

Results

+40%
Organic traffic increase over 4 months
1,200+
Crawl errors resolved in phase 1
2,100+
Orphaned pages reclaimed into index

Within 6 weeks of phase 1 completion, Google Search Console showed a marked increase in indexed pages and a reduction in "Discovered โ€” currently not indexed" notices. The LCP improvement from 1.8s to 1.1s moved the key product page templates from "Needs Improvement" to "Good" in Google's CWV report โ€” a signal that typically correlates with a ranking boost within 2โ€“3 crawl cycles.

๐Ÿ†
Biggest win: Three high-value credit card comparison pages that had been accidentally noindexed for over 4 months were reclaimed. Within 3 weeks of indexation, they began ranking in positions 4โ€“8 for competitive credit card queries โ€” driving an estimated โ‚น12L in monthly attributed revenue.

Key Takeaways

This project reinforced several principles I now apply to every technical SEO engagement. First, a crawl audit is not a one-time exercise โ€” it needs to be part of a monthly technical health monitoring workflow. I automated this with a Screaming Frog scheduled crawl and a GSC API dashboard that sends weekly alerts for new crawl errors.

Second, Core Web Vitals are fundamentally an engineering problem dressed up as an SEO problem. The SEO's job is not to fix the code, but to diagnose the issues accurately, translate them into engineering tickets, and build the business case for prioritisation. The SEO who understands LCP waterfall analysis will always get their tickets to the top of the sprint.

Third, internal linking is the most underrated technical SEO lever in large sites. Adding 2,100 orphaned pages back into the internal link graph effectively tripled their crawl frequency โ€” without touching a single line of content or building a single backlink.