Ir al contenido
Mercury .

Case 01PCCW · Bruce Lam · HK / GBA

Actualizado Agosto 2026

Clarifying “best premium mobile operator” beyond price tables

Telecom · Premium mobile

Cliente: PCCW — Bruce Lam

“Best mobile” queries collapse into price comparison. PCCW’s premium positioning was getting flattened. AI answers needed extractable proof of service quality, plan architecture and differentiators — not another feature dump — including a GBA track that does not assume Hong Kong Gemini visibility transfers to mainland assistants.

Línea Base

Premium-operator consideration answers defaulted to price tables. Brand entity mixed with MVNO / budget operators. Gemini visibility in Hong Kong did not appear on mainland assistants.

Intervención

  • Rebuilt premium proof into AI-extractable matrices: plans, support SLAs, device tiers, coverage narrative
  • Separated brand entity from MVNO / budget operator confusion
  • Created objection FAQs (value vs price, premium vs mass, business vs consumer)
  • Technical GEO pass: offer/schema clarity, canonical plan pages, internal link hierarchy
  • Dual-track GBA measurement so HK and mainland citation surfaces are improved separately

Cronograma

12-week programme. Eligibility and answer-structure outcomes below — unpublished Orbit figures stay under NDA.

Lo que lo hizo funcionar

Assistants quote what they can parse in one pass. Premium is a proof structure — SLAs, plan architecture, entity hygiene — not a slogan on a price table.

what changed — 12-week programme

query
best premium mobile operator
eligibility
Stronger framing in premium-operator consideration answers
separation
Clearer split from pure price-led recommendations
cross_border
Dual-track so GBA citation is not assumed from HK Gemini visibility

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