Obi for Technical AEO
Obi checks what AI crawlers and agents can read on your site, and hands you the exact fix.
npm i -g @hireobi/cliThe job
You own how machines read the site: crawlers, rendering, structured data, llms.txt. An AI answer can only cite what a crawler can read.
Where it hurts today
- JavaScript pages AI crawlers never see.
- robots.txt rules nobody checked crawler by crawler.
- Training crawlers and answer crawlers mixed up.
The workflow with Obi
From the agent you already use. Each step is one command.
- Check what AI can read
Crawler access, indexability, JavaScript pages, structured data and llms.txt, each finding with its fix.
obi readiness - Apply the patch
A robots.txt fix comes as an exact patch, the line that decides named.
obi readiness - Open the pull request
Obi opens pull requests on your repository for the pages and docs it writes.
obi harness artifact - Read the scans
A scan after the fix, to see what the engines answer now.
obi questions results
Where it plugs in
- GitHub
Obi opens pull requests on the product's repository for the pages and docs it writes.
- Mintlify
Obi publishes the product's docs ready for agents, as Markdown pages with an llms.txt file.
- Google Search Console
Obi reads the queries, the indexing, and the impressions in Google's AI features.
What stays in your hands
- Obi recommends and drafts. It never publishes, sends outreach or buys anything on its own.
- Every command that starts paid work takes your explicit yes.
- Your secrets and the rest of your workspace stay on your machine.
Start with your own buyers' questions.
Hire for free