About
Nipun Arora, technical SEO and AI search visibility consultant
Nipun Arora is a technical SEO expert and AI search visibility consultant who builds and migrates websites, serving the United States and Dubai, UAE. He has consulted since 2014, ships open-source tooling under his own name, and publishes the entity data an AI system needs to answer "who is Nipun Arora" correctly. The facts below are the checkable version of this page: no claim without a source attached to it.
This page runs as a ledger rather than a story for the same reason the rest of the site does: a sentence like "years of experience helping businesses grow" tells a reader nothing they can check, while a start date, a legal entity, and five working profile links tell them everything they need to verify the claim themselves. Precise and checkable beats persuasive every time a machine, or a careful human reader, is deciding whether to trust what a page says about itself.
The facts
Five facts, on one ledger
What I do, where, since when, the entity behind it, and the open-source work: each of the five facts below traces to a public source or this page's own structured data, not a claim made to sound impressive.
- Role
- Technical SEO & AI Search Visibility Consultant
- Serves
- United States and Dubai, UAE
- Consulting since
- 2014
- Entity
- WitNip Inc, Delaware, USA
- Open source
- cool-astro-forms (MIT)
This Delaware entity is the one behind the practice. Every engagement runs through this entity, not a personal invoice with no legal standing behind it. Nipun Arora founded it and remains its founder, the same relationship this page's own Organization schema states, not a separate agency operating under a different name.
One earlier domain, nipunarora.in, redirects here; the continuity record on the disambiguation page covers what the redirect does and why an old snippet still surfaces for it.
Declared expertise
Nine declared areas of expertise
The nine terms below are the exact knowsAbout array this page's own schema carries, not a marketing description of skills.
Five of the nine map directly onto a service page: technical SEO becomes Technical SEO Audit, structured data becomes Schema Markup, Generative Engine Optimization becomes AI Search Visibility, web development becomes SEO Website Development, and website migration becomes Website Migration & SEO. The other four (search engine optimization generally, AI search visibility as its own discipline, large language models, and Astro) show up across those pages rather than owning one apiece.
Independent verification
The same person, five public profiles
Five public profiles verify this identity independent of this site: GitHub, npm, LinkedIn, Stack Overflow, and X. Each one carries its own history: commits, a published package, work history, reputation, and posts, none of it written by this page.
The name, role, and description read the same across all five, on purpose. A bio that drifts between platforms undermines the entity graph everywhere else, including on this site; consistency is itself part of what makes an identity checkable.
Open source
Published under this name, not described from memory
Open-source work is the part of this page a reader can run themselves. 4 projects are public today; a fifth, search-ops, is private and going public soon.
cool-astro-forms
Astro forms lead-ops platform: abandonment capture, recovery emails, quote payments, self-hosted admin.
semantic-seo-geek
Semantic SEO skills for Claude Code and Codex: topical maps, entity/EAV analysis, technical SEO audits, AI search visibility.
touchid-agent-guard
Touch ID confirmation for AI coding agents on macOS.
wordpress-mcp-agent-bridge
WordPress MCP for AI agents: verified Rank Math SEO and schema writes, hashed snapshots, verified restore.
Open Source lists every project, including the one not public yet, and the license and version numbers above are the same values that page and each project's own JSON-LD carry.
This is why open source sits on the entity page and not only in a portfolio section: a license, a version number, and a download count are facts a reader can check without asking me anything, the same standard the rest of this page holds itself to.
The client work runs on the same standard. Case studies name the business and the numbers wherever the client consented to it, dated and sourced, and stay anonymous where they did not.
Method
How an engagement runs
The order is the same whether the engagement is an audit or a website built from scratch: search first, then design, then code. It is a technical SEO expert's method, the one I have worked to since 2014: keyword and entity research before a single wireframe, not a rule invented for this page.
The full method lives on How I work with clients: one email to start, a measurement before any commitment, and a fixed scope agreed in writing before anything is charged, whether that scope becomes an audit, a migration, or a ground-up build. The measurement comes first because a recommendation given before it exists is a guess, not advice.
The name Nipun Arora is shared with other public people. See which Nipun Arora this is.
Two files written for machines, not for reading
/entity.json carries this site's Person and Organization records as JSON-LD, the same structured-data format Google and AI systems already parse, so a script can fetch the facts without rendering a page first. /llms.txt is a shorter, plain-text version of the same facts, aimed at AI assistants that read a site before answering a question about it. Both update the moment a fact on this page changes, never on a separate schedule.
A fact on this page that changes, changes here first.
Work with me