Multilingual Google Ads campaigns for Switzerland

Language and region are two separate decisions

The obvious set-up goes like this: German for German-speaking Switzerland, French for Romandy, Italian for Ticino. I consider it wrong, because it mixes up two questions. The region governs where you release budget and where you deliver. The language governs which search query you can serve properly, and that depends on what you actually have in place: ad, landing page, product data. Someone searching in French in Zurich belongs in your French campaign, and someone searching in German in Lausanne belongs in the German one.

Two separate business decisions follow from this. The target area is a question of delivery and offer. The language version is an investment with running costs that has to pay for itself.

What language targeting still controls

Much less than the old setting suggests. As of November 2026, according to Google, the situation is as follows:

Whether the setting is still visible in your account makes little difference to the logic. For search queries in a clear language, according to Google, ads and landing pages in that language take priority. For queries without a clear language, such as brand names, the user's preferred language counts. Google also checks whether someone understands the language of the ad and landing page, which is why an ad can appear for a query in another language.

You cannot exclude a language: according to Google, quoted by PPC Land, a language that has not been selected does not count as excluded. For you this means you control language through the offer you build, not through a setting. If the French ad is missing, at best you serve French queries with a German one.

How I would build the structure for Switzerland

1. Separate Search campaigns for each language, with keywords and ads in exactly that language. Separate single-language campaigns continue to work as before, according to Google. The benefit is commercial: each language has its own budget and its own target, and you can see what it brings in.
2. Each of these campaigns targets the whole of Switzerland, with the Presence option. "Presence or interest" also reaches users outside the area who show interest in the target region. Google generally recommends broad targeting for Search, but names "Presence" as potentially more suitable when only people in specific locations should be reached. For a shop with Swiss prices and delivery terms, that is usually the case.
3. Split by region only for a business reason: a limited delivery zone, branches or a different product range. Trying to hit a language through very small areas is not worth it: Google warns that such areas may only serve intermittently or not at all.
4. A brand campaign in every language you offer. Because a brand name does not reveal a language, the user's preferred language counts here. I consider this the cheapest way into a new language version, because you are serving searchers who already know you.

For Shopping ads in Performance Max the language setting does not apply. I would therefore maintain a separate data source for each language, pointing to the matching language version. Details on feed and CHF are in Google Shopping for Switzerland, and the question of separate accounts across the DACH region (Germany, Austria and Switzerland) in one account or several for DACH.

If the budget only supports a single clean campaign, you are better off staying with German and not splitting anything.

Is machine translation enough?

As a draft, yes. As a result, no. Google itself states that it does not translate your ads. The new AI campaign localization tool is no help to a German-language account so far: it only works with US English as the source language, with French and Italian as target languages. You cannot transfer German campaigns with it.

If you have an English campaign and use the tool, you should know two things. Budgets and bids are copied unchanged, without currency conversion: €100 stays €100. The new campaign starts paused and comes with a review table including a back-translation, which you should actually read.

My advice for any other machine translation: have it checked by a native speaker of the language who understands your product range. The risk lies less in the ad copy than in product names, size details and delivery terms, where a mistake leads to returns and customer service cases. For a small range of products that need little explanation, the check can be lighter than for technical items or products that need advice.

Every language needs its own landing page

I consider a French ad leading to a German page a wasted click. For product data, Merchant Center rules the case out entirely: according to its help pages, the elements of the landing page and checkout process that help users navigate and make a purchase decision must also be in the language of the data source. A translated product page with a German checkout is therefore not enough. Check the entire path through to the order confirmation.

For organic search, the language versions should be linked via hreflang. Codes such as de-CH, fr-CH and it-CH are permitted, each version lists itself and all the others, and without links in both directions Google ignores the tags. Do not count on hreflang for your ads, though: it belongs to Google Search. In the campaign and in the feed, you set the correct language URL yourself.

One check I would always run: open your French target URL with an IP address from Zurich and your German one with an IP address from Geneva. If the shop redirects by location, the click ends up in the wrong language again, and the whole separation of region and language comes to nothing.

Swiss spelling is not cosmetic

German for Switzerland means, at the very least, no ß. The guide from the Federal Chancellery prescribes ss instead. That is an in-house rule of the federal administration, but it reflects Swiss writing practice. "Strasse" instead of "Straße" costs you little, and together with prices in CHF it tells readers that they have not landed on a German site. The same applies to feed titles and ad copy. If you run a dedicated de-CH version, you change this once. If you do not, you should at least adapt the ads and the pages they lead to.

Do Romandy and Ticino pay off?

For 2024 the Federal Statistical Office gives the main language as German for 61%, French for 23% and Italian for 8% of the population, with multiple answers included. That describes language groups, not purchasing power or search volume, and is therefore no basis for splitting the budget. The more useful question is how many orders the language version needs to carry:

Additional orders needed per month = fixed costs of the language / (contribution margin per order minus ad spend per order)

I count translation spread over the months, maintenance of feed and shop, customer service and returns in that language as fixed costs. What belongs in contribution margin is covered in which costs belong in contribution margin. A worked example with invented figures, assuming the language version costs CHF 3,000 a month:

This also answers the budget question: the budget for Romandy or Ticino follows from the hurdle, not from the population share. If the required budget or the required number of orders is out of reach, you do not build the language, and a smaller budget does not rescue the calculation. How expensive an individual click is in Switzerland is covered in the article on click prices.

My assessment on Ticino: the 8% of Italian speakers do not rule it out. They only make the hurdle harder to reach, because fixed costs barely shrink with the size of the language group. With a small order value it will often not work out, with a large one it can. In most cases I would look at French first, because the larger language group is there at similar cost.

Before you build, look at your order history: how many orders already come through the German version from postcodes in Romandy and Ticino? They do not count as additional, because you already have them. But they show whether there is any demand at all. You can also lower the hurdle by translating only best sellers and the checkout at first, and running the brand campaign plus a few categories.

Existing shops lower the hurdle

If you already run a French or Italian shop for France or Italy, you only carry part of the fixed costs: texts and parts of the maintenance are already paid for, and CHF and Swiss delivery terms come on top. The hurdle then drops considerably, and I would bring Switzerland in earlier. The reverse also applies: if you are not yet active in Switzerland at all, the language question comes second. First the expansion itself has to pay off, and German-speaking Switzerland is enough as the initial test case.

The calculation assumes that you can attribute the additional orders of a language reasonably cleanly, and that ad spend per order in the new language is estimated, not measured. So start with a cautious figure before launch and replace it with the real one after the first few months.