Recovering a 15M-user banking platform after two Google core updates.
Associate Business Manager, SEO at Puretech Digital, leading the agency side for a major Indian banking platform. The client is under NDA, so this study names the work, not the bank — and every number in it comes from the client's own GA360 and Search Console, which I presented quarterly to their SVP group.
Situation
A banking platform serving more than 15 million monthly users, where organic search influenced roughly $25M a month in revenue. Financial services is YMYL under the same scrutiny as health and legal — and at this scale, a template-level flaw isn't one broken page, it's ten thousand.
Constraint
Enterprise reality. Every fix shipped through the bank's release cycles, which meant every recommendation had to be argued in business terms and prioritized against engineering capacity — no "just push it live." Two Google core updates hit during the engagement, moving rankings on money terms while the release process moved at bank speed. And the platform carried years of accumulated technical debt: long-standing indexation gaps, conflicting canonicals, and client-side rendering that Googlebot saw differently than users did.
What I did
- Template-level core-update forensics: after each update, segmented the impact by page template rather than by URL — isolating which templates lost visibility, diffing their content and technical profiles against unaffected ones, and rebuilding the losing patterns. Rankings recovered on both occasions.
- Indexation and canonical repair: fixed long-standing index-coverage gaps and canonical conflicts, reconciling what the sitemaps declared against what GSC actually indexed.
- JS-rendering fixes: identified content that only existed client-side, got critical elements into server-rendered HTML, and verified with render testing what Googlebot actually received.
- Defended the money terms: held 90% of high-intent commercial keywords in Google's top 3 through the entire engagement — through both updates.
- Team and stakeholders: mentored three SEO executives and presented quarterly to the client's SVP group — translating crawl-level detail into revenue-level decisions.
Result
| Metric | Value |
|---|---|
| Monthly organic users | 15M+ |
| Organic-influenced revenue | $25M / month |
| High-intent commercial keywords held in top 3 | 90% |
| Google core updates recovered | 2 |
Source: client GA360, Google Search Console, agency reporting. Client identity available under NDA in an interview context.
What transfers to Berry Law
Two things directly. First, core-update resilience: YMYL legal content lives under the same algorithmic scrutiny as YMYL banking content, and the recovery method — isolate by template, diff, rebuild — is exactly how I'd protect Berry Law's programmatic practice-by-geography pages. Second, the working style: Berry Law's JD asks for someone who can command agencies and technical vendors. I've been the agency being commanded, and I now manage one — I know precisely where agency output goes soft and how to hold the standard.
What I'd do differently
Build the monitoring before the emergency. We diagnosed both core updates after impact; a standing template-level rank and quality regression dashboard would have cut days off each diagnosis. That dashboard is now a Phase 01 deliverable in the 90-day plan — you build the instruments before the storm, not during it.