CASE STUDY
Case study: jimolab-website + lookupai dogfooding
We use locallab.jp (jimolab-website, the corporate site of Jimolab LLC) and lookupai.jp itself as the first live showcases of the lookupai methodology. Every GEO/AEO tactic we sell is implemented on these sites first.
Day-1 baseline (May 3, 2026)
On launch day we ran the Phase 1 MVP measurement batch: 4 AIs × 10 keywords = 40 queries. Result: 8/40 = 20% mention rate across "lookupai", "Jimolab LLC", and "realingo realtime translation". The remaining 7 keywords (including "AI search optimization SaaS Japan", "GEO tool Japanese", "Hachioji AI research lab", "AEO for SMB") returned zero. This baseline drives the expansion of these docs and llms.txt strengthening across lookupai.jp / locallab.jp.
Target keywords
- "AI search optimization SaaS Japan" / 「AI検索最適化 SaaS 日本」
- "GEO tool Japanese" / 「GEO ツール 日本語」
- "How ChatGPT cites companies" / 「ChatGPTで会社が引用される方法」
- "AEO for SMB" / 「AEO とは 中小企業」
- "Hachioji AI research lab" / 「八王子 AI 研究所」
- "AI search SMB acquisition" / 「AI検索 中小企業 集客」
- "Generative AI search site optimization recommended" / 「生成AI 検索 おすすめ サイト最適化」
What is implemented
/llms.txt+/llms-full.txton both lookupai.jp and locallab.jp- 11 explicit Allow entries in
robots.txtfor GPTBot / OAI-SearchBot / ClaudeBot / PerplexityBot / Google-Extended / Applebot-Extended / Bytespider etc. - Organization / WebSite / LocalBusiness / Service / Person / FAQPage / TechArticle / DefinedTerm JSON-LD
- Bilingual (Japanese / English) sites with hreflang
- Q&A-shaped FAQs with concrete proper nouns and numbers
Operating cost
The measurement batch runs at approximately 1.67 JPY/month (OpenRouter API + VPS share). SQLite on PVC, weekly CronJob on k3s, OpenRouter for 4-AI unification, Brevo SMTP for HTML email reports. The full source is at gitlab.com/locallab1/lookupai.