How I got
here, and how
I work.
Pune, Maharashtra, India
I started in SEO in Jaipur in 2014, on a tax-and-compliance product nobody was searching for by name. The job was to take a domain sitting on page ten and make it visible. It took six or seven months and it taught me the thing I have relied on ever since: organic growth is mostly patience applied to the right diagnosis.
From there the work got broader. A Chief Minister's Office digital presence with an eight-person content team and an audience measured in millions. A sports media property where the interesting problem was not writing but deciding which forty thousand pages deserved to exist. Agency work on B2B martech accounts, where you learn to explain your reasoning to people paying for it. Then a proptech group, four people reporting to me, and a target we beat by more than double.
Since 2024 I have been running organic growth at a fintech fundraising platform, and watching the ground move. Answers replaced results. I went after it the same way I went after page ten in 2014: measure what is actually happening, find the pattern, build against it. That turned into 62,000+ AI citations from a standing start, and a set of automation agents that do the parts of the job that never needed a human.
What I want next is a role where organic search is treated as a serious growth channel rather than a content calendar, somewhere the AI-search shift is understood as the structural change it is, and there is appetite to build for it properly.
Four things that
are true of me.
I ship rather than hand off
Technical SEO, schema, integrations and front-end changes go live without an external developer in the loop. It shortens the distance between spotting a problem and fixing it.
I would rather be measured than optimistic
Every figure on this site is a measured result. I report the ones that did not move too. That is what makes the rest worth believing.
I build the team's capability, not a dependency on me
Daily cadence, explicit ownership and reporting people can act on. Four to eight people, run so the work continues when I am not in the room.
I automate the boring half deliberately
Not everything that can be automated should be. Clear inputs and a writable decision rule. Everything else keeps a human on it.
The paperwork.
B.Tech, Computer Science
Arya College of Engineering & Research Centre, Jaipur
Three, fluently
The ones I
get asked.
What exactly is AEO, and is it different from SEO?
It is the same discipline measured against a different surface. Classic SEO asks where you rank in a list of results. AEO asks whether a generative engine cites you inside its answer, which depends on entity clarity, how extractable a specific claim is, and whether you appear in the third-party sources the engine already trusts. The underlying work overlaps heavily; the prioritisation does not.
Are you available now?
Yes. I have resigned my current role and I am open to conversations now. Most interested where organic search is treated as a growth channel with real ownership attached.
Which employers and clients do these results belong to?
Roles are listed by industry here as a matter of discretion. Employer and client names, and the underlying reporting, are available on request and in the CV I send with applications.
Do you work hands-on or only manage?
Both, and I would not want a role that removed the hands-on half. I currently run a team's worth of output while shipping technical and front-end changes myself.
How do you use AI in the work?
As infrastructure rather than a writing shortcut. Multi-agent systems in Claude Code, connected over MCP to live Search Console, GA4, SE Ranking, Bing Webmaster and DataForSEO data, handling refresh cycles, decay pruning, anomaly detection and reporting. Judgement calls stay with me.