MegaCMO Research · Published report preview

STAR CLINIC

STAR CLINIC is a multi-site medical brand built on self-pay aesthetic medicine and extended into dental, rehabilitation, functional medicine, and preventive medicine, with eight service categories, a branch directory, and a physician directory folded into one filterable interface whose navigation advertises 272 services, 31 locations, 129 physicians, and 13,312 documented cases. Its growth friction is not at the top of the funnel but in three places. First, the public scale numbers share no common definition: the homepage claims more than 500,000 cumulative users, the about page claims 21-plus locations and more than 18 years, a third-party expo listing says 20 clinic sites, a business magazine reports 32 designated partner institutions and 400,000 users for the affiliated company STARNIC rather than for the clinic brand, and the MOHW national dataset dated 2024-12-31 lists 14 licensed institutions carrying 星和 in their name across eight cities and counties. For a brand whose product is trust, that spread is the most expensive leak it has. Second, the technical assets and what is actually indexed have come apart: the sitemap declares 10,871 URLs that all share one lastmod of 2026-07-10, of which 6,600 take the form /service/{uuid}?serviceCode= and 66 more are bare UUID service paths. Every one tested returns a 301, and the redirect target does not match the serviceCode in the URL, so a request for ellanse lands on botulinum-toxin-injection. Nine /Error/404 URLs are declared and answer with HTTP 200. Against that, only 36 of 456 knowledge-base articles, 62 of 129 physicians, and 24 of 31 branches are declared at all, and no page tested carries a canonical tag. Third, the only conversion action on the entire site is a consultation form plus a phone line and messaging, with no self-serve confirmation, reschedule, or cancel, so every unit of intent is handed back to a manual callback. The good news is that the foundation is better than the surface suggests: robots.txt already grants GPTBot, ClaudeBot, and PerplexityBot full crawl access, treatment pages already ship Service and MedicalProcedure, FAQPage, and BreadcrumbList structured data, physician pages already ship Person markup alongside specialty, education, career, and certification detail, and the service menu data layer already maps every service to the branch IDs that deliver it. What is missing is coverage, canonicalisation, and exposure rather than capability, and that whole path can be executed without touching efficacy, before-and-after, or price claims.