Case 03 — Terence Tsang · QQS · 燒鳥串
Actualizado Agosto 2026
Winning consideration for “best omakase” and “best yakitori” in Hong Kong
F&B · Omakase & Yakitori
Cliente: QQS Hospitality Consulting — Terence Tsang
Premium omakase and yakitori discovery in Hong Kong was dominated by listicles and review platforms. The venues had excellent product — but thin, non-citeable web structure, so AI answers defaulted to generic “best of” roundups.
Línea Base
AI shortlists cited third-party lists. No Restaurant/LocalBusiness schema, no bilingual “what defines great omakase / 燒鳥串” blocks, weak entity disambiguation vs similarly named venues.
Intervención
- Built answer architecture around comparison criteria AI can quote: chef narrative, course structure, sourcing, price-band transparency, reservation path
- Deployed Restaurant / LocalBusiness schema with menu and offer clarity
- Created bilingual FAQ and educational blocks for omakase and 燒鳥串 / yakitori
- Strengthened entity disambiguation vs similarly named venues and city-wide list pages
- Aligned booking CTAs so AI summaries could point to a clean next step
Cronograma
12-week programme. Eligibility and answer-structure outcomes below — unpublished Orbit figures stay under NDA.
Lo que lo hizo funcionar
F&B GEO is local entity work. Signature dishes, chef, neighbourhood and booking path have to be machine-legible or the listicle remains the source.
what changed — 12-week programme
- queries
- best omakase in Hong Kong · best yakitori · best 燒鳥串
- eligibility
- Clearer eligibility in AI shortlists for premium dining intent
- density
- Stronger on-site answer density for comparison queries
- citation_path
- Reduced reliance on third-party listicles as the only citeable source
Tu línea base a continuación
Obtenga las mismas tres métricas para su marca.
La auditoría gratuita de visibilidad de IA establece su línea base de Citation Frequency, Share of Voice y Recommendation Rank, el mismo punto de partida con el que comenzó cada caso anterior.
Escrito por James Huang, Fundador y CEO, Mercury Technology Solutions · Revisado por la Práctica Mercury GAIO · Actualizado Agosto 2026