SEO Consultant in India
I am Harsh Sharma, based in Gurugram. Nine years running organic search for sports media, iGaming, publishing and SaaS, and right now five English speaking markets on one domain. If your site should be doing better in search and nobody can tell you why, that is the problem I am good at.
Companies and sites I have worked on
What I can help with
Technical audits
I go through the site the way a crawler does rather than the way a tool does. Log files, Search Console, rendering, and the architecture underneath. Most of my work is as a technical SEO consultant.
Site migrations
The riskiest thing you can do to a site, and the thing most often done badly. Redirect mapping, indexation monitoring, and someone watching the numbers for weeks after launch rather than declaring it done on day one.
International SEO
Subdirectory structure, hreflang that validates, and market level keyword research to decide what actually needs localising. I currently run five English speaking markets on one domain, which is the hardest version of this.
Editorial and content systems
I have run SEO inside newsrooms publishing hundreds of pieces a week. The fix at that scale is never a better article, it is a better process. Written up in my editorial SEO systems.
Internal linking and architecture
Most sites leave authority routing to whatever the writer remembered to link. I map the link graph and design crawl paths deliberately, using an internal linking framework rather than a rule of thumb.
AI workflows for SEO teams
Built with Claude, ChatGPT and MCP for teams I was already running. Internal linking dashboards, daily rank reports, automated briefs. Detail on my AI assisted workflows.
How working together usually looks
Three shapes, depending on what you need. Prices depend on scope, so I quote before anything starts.
Technical audit
I go through the site properly and hand back a prioritised list your developers can action, with the reasoning behind each item so you can argue with it.
- Crawl and index review, plus log file analysis where logs exist
- Rendering check on how much of the page a crawler actually gets
- Site architecture and internal linking review
- A ranked fix list, separated into what your team can do and what needs engineering
You know what is holding the site back, and what to do first.
Project work
A defined piece of work with a start and an end. Usually a migration, a new market launch, an architecture rebuild, or recovering from a penalty.
- Redirect mapping and migration planning
- hreflang and subdirectory setup for new markets
- Site architecture and internal linking design
- Indexation and performance monitoring through launch and after it
The thing ships, and someone who has done it before is watching what happens next.
Advisory retainer
A regular slot for teams who already have people but want someone senior in the room. Usually a few hours a week.
- Roadmap and prioritisation calls
- Reviewing specs before they get built rather than after
- Reporting your team will actually open
- Standing in on the technical arguments with engineering
Your team keeps ownership of the work and stops guessing.
Not sure which one fits? Send me the site and what you have already tried and I will tell you what I would look at first.
How I work
The order I work through a problem in, and why that order.
Find the actual problem
Most SEO problems are misdiagnosed. Before anything gets changed I want to know what is really happening, which usually means log files and Search Console rather than a tool score out of a hundred.
Fix the structure before adding volume
More content on a broken structure just gives you a bigger broken site. Architecture, crawl paths and internal linking come first.
Build it so it keeps working
If a fix only holds while someone does it by hand every week, it is not finished. I would rather leave a process behind than a task list.
Work with the people who ship
SEO that lives in a separate deck never lands. I sit with product, engineering and content, and write specs they can build from without a translation layer.
Stay through the part after launch
The interesting part of a migration is the six weeks after it, when indexation settles and the rankings tell you what you actually did. Most people have moved on by then.
"Most SEO problems are misdiagnosed. The work is finding out what is actually happening before touching anything."
Work I can point at
Three problems from the last few years, with the numbers attached and the company named. The full write ups are on the homepage.
Getting a site out of a Google manual action
A penalty had taken the organic traffic out. Cleaned it up, rebuilt the architecture, got the traffic back.
Opening three new markets on one domain
Subdirectory structure and hreflang across five English speaking markets, with conversions up 60% month on month.
Scaling a cricket platform through an IPL season
Season traffic went from 5M to 25M, with organic visibility up more than 200% year on year.
Frequently Asked Questions
Tell me what is not growing
Send me the site and what you have already tried. I will tell you what I would look at first, whether or not we end up working together.






