SEO Consultant in India | Maharshi Kushwaha

Most companies that contact me have already done some SEO. They have an agency report, a backlog nobody owns, a few blog posts a month, and a sense that organic should be doing more. The problem is rarely a lack of ideas. It is that nobody has turned them into a system with an owner, a sequence and a feedback loop.

What an independent SEO consultant actually does

An agency sells capacity. A consultant sells judgement. That is the simplest way I can put the difference, and it shapes everything about how I work.

An agency is built to run a retainer: a fixed scope, a monthly deliverable, a team that rotates across accounts. That is fine for execution-heavy work with a clear brief. It is weak at diagnosis, at saying "stop doing that", and at working inside your engineering process rather than alongside it.

As a consultant, my job is to understand your site, your market and your team well enough to decide what matters, in what order, and then to make sure it actually gets implemented. I do not hand over a document and leave. I read the crawl and index data, I sit in the sprint planning, I review the pull request, I check the logs after the deploy. Implementation is where most SEO programmes die, and I have written about that in The Implementation Problem.

A consultant is accountable for the decision, not just the deliverable.

The other thing a consultant can do that an agency usually cannot is hold technical SEO, content and authority in one head. On most sites those three are owned by three different teams, and the opportunities sit in the seams between them. A page template that is fast but says nothing, a content programme that nobody links to, a link-building effort pointed at pages that are not indexed. I work across those seams on purpose.

Who should hire a consultant, and who should not

Founders and growth leads at D2C and SaaS companies

You have product-market fit and a marketing budget, but organic is an afterthought. You need someone to decide what the first ninety days of serious SEO should look like and to make sure engineering time is spent on the right things.

In-house marketing teams without an SEO specialist

You have content people and a developer, but nobody who can read a Search Console export and tell you what it means. A consultant gives you that judgement without a full-time hire you may not need yet.

Companies with an agency that is not moving the needle

The reports are tidy but traffic is flat. You want an independent read on what the agency is doing, what it is missing, and whether the money is in the right place. I do this often and I try to be fair to the agency.

Product and engineering teams shipping a migration or rebuild

A replatform, a domain change, a new JavaScript framework. These are the moments where years of organic equity can be lost in a week. You want someone embedded before the build starts, not after the drop.

Large sites with a technical problem nobody can name

Marketplaces, classifieds, listings, publishers. Hundreds of thousands of URLs, uneven indexing, crawl budget quietly wasted. This is technical SEO at scale, and it needs diagnosis before anyone touches content.

Who should not hire me

If you need twenty blog posts a month written and published, you need a content team, not a consultant. If you need someone to "just do the SEO" with no internal owner and no developer access, the engagement will stall and I will tell you so upfront.

The problems I am usually brought in to solve

The brief is almost never "do SEO". It is usually one of a handful of specific situations, and each one has a different starting point.

Traffic has plateaued and nobody knows why. The site has been growing for a while and then stops. Usually this is a structural ceiling: the architecture only supports so many ranking pages, the internal linking cannot carry authority to new sections, or the content has saturated its topical lane. The fix is rarely more content. It is almost always a strategy conversation about where the next tier of demand lives.

A migration or redesign went wrong. Rankings fell after a launch and the team is arguing about whether it was the redirects, the rendering, the removed pages or "a Google update". I pull the before-and-after crawl, the logs and the Search Console data and tell you which it was. Usually it is two or three compounding issues.

There is a huge content investment with little to show for it. Hundreds of articles, decent writing, and the organic chart barely moves. This is the classic sign of content produced without search-intent architecture, which I cover under content SEO and in the note Publishing More Is Not the Answer.

How I approach an engagement

Every engagement starts the same way regardless of model: I need to understand the site as a system before I recommend anything. That means I ask for access to Search Console, analytics, the CMS, and ideally server logs and a staging environment, and I spend the first stretch of time reading rather than talking.

My underlying method is the one laid out in the SEO Strategy Framework: identify where demand exists, identify what the site can credibly rank for, find the gap between the two, and then sequence the work by impact and effort. Technical constraints come first because they cap everything else. Content and authority work only pays off once the site can be crawled, rendered and indexed reliably.

Diagnose
Prioritise
Sequence
Implement
Measure
Compound

I also think about search more broadly than Google's ten blue links. Discovery now happens in AI answers, YouTube and marketplace search too, but the fundamentals that earn a classic result are the same ones that earn a citation, as the AI search citation experiment showed. I will not sell you a separate "AI SEO" strategy that ignores the base.

Engagement models

I run three kinds of engagement. The right one depends on how much internal capability you have and how urgent the problem is.

Advisory

A fixed number of hours each month for direction, review and decisions. Your team executes; I set priorities, review what ships, answer the hard questions and course-correct. Best when you already have a content person and a developer who can act on clear instructions.

Embedded

I work inside your team for a defined period, usually alongside a product or engineering squad. I join planning, write tickets, review implementation and own the SEO outcomes of the sprint. Best for migrations, rebuilds and large technical programmes where decisions happen daily.

Project

A defined scope with a defined end: an SEO audit, a migration plan, a programmatic SEO build, a content architecture. You get a clear deliverable and an implementation handover. Best when you need a specific answer rather than ongoing support.

What all three have in common

Direct access to me, not an account manager. Written reasoning for every recommendation. A measurement model agreed in the first weeks so we both know what "working" means. And a bias toward fewer, better changes over a long list of tweaks.

What you get

A diagnosis you can act on

What is actually constraining organic performance, in plain language, with evidence from your own data. Not a template report.

A sequenced roadmap

Technical, content and authority work ordered by impact and effort, with dependencies made explicit. Usually planned a quarter at a time.

Implementation-ready specifications

Tickets a developer can pick up, briefs a writer can write from, redirect maps an engineer can deploy. The detail that most "recommendations" lack.

A measurement model

Which pages, queries and segments we expect to move, by roughly when, and how we will know. Tied to leads, signups or revenue, not rankings alone. I explain why in Rankings Are Not the Goal.

Knowledge transfer

Your team should be more capable when I leave than when I arrived. Documentation, walkthroughs and the reasoning behind decisions, so the system keeps running without me.

How an engagement runs

Scoping call
Thirty to sixty minutes on what the business does, what has been tried, who would own implementation, and what a good outcome looks like. I will say if I do not think I am the right fit.
Access and immersion
Search Console, analytics, CMS, logs, dev or staging. I read before I recommend. For larger sites this includes a full crawl and a log-file sample.
Diagnosis and prioritisation
Findings organised by what they constrain, ranked by impact and effort. This becomes the roadmap, usually planned a quarter at a time.
Implementation with your team
I write the specifications, join planning, review the work, and unblock developers and writers. In embedded engagements this is daily; in advisory, it is weekly.
Measure, learn, re-sequence
We check what moved against the model, update priorities, and plan the next block of work. Over time this is what makes the system compound rather than reset.

Examples of this work

Technical SEO and content architecture (Rahul Verma, Finance) — scaled monthly organic visits from 8k to 45k (+462% growth).

Organic growth for SaaS & compliance (Yogesh Pant, Digiliance) — 10+ high-ticket qualified leads/mo and citations in AI-generated answers.

10+High-ticket leads/mo (Digiliance)

>2xDoubled qualified B2B enquiries (Varun Mehta)

8k → 45kMonthly traffic growth (Rahul Verma)

I work with companies across India, with a concentration in Delhi, Gurgaon and Bangalore, and remotely with teams elsewhere.

Frequently asked questions

What is the difference between an SEO consultant and an SEO agency?

An agency provides execution capacity under a fixed scope, usually through a team that rotates across clients. A consultant provides diagnosis, prioritisation and direct accountability for decisions, and typically works inside your team's process. Many companies use both: a consultant to set direction and an agency or in-house team to execute.

Do I need a developer or a content writer to work with you?

Yes, or at least access to one. I write the specifications and briefs, review the work and own the outcomes, but someone has to implement. If you have neither, we should talk about that in the scoping call; sometimes the right first step is helping you hire or brief a freelancer rather than starting SEO work.

How long before we see results?

It depends on what is wrong. Technical fixes that unblock crawling or indexing often show within weeks. Content programmes and authority building take months, and compound over quarters. I will give you a realistic range for your specific situation after the diagnosis, and I will not promise rankings or dates I cannot control.

Can you work with our existing agency?

Yes, and I try to make the relationship productive rather than adversarial. In practice I set priorities and review, the agency executes, and everyone sees the same roadmap. If the agency is genuinely not the right fit, I will say so with evidence, not as a reflex.

Do you work with companies outside India?

Yes. Most of my work is remote. I bring specific knowledge of the Indian market, which matters for mobile-first behaviour, Hindi and regional-language search and local competition, but the underlying method applies anywhere.

Start with a conversation

If any of the situations above sounds like yours, the quickest way to find out whether I can help is a short call. Tell me what the site does, what has been tried, and what is in the way. I will tell you what I would look at first and which engagement model makes sense.

Work With Me See All Services