Per-Language Analytics: The Dashboard Multilingual Sites Actually Need

Most multilingual sites fly blind: traffic aggregated, languages invisible, localization decisions made on vibes. Path-based language URLs make the fix almost embarrassingly simple.

The five-minute GA4 setup

Create comparisons filtering page path begins-with each language prefix. Add conversion and revenue columns. You now have product-line P&L per language (reference).

Search Console’s underused trick

Submit per-language sitemaps and the Pages report decomposes indexing by locale — catching “German is half-deindexed” class problems while they’re cheap. Country report adds where demand leaks from markets you haven’t localized: your expansion queue, pre-validated.

Decision rules worth stealing

Locale converts ≥ site average → expand its content. Traffic fine but conversion lags → human-polish the money pages (MTPE). Impressions rising in an unserved country for two straight months → ship that language. Boring rules, compounding returns.