SEO Specialist, 6+ years
Sakshi Kumari
Technical SEO, on-page and off-page optimisation, keyword research, content strategy and audits. Author of the AI answer extractability study and 28 articles on moxseo.com.
AdityaBhimrajkaFounder of MoxSEO, Chief Search Systems Architect.
Aditya Bhimrajka is the founder of MoxSEO and its Chief Search Systems Architect. He founded the company around one observation: search recommendations fail when technical, content, design, engineering and measurement decisions are made in isolation. His role is to keep them connected, from the first diagnosis through implementation and review.
- Role at MoxSEO
- Founder
- Articles published under his name
- 37
- Strategic direction and evidence standards
- Founder-led
- Day-to-day delivery
- Specialists
One accountable direction across disciplines
Founder-led does not mean every task depends on one person. It means the programme has a clear strategic owner.
That owner answers for problem definition, evidence standards, prioritisation, cross-functional tradeoffs and recommendation quality.
Aditya focuses on the decisions that materially affect outcomes: which constraints matter, which opportunity deserves investment, what must be true before release, how a claim should be supported, and what the resulting data does, or does not, prove. His published research covers enterprise technical SEO, knowledge graphs, large-scale indexing and generative engine optimisation.
The systems brought into the decision
Six working areas, evaluated together rather than handed between departments.
All services- Search architecture
- Information structure, internal links, indexability, entities, templates and customer journeys evaluated together.
- Technical SEO
- Rendering, performance, structured data, migrations, platform constraints and release risks translated into engineering decisions.
- Content systems
- Intent, evidence, editorial standards, reusable page models, subject depth and conversion paths designed for operation.
- AI discovery
- Crawler accessibility, answer extractability, source clarity and brand evidence assessed through observable website signals.
- Web product decisions
- Design and development tradeoffs reviewed for usability, discoverability, maintainability and business impact.
- Measurement
- Implementation records, leading indicators, qualified demand, conversion contribution and attribution limits made visible.
Where founder participation matters
Leadership context meets production reality when decisions cross boundaries. These tradeoffs are surfaced early and documented.
How we work- Commercial priorities versus technical debt
- Which fix earns investment now, and which waits.
- Speed versus durability
- Shipping quickly without creating the next migration problem.
- Content volume versus quality
- Publishing only what has a clear audience and purpose.
- Redesign ambition versus migration risk
- Protecting existing search value through every template change.
- Measurement certainty versus honest attribution
- Reporting what moved, and how confident the link to the work is.
How recommendations are challenged
Every strategic recommendation answers four questions before it reaches a client, and every finding behind it carries a confidence label.
How a finding is labelledExample
Finding
Category pages render their product grid only after JavaScript runs.
ObservationSeen on the rendered site or in the data, at a stated time, on stated pages.
What is observed?
Separate rendered-site evidence, customer behaviour, analytics and market data from assumptions.
Why does it matter?
Connect the issue to discovery, comprehension, user action, operational risk or commercial value.
What will change?
Define the page, template, component, workflow, owner and acceptance criteria required in production.
How will we learn?
Record the release and evaluate the appropriate technical, search, behavioural and commercial signals.
Research and client work are part of accountability.
Public work does not replace client-specific evidence, but it makes the reasoning standard visible before a sales conversation.
Founder questions
How founder-led delivery works in practice.
Aditya Bhimrajka is the founder of MoxSEO and its Chief Search Systems Architect. He owns strategic direction, problem definition, evidence standards, prioritisation, cross-functional tradeoffs and the quality of every recommendation that leaves the studio.
Involvement depends on scope, but strategic direction, major prioritisation decisions and quality standards remain founder-led on every MoxSEO engagement. The proposal states who is responsible for what, so you know where founder judgment applies.
MoxSEO specialists handle research, content, engineering, analytics and delivery tasks according to the engagement, led day to day by SEO specialists Sakshi Kumari and Ashish Khan. Ownership and review stages are documented in the proposal and the delivery record.
Yes. Advisory work suits capable internal teams that need diagnosis, decision support, implementation-ready specifications, migration oversight or independent validation, while their own developers and editors ship the changes.
Share the website, business model, priority markets, current constraints, previous SEO work, who owns implementation and the decision you need to make. Do not send passwords or production credentials; access is agreed separately if an engagement proceeds.
Run day to day by two specialists
Aditya sets direction and evidence standards. Sakshi Kumari and Ashish Khan run the work, take the strategy calls and sign the research they publish.
SEO Specialist, research contributor
Ashish Khan
Keyword research, technical SEO, content strategy and link building. Author of the AI crawler-blocking study across 506 domains and 42 articles on moxseo.com.
Search, technical, content, analytics, design and engineering responsibilities are assigned around each engagement.
Team and responsibilitiesWhere the direction was applied
Research Aditya's team put their names to, and client projects where architecture, templates, intent and measurement had to work as one system.
Original research
3%of 243 top websites were structurally quotable by AI answer engines.AI answer extractability study, Sakshi Kumari2xAcross 506 top sites, AI training crawlers are blocked about twice as often as AI retrieval crawlers.AI crawler-blocking study, Ashish Khan16%of 148 businesses scanned in 20 cities sign their work with a visible author and date.City market AI readiness studyClient work
Miracuves: software catalogueCatalogue SEO across 3,000 URLs of product, industry and solution pages, a scope figure.
- BookBoatsNow: rental marketplace
Marketplace search foundation from a fresh domain.
- MyRIDI: urban mobility platform
800K+ organic search impressions in year one.
Bring the decision
that needs accountable direction.
Share the website, the commercial context, your current evidence, ownership and constraints. In a free 30-minute call, Sakshi Kumari or Ashish Khan name the first move that fits the system you operate.
A call is not an engagement. We never guarantee rankings, traffic or revenue.