Ketoconazole (Topical) for Scalp Microbiome
Topical ketoconazole reliably lowers Malassezia yeast on the scalp and eases dandruff and seborrheic dermatitis, but evidence that it "improves scalp microbiome diversity" as a goal in healthy people is weak and preliminary. Treat it as an antifungal for flaking and itch, not a proven microbiome-balancing product.
Why this grade7-layer evidence engine
Only three small studies directly examine ketoconazole and the scalp microbiome. An open-label RCT (n=68, PMID 34416081) found 2% ketoconazole significantly reduced Malassezia (p<0.005), raised fungal diversity, and improved flaking and redness, but it was run and funded by shampoo-makers L'Oreal/Vichy, a notable conflict of interest. A facial cohort (n=45, PMID 35092701) showed shifting fungal diversity but reported no p-values and was not on the scalp.
A 2024 narrative review (PMID 39310465) pooled wider data confirming ketoconazole lowers Malassezia density and improves clinical signs, with one cited trial reporting 89% versus 44% responders on placebo (p<0.01). The clinical antifungal effect is well supported, but no high-quality meta-analysis uses microbiome diversity itself as the main outcome, and total enrollment across these studies is roughly 130 people.
Regulators back the antifungal use, not a microbiome claim: the US FDA labels it for topical use, and the UK NHS calls ketoconazole shampoo the most effective antifungal for seborrheic dermatitis. Clinics such as Cleveland Clinic list it only as a Malassezia treatment and never frame it as microbiome modulation. Because the real evidence covers yeast suppression in flaky-scalp patients rather than broad microbiome balancing, this earns a weak C grade.
Scoring transparency
All scores computed by a 7-layer evidence engine — fully auditable▸View the full decision path (audit trail)
- compute_raw_score — 加權公式: L2×0.30 + L3×0.25 + L5×0.25 + L11×0.10 + L1×0.10 = 0.655
- tier_from_score — 依分數區間映射至 tier letter
- apply_hec_rules — 高品質 SR/MA 顯示 positive (1 篇 > 0 negative)
- tier_strict_requirement_check — | B→C 因 scope.conflation_risk=true 且 L11 獨評較低 (B7-2 tier cap)
- detect_disputes — 偵測到 0 個 hard + 0 個 soft dispute
- decide_status — 依 tier + dispute 結果決定 status