Web design in Zug.

Zug is the one Swiss location where English is the de facto working language for a large share of companies without ever having become an official one. The figures are unambiguous. At the end of 2025 the canton was home to 41,322 foreign nationals, a share of 30.6 per cent among more than 130,000 residents from over 140 nations. Some 41.7 per cent of employed people aged 15 and over speak English at work, and one person in seven in the Zug population speaks mainly English.

Behind that sit three economic clusters with very different web needs. The blockchain environment, which at the start of 2026 comprised more than 1,100 companies and organisations with an estimated 6,200 professionals, and whose centre of gravity remains in the canton of Zug. International trade: more than 1,700 consumer-goods companies employing around 14,000 people and generating roughly a third of cantonal GDP, plus some 200 commodity trading firms with around 2,100 employees. And finally the local trade of the town of Zug and the municipalities along the lake, which has little to do with any of that.

For the first two groups English is the language in which decisions are made, and German is the language in which you are registered. For the third group it is exactly the reverse. That classification is the first thing we settle in the opening conversation, because it determines the address structure, the editorial workload and the maintenance cost for years to come.

A website that leads in English is not the same site with the language switch flipped. It has a different address structure, different defaults and a different maintenance logic. Five decisions belong before the first line of code:

• Which language sits on the main address? If English carries the business, it belongs at the root of the domain and German in its own path — not the other way round out of habit.
• Which version does somebody with no detectable language preference get? That default is frequently forgotten, and it decides what a search system serves as standard.
• Are both languages marked up reciprocally? Without the return reference, the second version is treated as a duplicate and the whole effort evaporates. The mechanics are in our glossary entry on hreflang.
• Who maintains which language? With no named owner it is regularly the German version that goes stale — and that is precisely the one authorities, banks and local partners read.
• Do numbers, dates and amounts stay consistent? Date formats, thousands separators and CHF figures differ between language versions and are almost always overlooked.

The cost of the second language does not sit in development. It sits in the editorial work over years. So our recommendation is often the uncomfortable one: better one language kept complete and current than two kept half current. A German version that has named the wrong managing director for two years does more damage at a location like Zug than no German version at all.

Internationally, a Zug address is both an advantage and something that has to be explained: anyone who does not know you checks first whether a working business sits behind the entry. That check rarely takes longer than two minutes, and it happens on your website. What counts in it is verifiable detail, not design.

Evidenceable: people with names, roles and photographs rather than anonymous mood shots. A full business address with a telephone number. The commercial register entry including the company identification number. Statements about how long you have operated and in which markets. Why agreement between all these sources carries so much weight is explained in our glossary entry on NAP consistency.

Not evidenceable, and therefore harmful: invented awards, client logos without a mandate, "market leader" with no reference quantity, team pages listing people who left long ago. In an environment where many participants check each other, every one of those exaggerations surfaces sooner than it would elsewhere. The same principle increasingly governs AI answers: systems prefer to name companies whose details can be confirmed from several independent sources. How that works methodically is described on GEO agency Switzerland.

There is a practical consequence for the build. Trust content — people, address, register entry, history — has to be real pages that can be indexed and quoted, not a graphic in a footer. What cannot be read cannot be confirmed.

We design and we develop. We give no legal advice and we assess no regulatory admissibility. That is not a formality but a clarification of roles that becomes necessary in Zug projects regularly. Whether a statement about a financial product, a return, a token or a licensing status may appear on a website is answered by your legal advisers and the competent authority.

What we can contribute is a structure that makes legal review practical in the first place. That means every claim requiring evidence is tied to a source and a date. That qualifications and caveats sit where the claim sits, not in a separate document. That copy blocks are built so a formulation can be changed later without rebuilding the page. And that an approval loop for reviewed text is in the schedule from the beginning — not as a surprise three days before launch.

If your undertaking is really an application rather than a website — a client area, a portal, a calculation tool — that is a different project with a different approach and a different budget. We describe it under web development. If the idea should be tested before anything is built, prototype validation is the entry point, where a working prototype starts at CHF 10,000.

The range runs from CHF 3,000 to CHF 25,000, and bilingualism is the item that moves you within it. At the lower end sits a focused single-language presence for a local business or a young firm. At the upper end, a genuinely bilingual corporate site with an editing system, service and team areas, documents, and connections to existing systems. Our project calculator gives a first estimate in two minutes.

The process runs in four steps: an opening video call settling the language question, the audience and the scope; a free designed concept within 48 hours; implementation on Next.js and TypeScript with a preview URL live from the first working day; and launch with handover of credentials, code and written editing instructions. The site then belongs to you, with no builder subscription and no dependence on us.

We can evidence our craft with projects from the Zurich region: the website and Shopify store including branding for JUCAN Tailored Suits, the digital presence for the Nolte Küchen showroom in Zurich, the website for Leo Ristorante, and the site with its online calculator for Rohrsanova. All of them are documented under our work. We have no Zug client project to show — and we will not invent one to look better at this location.

Four situations in which we would advise against working with us — said in the first conversation, not in the third month:

• You need a partner who shares the legal risk. If regulatory assessment is meant to be part of the engagement, we are the wrong address. That calls for a law firm, not an agency.
• Your communication runs largely in English with native editorial standards. We implement English content, but we are not an English-language editorial team. Where language is the product, that work belongs with somebody whose core business it is.
• Your budget is below CHF 3,000. Then we will not build half a thing. For a young company, a simple and honestly brief site plus a properly maintained business profile is the better investment in that position.
• You expect weekly presence in your office. Even at a good half hour of travel, we do not work on site. If attendance is meant to be part of the service, an agency in Zug or Zurich is the more practical choice.

And a note that goes beyond the website. If your company is registered in Zug but operates elsewhere, optimising for the place name "Zug" is rarely the right lever. What counts then is the market in which you actually want to be found — and that is a question of search strategy rather than design. We would rather say so beforehand than build a location page that helps nobody.