Multilingual SEO Analytics: Track Each Language in GSC & GA4

Summarize this post with: 10 min read

Multilingual SEO analytics means measuring search performance separately for each language version of your site instead of as one global total. In practice you filter Google Search Console by language folder and country, segment Google Analytics 4 by the same language path, and compare impressions, CTR, rankings and conversions market by market so you know which locale to fix or fund next.

Below is how to set that up, which numbers to watch, and how to read the patterns that show up.

Key takeaways

Segment by the URL of each language version (/de/, de.example.com) rather than by the visitor’s browser language. That only works if every language has its own indexable URL.
In Search Console, use a page filter for each language plus a country filter. Regex filters let you group many pages at once.
In GA4, build a “language version” dimension from the page path. GA4’s built-in Language dimension is the browser setting, which is a different thing from the page language.
Read each market on its own. Impressions show demand, CTR shows whether your translated titles earn the click, and conversion rate shows whether the localized page does its job.
Review monthly, re-rank markets quarterly, and check hreflang and indexing whenever a locale drops suddenly.

Multilingual SEO analytics workflow diagram The loop: research markets, measure each language separately, review in a dashboard, fix, repeat.

Why site-wide totals mislead

Picture a SaaS site in English, Spanish, German and French. Global organic traffic is up 20%, so the report looks healthy. Split it by language and it reads differently:

German has modest traffic but converts well.
Spanish has the most sessions and the weakest engagement.
French gets plenty of impressions and few clicks.
English still gets most of the branded search.

One line chart shows none of this. Each problem has a different fix (better German content, a better Spanish landing experience, better French titles), and you only see them when every report is split by language.

Step 0: make sure each language is measurable

Analytics can only separate what search engines can separate. Before you measure anything, check that:

Every language has its own URL: a subfolder (/de/), subdomain (de.example.com) or separate domain. A translation that only appears after a cookie or script runs will not show up in Search Console as its own set of pages. Google recommends distinct URLs for each language and advises against switching content by IP or browser settings (Google Search Central).
Hreflang tags are in place and reciprocal, so Google shows the right version to the right audience. See our complete hreflang guide.
Titles and meta descriptions are translated. Untranslated metadata is the most common reason for poor CTR in non-English markets.
Your analytics tag loads on every language version, subdomains included, and those subdomains are covered by the same GA4 data stream or a cross-domain setup.

If your language versions live on subdomains, add each one to Search Console as its own property, or use a Domain property that covers them all.

Step 1: Search Console by language

Search Console shows you demand (impressions), visibility (position) and how often people click (CTR) for each language.

Start by filtering on the language folder. In the Performance report, add a Page filter. For a single language, “URLs containing /de/” is enough. To group several, choose Custom (regex). Search Console uses RE2 regular expressions, so for example:

/(de|at|ch)/ groups German-language folders for three markets.
/(de|fr|es)/ with Doesn’t match regex isolates your source-language pages when the other languages sit in folders. (RE2 has no lookaheads, so use the “doesn’t match” option instead of writing a negative pattern.)

Then add a country filter. If a German page earns most of its impressions outside Germany, Austria and Switzerland, there is usually an hreflang or targeting problem.

Use Compare to set the last 28 days against the previous period for each language. If impressions rise and clicks stay flat, your snippets are the problem, not your rankings.

Finally, check indexing for each language. In the Pages (indexing) report, filter by the same folder. A language where most URLs sit in “Crawled, currently not indexed” or “Alternate page with proper canonical tag” has a technical problem rather than a content one.

To get the same data outside the interface, use the Search Console API or the free Looker Studio connector. Both support page and country dimensions, and that is how most teams build a dashboard per language.

Step 2: GA4 by language version

GA4 tells you what happens after the click, with one trap. Its built-in Language dimension is “the language of a user’s browser or device,” and Country is where the activity came from (GA4 dimensions reference). Neither tells you which language version of your site someone used. A Spanish speaker in the US with an English browser who reads your /es/ pages shows up as English, United States.

Segment by the page path instead:

In Explore, create a free-form exploration.
Add the dimensions Landing page + query string, Session default channel group and Country.
Add a filter: Session default channel group exactly matches Organic Search.
Add a filter on Landing page for each language folder, or create a custom content group (set in your tag) whose value is the page language.

For subdomains, use Hostname as the language dimension instead of the path.

Then add the metrics you care about: sessions, engaged sessions, engagement rate, key events (conversions), and revenue if you track it.

Step 3: the metrics worth tracking per market

Metric	Where	What it tells you
Impressions	Search Console	Demand you are visible for in that language
Average position	Search Console	How competitive your localized pages are
CTR	Search Console	Whether translated titles and descriptions earn the click
Indexed pages	Search Console	Whether search engines accept the language version at all
Organic sessions	GA4	Traffic delivered to that language version
Engagement rate	GA4	Whether the page matches local intent
Conversion rate	GA4	Whether the localized journey (prices, trust, checkout) works
Revenue or pipeline per session	GA4 or CRM	Which market deserves the next investment

Pair each visibility metric with an outcome metric. A market with half the traffic and twice the conversion rate is often the better bet.

Step 4: compare markets fairly

Raw traffic favours big markets. For a fair comparison, look at efficiency and trend inside each market:

Share of available demand: your impressions divided by the market’s search volume for your core terms, taken from a keyword tool set to that country.
Trend: the month-over-month change in clicks and conversions for each language.
Efficiency: conversions per 1,000 organic sessions.

Rank markets into three groups: invest (efficient and growing), fix (demand exists, results lag) and hold (small demand, fine as is). Re-rank every quarter, because algorithm updates, new competitors and your own new content keep changing the order.

Step 5: read the pattern and fix the right thing

What you see	Likely cause	What to do
High impressions, low CTR	Titles and descriptions translated literally or not at all	Rewrite localized titles using local keywords; test two versions
Good rankings, little traffic	You rank for terms nobody searches in that language	Redo keyword research with a native speaker
Traffic but low conversion	Prices, payment methods, shipping or trust signals not localized	Review the full journey in that market, including checkout
Pages missing from the index	Hreflang errors, canonicals pointing to the English page, or blocked language folder	Audit hreflang reciprocity and canonicals; check robots rules
Wrong language ranking in a country	Missing or incorrect hreflang, no `x-default`	Fix hreflang and add `x-default`
Sudden drop in one language only	Deployment removed hreflang, a folder was noindexed, or translations stopped updating	Compare the page source before and after the drop

For keyword work per market, see how to translate SEO keywords for different global audiences. For the structure decision, see subdirectories vs subdomains.

Step 6: turn analytics into a routine

Once a month, spend about 30 minutes per language comparing clicks, impressions, CTR and conversions with the previous month, and look at the 10 pages gaining and losing the most.
Once a quarter, re-rank markets, refresh keyword research for the top market, and review the lowest-CTR pages in each language.
After every release, spot-check hreflang and canonicals on a few pages in each language.

Feed what you learn into the content plan. Publish more of what already works in a market, and send high-traffic, low-conversion pages to a native speaker for review. Our translation quality workflow explains how to organize that review.

How ConveyThis makes language versions measurable

Most measurement problems start upstream, with language versions that search engines cannot tell apart. ConveyThis multilingual SEO publishes each language on its own URL (subfolders, subdomains or ?lang, plus second-level domains on the Extreme plan), adds hreflang tags automatically, and translates page titles, meta descriptions and JSON-LD. Search Console and GA4 then have separate language versions to report on from the first day.

When the data turns up a problem, you fix it in the same tool: the visual editor for rewriting a weak translated title in context, a glossary to lock the local keywords you want used, and team roles so a native reviewer can own each language. Words are counted only when a translated page is shown to a visitor, and bots do not count, so search engine crawling does not eat into your plan.

Frequently asked questions

How do I measure multilingual SEO performance? Filter Search Console by each language’s URL folder or subdomain and by country, segment GA4 organic traffic by the same paths, and compare impressions, CTR, rankings, engagement and conversions per language.

Can I use GA4’s Language dimension to separate language versions? Not reliably. It reports the visitor’s browser or device language, not the version of your site they viewed. Use the page path, hostname or a content group instead.

Why does one language get impressions but few clicks? Usually because titles and meta descriptions were translated literally or left in the source language. Rewrite them around the terms local searchers use.

How often should I review multilingual SEO data? Monthly for trends and quick fixes, quarterly for market prioritization and keyword research.

If you would rather not build measurable language versions by hand, start with ConveyThis.