Free AI check Book a strategy call

The peoplewho runMoxSEO

The MoxSEO team is led by founder Aditya Bhimrajka and run day to day by SEO specialists Sakshi Kumari and Ashish Khan, with SEO associates Samruddhi Kadam and Yash Narayan and contributor Rutuja. Specialists are organised around the work, not account-management layers, and everyone here signs what they publish.

Articles published under each person's own name on moxseo.com151
  1. Ashish Khan42
  2. Aditya Bhimrajka37
  3. Sakshi Kumari28
  4. Samruddhi Kadam27
  5. Yash Narayan16
  6. Rutuja1
Source: moxseo.com author archives, October 2026
The two specialists you will work withThey take every strategy call

Sakshi KumariPlaceholder

SEO Specialist, 6+ years

Works across technical SEO, on-page and off-page optimisation, keyword research, content strategy, audits, competitor analysis and organic growth.

She focuses on organic visibility, website performance and search-focused content that attracts relevant traffic. Her documented authorship includes MoxSEO's search guides, such as the local SEO strategy guide, and its answer-extractability research.

243Sites scored for the AI answer extractability study. Only 3% were structurally quotable.Read the study28Articles published under her nameAuthor page
Book a call with SakshiLinkedInTry the extractability checker

Ashish KhanPlaceholder

SEO Specialist, research contributor

Works on keyword research, on-page optimisation, technical SEO, content strategy and link building, combining competitor analysis and SEO audits with data-driven optimisation.

He is the named author of MoxSEO's AI crawler-blocking study, which separates AI training crawlers from answer-retrieval crawlers across 506 domains.

506Domains in the AI crawler-blocking study. 104 of them block at least one AI crawler.Read the study42Articles published under his nameAuthor page
Book a call with AshishLinkedInUse the AI crawler access checker

Everyone who signs work on moxseo.com

Direction, associates and contributors. Roles and bios are taken from each person's author record; nothing here is written for the brochure.

  1. Aditya Bhimrajka

    Founder & Chief Search Systems Architect

    Leads research in enterprise technical SEO, knowledge graphs, large-scale indexing and generative engine optimisation, and keeps strategic direction and evidence standards founder-led.
    Read the founder profile

    37articles

  2. Samruddhi Kadam

    SEO Associate, 2 years

    Keyword research, on-page SEO, content optimisation, competitor analysis and website performance tracking.
    Author page

    27articles

  3. Yash Narayan

    SEO Associate, 3 years

    Keyword research, on-page SEO, content optimisation, competitor analysis and website performance monitoring.
    Author page

    16articles

  4. Rutuja

    Content contributor

    Writes practical SEO checklists and process guides for teams managing search in-house.
    Author page

    1article

Sakshi Kumari and Ashish Khan are featured above. Named biographies and portraits are added only when names, roles, profile details and consented photographs are on file.

Three responsibilities, one decision record

Search performance rarely belongs to one department. Work is organised around the website and the customer journey, then each decision goes to the specialist qualified to make it, with explicit owners, reviewers and handoffs instead of a chain of account-management layers.

Search & technical

Architecture and implementation responsibility

  • Crawl access
  • Rendering
  • Indexability
  • Templates
  • Internal links
  • Schema
  • Performance
  • Migrations
  • Release validation

Content & research

Evidence and information responsibility

  • Customer questions
  • Subject coverage
  • Source quality
  • Editorial standards
  • Page models
  • Extractability
  • Corrections

Design, engineering & data

Experience and measurement responsibility

  • Components
  • CMS workflows
  • Accessibility
  • Conversion paths
  • Analytics definitions
  • Testing
  • Dashboards
  • Production QA

What each discipline contributesSix disciplines are drawn on as the scope requires.

Search strategy
Defines intent, opportunity, priorities, tradeoffs and the connection between visibility and commercial goals.
Technical SEO
Inspects crawling, rendering, indexability, templates, schema, performance, migrations and platform behaviour.
Content strategy and editing
Turns customer questions and evidence into useful structures, briefs, standards and maintainable content systems.
Design and engineering
Builds or changes components, templates, CMS workflows, e-commerce experiences and conversion paths while protecting discovery.
Analytics and research
Defines events, evaluates demand and behaviour, supports original studies, and communicates confidence and limitations.
Programme delivery
Maintains the decision record, owners, dependencies, acceptance criteria, release checks and communication cadence.

Reviewed where mistakes happen

Four review boundaries, in this order, on every piece of work that reaches production.

  1. Evidence review

    The finding comes from the rendered site, reliable data, customer context, or a labelled hypothesis.

  2. Specification review

    Owners understand what changes, why it matters, the dependencies and the acceptance criteria.

  3. Production review

    The released page, template, event or workflow is validated, not assumed to match the brief.

  4. Outcome review

    Results are compared with the original decision, exceptions recorded, future priorities updated.

Scope decides the team

Not the other way around. The proposal names the disciplines required, your owners, the dependencies and the review stages before anyone starts. Specialists are added because the work needs them, not to make the team look larger.

Your team is part of delivery. Product owners know roadmap constraints, sales and support hear customer language, engineers know platform risk, legal teams set boundaries and leadership sets commercial priorities. A shared decision model puts that context into the work before recommendations are written.

A crawl, rendering and indexability problem needs depth, not headcount.

  • Search architect
  • Engineer
Example compositions from the MoxSEO team modelOrange added for this scope
  • Named owners
  • Written decisions
  • Visible blockers
  • Recorded validation

Decisions should not disappear inside meetings.

Will we have a single point of contact?
Yes, while keeping access to the specialists responsible for important decisions. Communication should reduce ambiguity rather than hide expertise.
Can the team work inside our existing tools?
Where appropriate, work runs in your project management, documentation, analytics, design, development and release systems.
Can MoxSEO augment an existing team?
Yes. An engagement can cover a missing specialty, an independent review, a temporary delivery gap, or an initiative that crosses teams.
How is accountability kept?
Every task connects to a decision, owner, evidence, dependency, acceptance criteria, release state and measurement plan.

Where the team model shows up in client work

+340%Dermacian: local discovery, treatment information, technical foundations and enquiry journeys for a dermatology clinic.Read the project3,000Miracuves: URLs in a catalogue where content models, templates, technical controls and measurement needed shared ownership.Read the project3,000+URview: signups from organic search in six months, linking launch, discovery, content, conversion and measurement.Read the project
See how work reaches production Service capabilities

Bring the decision
that needs accountable direction.

Share the website, the commercial context, your current evidence and who owns what. In a free 30-minute call, Sakshi Kumari or Ashish Khan, the specialists who run MoxSEO, name the first move that fits the system you operate.

Book a strategy callOr email contact@moxseo.com

A call is not an engagement. We never guarantee rankings, traffic or revenue.