Reference Implementation №1 · est. 2026
AI Native MEO
The first reference implementation of the LLMO Framework, applied to local businesses — for the era when customers ask AI, not search engines, for recommendations.
While terms like AEO and GEO circulate in the AI-search optimization space, LLMO (Large Language Model Optimization) has emerged as the most precise framework. AI Native MEO is its local-business specialization.
Definition
What AI Native MEO is
Traditional MEO (Map Engine Optimization) targeted Google Maps rankings. AI Native MEO targets the next layer: being cited and recommended by generative AI systems — ChatGPT, Gemini, Claude, Perplexity — when users ask for local recommendations in natural language.
This site is the engineer's perspective on that shift, written from the LLMO Framework standard, not from a marketing agency's vantage point.
Recent entries
All articles →- 01
Established vs Newly Opened: The Cold-Start Asymmetry in How AI Assistants Cite Local Businesses
An established business and a newly opened one can publish the same Google Business Profile fields and be treated as utterly different entities by an AI assistant. The reason is a cold-start asymmetry: four signals that an old business has accumulated and a new one structurally cannot, and the way each engine reasons about their absence. A comparison of where the asymmetry lives, what compensates for it, and why the trap of faking maturity is worse than admitting youth.
- 02
Modeling Reviews and aggregateRating in JSON-LD: How AI Assistants Build a Local Business's Reputation Layer
An engineer's reading of Review and aggregateRating as a nested schema graph: how `Review`, `reviewRating`, `aggregateRating`, `reviewCount`, and `bestRating` actually wire onto a `LocalBusiness` or `Place` node, why an `aggregateRating` without individual `Review` children quietly loses confidence inside an AI assistant, and how the four major engines resolve the provenance conflict when your first-party schema says one number and Google Business Profile says another.
- 03
Service Area in JSON-LD: How AI Assistants Cite Plumbers, Mobile Hairdressers, and Other Businesses That Come to You
An engineer's read of how service-area businesses should encode themselves in JSON-LD: GeoCircle vs AdministrativeArea vs containedInPlace, providerMobility, and why AI assistants treat a plumber's 'where' very differently from a cafe's.